Check LINK wallet balances on-chain via x402 micropayment at $0.02 per request on Base.
What it does
This endpoint at lowpaymentfee.com returns the balance of a LINK (Chainlink) wallet. It is part of a broader suite of pay-per-call APIs offered by lowpaymentfee.com, all gated via the x402 payment protocol. Each request costs $0.02 (20,000 base units of USDC on the Base network, where USDC has 6 decimals). No API keys or accounts are required — callers simply attach an x402 payment header with each request.
The provider's landing page lists dozens of endpoints spanning data analytics, AI/ML inference, finance/Web3 data, and infrastructure utilities, all at the same $0.02 per-call price point. This specific endpoint (`/api/v1/wallet/LINK/balance`) falls under the Finance & Web3 category and likely returns the LINK token balance for a given wallet address. The endpoint accepts POST requests and returns JSON.
Documentation 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 x402 challenge is live and well-formed, confirming the endpoint is operational, but the lack of documentation makes it difficult to know the exact request body format or response structure.
Capabilities
Use cases
- —Querying LINK token balances for a specific wallet address
- —Integrating on-chain LINK balance checks into automated trading or portfolio dashboards
- —Agent-driven wallet monitoring without needing API keys or accounts
Fit
Best for
- —Developers needing quick, keyless LINK balance lookups
- —AI agents that can settle x402 micropayments on Base
- —Low-volume or sporadic balance checks where $0.02/call is cost-effective
Not for
- —High-frequency balance polling where per-call costs would accumulate quickly
- —Users who need detailed transaction history or multi-token balance queries in a single call
- —Anyone unable to settle USDC payments on the Base network
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/wallet/LINK/balance \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-token>" \
-d '{"address": "0xYourWalletAddress"}'Example
Request
{
"address": "0x1234567890abcdef1234567890abcdef12345678"
}Endpoint
Quality
The x402 challenge is live and pricing is clear ($0.02/call in USDC on Base), but there is zero documentation: no OpenAPI spec, no request/response schema, no examples. The request body and response format are entirely inferred. The docs pages return only a wallet-connect prompt.
Warnings
- —No documentation available — docs, pricing, API, and README pages all show only 'Connect wallet'
- —No OpenAPI or schema provided; request body format is guessed
- —Response schema is unknown — example_response_json is null
- —The provider lists many endpoints but none have documented schemas
Citations
- —Endpoint returns HTTP 402 with x402 challenge, confirming it is livehttps://lowpaymentfee.com/api/v1/wallet/LINK/balance
- —Price is $0.02 per request (maxAmountRequired 20000 base units of USDC with 6 decimals on Base)https://lowpaymentfee.com
- —USDC asset address 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Base networkhttps://lowpaymentfee.com/api/v1/wallet/LINK/balance
- —No API keys, no rate limits, instant access advertisedhttps://lowpaymentfee.com