Query RSR token 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 RSR (Reserve Rights) token. 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 on the platform use the x402 payment protocol, settling in USDC on the Base network.
The specific endpoint `/api/v1/wallet/RSR/balance` accepts POST requests and costs $0.02 per call (20,000 base units of USDC with 6 decimals). No API keys or accounts are required — payment is handled inline via the x402 `X-PAYMENT` header. The platform advertises no rate limits and instant access.
Documentation on the site is extremely thin. The docs, pricing, API, and README pages all render only a "Connect wallet" prompt with no further technical detail. There is no OpenAPI schema, no request/response examples, and no description of what parameters the endpoint expects (e.g., a wallet address) or what fields the response contains. The endpoint is confirmed live (returns a proper 402 challenge), but the lack of documentation makes integration speculative.
Capabilities
Use cases
- —Checking RSR token balance for a given wallet address
- —Monitoring RSR holdings programmatically in a portfolio tracker
- —Integrating RSR balance lookups into a trading bot or DeFi dashboard
Fit
Best for
- —Developers needing on-demand RSR balance checks without API key management
- —Agents or bots that can pay per call via x402 on Base
- —Low-volume or sporadic wallet balance queries where subscription pricing is wasteful
Not for
- —High-frequency balance polling where $0.02/request adds up quickly
- —Users who need balances for many tokens in a single call (this endpoint is RSR-specific)
- —Anyone requiring detailed documentation or guaranteed SLAs before integrating
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/wallet/RSR/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, documentation is essentially nonexistent — docs/pricing/API pages all show only 'Connect wallet'. There is no OpenAPI schema, no request/response examples, and the request body format is entirely inferred. The example request is speculative.
Warnings
- —No documentation available — docs, pricing, API, and README pages all render only 'Connect wallet'
- —No OpenAPI or schema definition; request parameters and response format are unknown
- —Example request body (address field) is inferred and not confirmed by any source material
- —The broader platform lists many endpoints but none have documented schemas
Citations
- —The endpoint returns a 402 challenge with maxAmountRequired of 20000 in USDC on Base networkhttps://lowpaymentfee.com/api/v1/wallet/RSR/balance
- —All endpoints on the platform cost $0.02 per request with no API keys, no rate limits, and instant accesshttps://lowpaymentfee.com
- —The asset used for payment is USDC (contract 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913) on Basehttps://lowpaymentfee.com/api/v1/wallet/RSR/balance
- —Docs, pricing, API, and README pages render only 'Connect wallet' with no further contenthttps://lowpaymentfee.com/docs