x402-gated account balance endpoint on Base, pay-per-call with USDC.
What it does
This endpoint at lowpaymentfee.com provides a "Premium API Access" account balance lookup via the x402 payment protocol. When called without payment, it returns a 402 challenge requiring a USDC micropayment on the Base network. The specific endpoint `/api/v1/accounts/80/balance` appears to return balance information for account ID 80, though no detailed documentation or response schema is available.
The parent site lowpaymentfee.com hosts a broader suite of x402-gated APIs spanning data & analytics, AI/ML (sentiment analysis, summarization, classification, embeddings), finance & Web3 (price feeds, exchange rates, token quotes, gas estimates), and infrastructure utilities (geocoding, validation, conversion, generation). All endpoints are listed at $0.02 per request. The probed endpoint's x402 challenge specifies a maxAmountRequired of 20000 base units of USDC (6 decimals), which equals $0.02 — consistent with the site's advertised pricing.
The site advertises no API keys, no rate limits, and instant access. Payment settles on the Base L2 network using USDC (contract 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913). Documentation pages (/docs, /pricing, /README) returned only a "Connect wallet" prompt with no substantive content, so the actual response format and fields for this specific endpoint remain unknown.
Capabilities
Use cases
- —Querying account balance data with per-request USDC micropayments
- —Agent-driven balance lookups without API key management
- —Programmatic access to account information via x402 protocol
Fit
Best for
- —Developers experimenting with x402 pay-per-call APIs
- —Agents that can settle USDC payments on Base
- —Use cases needing keyless, on-demand API access
Not for
- —Users who need detailed API documentation or response schemas before integrating
- —High-volume use cases where per-request payment overhead is impractical
- —Users without a Base-compatible USDC wallet
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/accounts/80/balance \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-token>"Endpoint
Quality
The endpoint is live and returns a valid x402 challenge, but there is no documentation, no response schema, no example responses, and the docs/pricing/README pages are all empty stubs. The purpose of the specific '/accounts/80/balance' endpoint is only inferable from its URL path. This is effectively a stub listing.
Warnings
- —No documentation available — /docs, /pricing, and /README pages all return only a 'Connect wallet' prompt with no content.
- —No response schema or example response is provided for this endpoint.
- —The specific meaning of 'account 80' and what 'balance' returns is undocumented.
- —The broader site lists many API categories (AI, finance, utilities) but none have visible documentation; it is unclear whether all endpoints are fully functional.
Citations
- —The x402 challenge specifies maxAmountRequired of 20000 base units of USDC on Base networkhttps://lowpaymentfee.com/api/v1/accounts/80/balance
- —USDC asset contract is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/accounts/80/balance
- —Site advertises $0.02 per request, no API keys, no rate limits, instant accesshttps://lowpaymentfee.com
- —Documentation pages (/docs, /pricing, /README) contain only 'Connect wallet' with no substantive contenthttps://lowpaymentfee.com/docs