Check account balance via x402 micropayment on Base network for $0.02 per request.
What it does
This endpoint at lowpaymentfee.com returns account balance information for a specific account (account ID 26) via an x402-gated POST request. Payment is settled in USDC on the Base network at $0.02 per call (20,000 base units with 6 decimals). No API keys or rate limits are required — access is granted purely through the x402 payment protocol.
The provider, lowpaymentfee.com, hosts a broader suite of pay-per-request APIs spanning data analytics, AI/ML inference (sentiment analysis, summarization, classification, embeddings), finance and crypto market data, and infrastructure utilities (geocoding, validation, conversion, generation). All endpoints are listed at $0.02 per request and settle on the Base network using USDC.
Documentation is extremely sparse. The crawled /docs, /api, /pricing, and /README pages all returned only a "Connect wallet" prompt with no further content. There is no OpenAPI schema, no request/response examples, and no detailed documentation for what the balance endpoint actually returns or what input it expects. The endpoint is confirmed live (402 challenge captured), but the actual functionality behind the paywall is unverifiable from available materials.
Capabilities
Use cases
- —Querying account balance data behind a micropayment wall
- —Demonstrating x402 payment protocol integration
- —Agent-driven balance lookups without API key management
Fit
Best for
- —Developers experimenting with x402 payment protocol
- —Agents that need keyless, pay-per-call API access
- —Low-friction balance queries settled in USDC on Base
Not for
- —Production use requiring documented request/response schemas
- —High-volume balance queries where per-call pricing adds up
- —Users who need detailed API documentation before integrating
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/accounts/26/balance \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-token>"Endpoint
Quality
The endpoint is confirmed live via a valid 402 challenge, and pricing is clear ($0.02 USDC on Base). However, there is no OpenAPI schema, no request/response examples, and all documentation pages are empty stubs showing only 'Connect wallet'. The actual functionality behind the paywall cannot be verified.
Warnings
- —No API documentation available — /docs, /api, /pricing, and /README all return only 'Connect wallet'
- —No OpenAPI or output schema describing request parameters or response format
- —Actual endpoint behavior behind the paywall is unverifiable from crawl data
- —The specific endpoint path (/accounts/26/balance) suggests a hardcoded account ID; unclear if this is parameterizable
Citations
- —Endpoint returns 402 with x402 challenge requiring 20000 base units of USDC on Base networkhttps://lowpaymentfee.com/api/v1/accounts/26/balance
- —All APIs priced at $0.02 per request with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —USDC asset address 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Basehttps://lowpaymentfee.com/api/v1/accounts/26/balance
- —Provider offers APIs across data analytics, AI/ML, finance/Web3, and infrastructure categorieshttps://lowpaymentfee.com