Query CRV 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 CRV (Curve DAO Token) on the Base network. It is part of a broader suite of pay-per-call APIs offered by lowpaymentfee.com, spanning data analytics, AI/ML inference, finance/Web3, and infrastructure utilities. All endpoints use the x402 payment protocol, settling in USDC on Base with no API keys, no rate limits, and no subscriptions required.
The specific endpoint `/api/v1/wallet/CRV/balance` accepts POST requests and charges a maximum of $0.02 per call (20,000 base units of USDC, which has 6 decimals). Payment is made via the x402 exact scheme to the payee address `0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3`, with a timeout of 300 seconds. The response MIME type is `application/json`.
Documentation on the site is extremely sparse — the docs, pricing, API, and README pages all render only a "Connect wallet" prompt with no further technical detail. There is no OpenAPI spec, no request/response schema, and no usage examples available from the crawled material. The endpoint is confirmed live (returns a proper 402 challenge), but the actual response format and required request body fields are unknown.
Capabilities
Use cases
- —Check CRV token balance for a given wallet address on Base
- —Integrate CRV balance checks into portfolio tracking dashboards
- —Automate wallet monitoring for Curve DAO Token holdings
Fit
Best for
- —Agents needing on-demand CRV balance lookups without API key management
- —Developers building crypto portfolio tools on Base
- —Micropayment-friendly workflows that need per-call billing
Not for
- —Bulk or high-frequency balance polling where $0.02/call adds up quickly
- —Users who need balances for tokens not offered by this provider
- —Anyone requiring detailed documentation or SLA guarantees before integration
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/wallet/CRV/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 and returns a valid x402 challenge with clear pricing. However, there is no OpenAPI spec, no documented request/response schema, no examples, and the docs pages are empty stubs. The request body and response format are entirely inferred.
Warnings
- —No OpenAPI or schema documentation available — request and response formats are unknown and inferred
- —All docs/pricing/README pages on the site render only 'Connect wallet' with no technical content
- —The example_request_json is speculative; actual required fields are undocumented
Citations
- —The endpoint returns a 402 x402 challenge with maxAmountRequired of 20000 in USDC on Basehttps://lowpaymentfee.com/api/v1/wallet/CRV/balance
- —All APIs on the site are priced at $0.02 per request with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —The asset address 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 is USDC on Basehttps://lowpaymentfee.com/api/v1/wallet/CRV/balance