Check MATIC wallet balances via x402 micropayment on Base for $0.02 per request.
What it does
This endpoint at lowpaymentfee.com returns MATIC wallet balance data, accessible through the x402 payment protocol. It is part of a broader suite of pay-per-call APIs offered by the same provider, spanning data analytics, AI/ML inference, finance/Web3, and utility services. All endpoints on the platform share a uniform $0.02-per-request pricing model settled in USDC on the Base network.
The specific endpoint `/api/v1/wallet/MATIC/balance` accepts POST requests and returns JSON. Payment is handled via the x402 exact-payment scheme: callers attach an `X-PAYMENT` header with a signed USDC payment of up to 20,000 base units (i.e., $0.02, since USDC uses 6 decimals) to the provider's address on Base. No API keys, accounts, or rate limits are advertised — access is purely payment-gated.
Documentation beyond the landing page is extremely sparse. The /docs, /pricing, /api, and /README pages all resolve to a minimal "Connect wallet" prompt with no additional 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 behavior, required request body fields, and response format are unknown.
Capabilities
Use cases
- —Querying MATIC token balances for a given wallet address
- —Integrating wallet balance checks into automated trading or portfolio bots
- —Agent-driven on-chain balance monitoring without API key management
Fit
Best for
- —Agents needing quick, keyless MATIC balance lookups
- —Developers who prefer pay-per-call over subscription API plans
- —x402-native workflows on the Base network
Not for
- —High-volume balance polling where $0.02/request adds up quickly
- —Users who need detailed transaction history or multi-token queries
- —Anyone requiring well-documented request/response schemas before integration
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/wallet/MATIC/balance \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-signed-payment-header>" \
-d '{"address": "0xYourWalletAddress"}'Example
Request
{
"address": "0x1234567890abcdef1234567890abcdef12345678"
}Endpoint
Quality
The endpoint is confirmed live with a valid x402 402 challenge and clear pricing ($0.02 USDC on Base). However, there is no OpenAPI spec, no documented request/response schema, no examples, and all documentation 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
- —All doc/pricing/README pages return only a 'Connect wallet' stub with no content
- —Example request JSON is speculative; actual required fields are undocumented
- —The broader platform lists many endpoints but none have detailed docs
Citations
- —Endpoint returns a 402 x402 challenge with maxAmountRequired of 20000 base units in USDC on Basehttps://lowpaymentfee.com/api/v1/wallet/MATIC/balance
- —All APIs on the platform are priced at $0.02 per request with no API keys, no rate limits, and instant accesshttps://lowpaymentfee.com
- —USDC asset address 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Base networkhttps://lowpaymentfee.com/api/v1/wallet/MATIC/balance