Query ENS wallet balances via x402 micropayment on Base for $0.02 per request.
What it does
This endpoint at lowpaymentfee.com provides ENS (Ethereum Name Service) wallet balance lookups, accessible via the x402 payment protocol. The endpoint accepts POST requests and returns JSON. Payment is settled on the Base network using USDC (contract 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913) at a cost of $0.02 per request (20,000 base units with 6 decimals). No API keys or rate limits are required — callers simply attach an X-PAYMENT header with a valid x402 payment proof.
The provider (lowpaymentfee.com) hosts a broad catalog of pay-per-call APIs spanning data analytics, AI/ML inference, finance/Web3, and utility services, all priced at $0.02 per request on the Base network. This specific endpoint focuses on ENS balance queries, likely resolving an ENS name to its associated wallet address and returning the balance. However, the exact request schema (e.g., whether the ENS name is passed in the URL path, query params, or POST body) and the response schema are not documented in the crawled material.
The endpoint is live, returning a well-formed x402 challenge (HTTP 402) with version 1 of the protocol. Documentation pages on the site (/docs, /pricing, /README) appear to require wallet connection and did not yield useful content during the crawl, so details about request/response formats remain unknown.
Capabilities
Use cases
- —Check the token balance of a wallet identified by its ENS name
- —Build dashboards that display ENS-linked wallet balances in real time
- —Integrate ENS balance checks into trading bots or portfolio trackers
- —Verify wallet holdings before executing on-chain transactions
- —Agent-driven wallet monitoring without managing API keys
Fit
Best for
- —Developers needing quick ENS balance lookups without subscription overhead
- —AI agents that need pay-per-call crypto data access
- —Prototyping Web3 apps that resolve ENS names to balances
Not for
- —High-volume batch queries where per-call pricing adds up (no bulk discount documented)
- —Users who need detailed transaction history rather than just balances
- —Non-crypto use cases with no need for ENS resolution
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/wallet/ENS/balance \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402_payment_proof>" \
-d '{"ensName": "vitalik.eth"}'Example
Request
{
"ensName": "vitalik.eth"
}Endpoint
Quality
The endpoint is live and returns a valid x402 challenge, confirming it exists and accepts USDC on Base. However, there is no OpenAPI schema, no documented request/response format, and all documentation pages require wallet connection and returned no content. The request body and response structure are entirely inferred.
Warnings
- —No request or response schema documented — request body format is guessed
- —All documentation pages (/docs, /pricing, /README) returned only 'Connect wallet' with no useful content
- —The provider hosts many endpoints at $0.02 each but provides no detailed docs for any of them
- —Example request JSON is speculative; actual field names may differ
Citations
- —Endpoint returns HTTP 402 with x402 version 1 challenge, confirming it is livehttps://lowpaymentfee.com/api/v1/wallet/ENS/balance
- —Payment is 20,000 base units of USDC (6 decimals = $0.02) on Base networkhttps://lowpaymentfee.com/api/v1/wallet/ENS/balance
- —All APIs on the site are priced at $0.02 per request with no API keys or rate limitshttps://lowpaymentfee.com
- —USDC asset contract is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/wallet/ENS/balance