Query OKB wallet balance via x402 micropayment on Base for $0.02 per request.
What it does
This endpoint at lowpaymentfee.com returns the wallet balance for the OKB token. It is part of a broader suite of pay-per-call APIs offered by lowpaymentfee.com, all gated behind the x402 payment protocol. The endpoint accepts POST requests and returns JSON.
Payment is settled on the Base network using USDC (contract 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913). The maximum amount required per call is 20,000 base units of USDC, which equals $0.02 (USDC uses 6 decimals). No API keys or rate limits are advertised — access is granted purely through the x402 payment header. The provider advertises uniform $0.02 pricing across all their endpoints.
The provider's site lists endpoints spanning data analytics, AI/ML inference (sentiment, summarization, classification, embeddings), finance/Web3 (price feeds, exchange rates, token quotes, gas estimates), and infrastructure utilities (geocoding, validation, conversion, generation). However, this specific listing covers only the `/api/v1/wallet/OKB/balance` endpoint. Documentation beyond the landing page is extremely sparse — the docs, API, pricing, and README pages all render only a "Connect wallet" prompt with no additional technical detail or schema information.
Capabilities
Use cases
- —Checking OKB token balance for a given wallet address
- —Integrating OKB balance lookups into trading bots or portfolio dashboards
- —Automated monitoring of OKB holdings across wallets
Fit
Best for
- —Agents needing on-demand crypto wallet balance queries without API key management
- —Developers who prefer pay-per-call micropayments over subscription billing
- —Quick one-off OKB balance lookups settled via USDC on Base
Not for
- —High-frequency polling where per-request fees would accumulate significantly
- —Users who need detailed transaction history or multi-token portfolio aggregation
- —Anyone without a Base-network USDC wallet to fund x402 payments
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/wallet/OKB/balance \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402_payment_token>" \
-d '{"address": "0xYourWalletAddress"}'Example
Request
{
"address": "0x1234567890abcdef1234567890abcdef12345678"
}Endpoint
Quality
The endpoint is live (returns a valid x402 402 challenge) and pricing is clear ($0.02 USDC on Base). However, there is no documentation, no OpenAPI schema, no example responses, and no information about what request body fields are expected or what the response format looks like. The request and response examples above are inferred/guessed. The docs, API, pricing, and README pages are all blank beyond a wallet-connect prompt.
Warnings
- —No documentation available — docs, API, pricing, and README pages all show only 'Connect wallet' with no technical content.
- —Request body schema is unknown; the example_request_json is speculative.
- —Response schema is completely unknown; no example_response_json can be provided.
- —The provider site lists many diverse endpoints (AI, analytics, finance, utilities) all at $0.02 — it is unclear whether these are fully implemented or placeholder listings.
Citations
- —The endpoint returns a 402 x402 challenge with maxAmountRequired of 20000 base units of USDC on Base networkhttps://lowpaymentfee.com/api/v1/wallet/OKB/balance
- —USDC asset contract is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Basehttps://lowpaymentfee.com/api/v1/wallet/OKB/balance
- —Uniform pricing of $0.02 per request across all endpoints, no API keys, no rate limitshttps://lowpaymentfee.com
- —Docs, API, pricing, and README pages render only 'Connect wallet' with no additional contenthttps://lowpaymentfee.com/docs