Query BLUR token wallet balance on Base via x402 micropayment at $0.02 per request.
What it does
This endpoint at lowpaymentfee.com returns the wallet balance for the BLUR token. It is part of a broader suite of pay-per-call APIs offered by the provider, spanning data analytics, AI/ML inference, finance/Web3, and utility services. All endpoints are gated behind the x402 payment protocol, settling in USDC on the Base network.
The specific endpoint `/api/v1/wallet/BLUR/balance` accepts POST requests and returns JSON. The x402 challenge advertises a maximum cost of 20,000 base units of USDC (0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Base), which equals $0.02 per request (USDC uses 6 decimals). The provider's landing page confirms a flat $0.02/request pricing model across all endpoints, with no API keys, no rate limits, and no minimum commitments required.
Documentation is extremely sparse — the /docs, /api, /pricing, and /README pages all render only a "Connect wallet" prompt with no further technical detail. There is no OpenAPI spec, no request/response schema documentation, and no example payloads available. The endpoint is live (returns a proper 402 x402 challenge), but the actual response format and required request body fields are unknown. The wallet balance endpoint likely returns a JSON object with balance information for the BLUR token, but this is inferred from the endpoint path rather than documented.
Capabilities
Use cases
- —Checking BLUR token balance for a given wallet address
- —Integrating BLUR balance data into portfolio tracking dashboards
- —Automated agents querying token holdings as part of trading workflows
Fit
Best for
- —Agents needing quick BLUR token balance lookups without API key management
- —Pay-per-use crypto data queries settled on Base
- —Lightweight wallet balance checks without subscription overhead
Not for
- —Bulk historical balance queries (no documented batch support)
- —Users needing detailed documentation or guaranteed SLAs
- —Multi-token or multi-chain balance aggregation in a single call
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/wallet/BLUR/balance \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402_payment_header>" \
-d '{"address": "0xYourWalletAddress"}'Example
Request
{
"address": "0x1234567890abcdef1234567890abcdef12345678"
}Endpoint
Quality
The endpoint is live and returns a valid x402 challenge with clear pricing ($0.02 USDC on Base). However, documentation is essentially nonexistent — no OpenAPI spec, no request/response schemas, no examples. The request body and response format are entirely inferred from the URL path. This is effectively a stub listing.
Warnings
- —No documentation available — /docs, /api, /pricing, and /README pages all show only 'Connect wallet' with no technical content
- —No OpenAPI or schema definition found; request body and response format are unknown
- —Example request JSON is speculative — actual required fields are undocumented
- —The broader provider site lists many endpoint categories but this specific wallet balance endpoint is not listed on the landing page
Citations
- —The x402 challenge advertises maxAmountRequired of 20000 base units of USDC on Base networkhttps://lowpaymentfee.com/api/v1/wallet/BLUR/balance
- —USDC contract address on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/wallet/BLUR/balance
- —Provider advertises $0.02/request flat pricing with no API keys, no rate limits, and instant accesshttps://lowpaymentfee.com