NFT metadata endpoint on Base, pay-per-call via x402 with USDC at $0.02/request.
What it does
This endpoint at lowpaymentfee.com serves NFT metadata for token ID 98 via a POST request, gated by the x402 payment protocol. Each call costs $0.02 in USDC on the Base network (maxAmountRequired of 20,000 base units with 6 decimals = $0.02). No API keys or accounts are needed — callers attach an X-PAYMENT header with a valid x402 payment proof and receive JSON metadata in response.
The provider hosts a broader suite of pay-per-call APIs across categories including data analytics, AI/ML inference (sentiment analysis, summarization, classification, embeddings), finance/Web3 (price feeds, exchange rates, gas estimates), and infrastructure utilities (geocoding, validation, conversion). All endpoints share the same $0.02/request pricing model, settle on Base via USDC, and require no rate-limit management or subscription commitments.
This specific endpoint returns NFT metadata (mimeType: application/json). The exact schema of the returned metadata is not documented, so callers should expect a standard NFT metadata JSON object but should verify the response structure. The x402 challenge is live and correctly configured with x402Version 1, a 300-second payment timeout, and payment directed to address 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3 using USDC contract 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Base.
Capabilities
Use cases
- —Fetching NFT metadata for token ID 98 in automated pipelines
- —Integrating NFT data into wallets or marketplaces without API key management
- —Agent-driven NFT metadata retrieval with micropayment settlement
Fit
Best for
- —Developers needing keyless, pay-per-call NFT metadata access
- —AI agents that can settle x402 payments on Base
- —Projects wanting low-friction NFT data without subscriptions
Not for
- —Bulk retrieval of metadata for thousands of NFTs (no batch endpoint documented)
- —Users who cannot settle USDC payments on the Base network
- —Applications requiring metadata for arbitrary token IDs (only token 98 is confirmed)
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/nfts/98/metadata \
-H "X-PAYMENT: <x402-payment-proof>" \
-H "Content-Type: application/json"Endpoint
Quality
The x402 challenge is live and well-formed, confirming the endpoint works and pricing is clear ($0.02 USDC on Base). However, there is no OpenAPI schema, no documented request body format, no example response, and no detail on what the NFT metadata actually contains. The crawl pages beyond the landing page returned only 'Connect wallet' with no additional documentation.
Warnings
- —No response schema or example response documented — the structure of the returned NFT metadata is unknown.
- —No request body schema documented — it is unclear whether a POST body is required or what fields it accepts.
- —Only token ID 98 is confirmed at this path; availability of other token IDs is not documented.
- —Provider docs pages (/api, /pricing, /README) returned no useful content beyond 'Connect wallet'.
Citations
- —The endpoint returns HTTP 402 with x402Version 1, maxAmountRequired 20000 in USDC on Base networkhttps://lowpaymentfee.com/api/v1/nfts/98/metadata
- —USDC asset contract is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Basehttps://lowpaymentfee.com/api/v1/nfts/98/metadata
- —All endpoints priced at $0.02/request with no API keys, no rate limits, instant access on Base networkhttps://lowpaymentfee.com
- —Payment timeout is 300 seconds, payTo address is 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3https://lowpaymentfee.com/api/v1/nfts/98/metadata