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 91) behind an x402 paywall. It is part of a broader platform offering dozens of pay-per-call API endpoints spanning data analytics, AI/ML inference, finance/Web3 data, and infrastructure utilities — all priced at $0.02 per request and settled in USDC on the Base network.
The specific endpoint `/api/v1/accounts/91/balance` accepts POST requests and requires an X-PAYMENT header conforming to the x402 protocol (version 1, "exact" scheme). Payment is made in USDC (contract 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Base) to the payTo address. The maxAmountRequired of 20000 base units corresponds to $0.02 (USDC uses 6 decimals). The endpoint returns JSON.
Documentation beyond the landing page is extremely sparse — the docs, API, pricing, and README pages all render only a "Connect wallet" prompt with no further content. There is no OpenAPI schema, no request/response examples, and no description of what fields the balance response contains or what input parameters (if any) the POST body expects. The platform advertises no API keys, no rate limits, and instant access, but the actual behavior and data returned by this specific endpoint remain undocumented.
Capabilities
Use cases
- —Querying account balance data with per-request USDC micropayments
- —Integrating pay-as-you-go balance lookups into agent workflows
- —Demonstrating x402 protocol payment flows on Base network
Fit
Best for
- —Developers experimenting with x402 micropayment protocols
- —Agents needing on-demand account balance data without API key management
- —Low-volume, pay-per-use balance queries
Not for
- —High-volume balance monitoring requiring bulk or subscription pricing
- —Users who need detailed API documentation and response schemas before integrating
- —Anyone without a Base-network USDC wallet
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/accounts/91/balance \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-token>"Endpoint
Quality
The endpoint is live (returns a valid 402 x402 challenge) and pricing is clear ($0.02 USDC on Base). However, there is no OpenAPI schema, no documented request/response format, no examples, and all documentation pages render only a wallet-connect prompt. The purpose of this specific endpoint (account 91 balance) is vague and undocumented.
Warnings
- —No API documentation available — docs, pricing, and README pages all show only 'Connect wallet' with no content.
- —No request body schema or response schema documented; callers cannot know what to send or what to expect back.
- —The endpoint path references a hardcoded account ID (91); it is unclear whether this is a demo or a real account lookup.
- —The broader platform lists many endpoints but none appear to have public documentation beyond titles and prices.
Citations
- —The endpoint returns a 402 x402 challenge with maxAmountRequired of 20000 base units in USDC on Base network.https://lowpaymentfee.com/api/v1/accounts/91/balance
- —All endpoints on the platform are priced at $0.02 per request with no API keys, no rate limits, and instant access.https://lowpaymentfee.com
- —USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913.https://lowpaymentfee.com/api/v1/accounts/91/balance
- —Documentation pages (docs, api, pricing, README) render only a 'Connect wallet' prompt.https://lowpaymentfee.com/docs