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 70 via a POST request, gated behind 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 return.
The provider, lowpaymentfee.com, hosts a broader catalog of pay-per-call APIs spanning data analytics, AI/ML inference, finance/Web3 data, and utility services, all priced at $0.02 per request and settled in USDC on Base. This specific endpoint (/api/v1/nfts/70/metadata) returns NFT metadata, though the exact schema of the response is not documented. The x402 challenge confirms the endpoint is live, accepts the "exact" payment scheme, and targets the canonical USDC contract on Base (0x8335…2913). The payment recipient address is 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3, with a maximum timeout of 300 seconds.
Note that documentation is minimal — there is no OpenAPI spec, no example request/response payloads, and the crawled pages beyond the landing page returned only wallet-connect prompts. The actual structure of the NFT metadata returned is unknown.
Capabilities
Use cases
- —Retrieving metadata for NFT token ID 70 programmatically
- —Integrating NFT display data into wallets or marketplaces
- —Agent-driven NFT data lookups with automatic micropayment
Fit
Best for
- —Developers needing NFT metadata without API key management
- —AI agents that can settle x402 payments on Base
- —Low-volume, on-demand NFT data retrieval
Not for
- —Bulk retrieval of metadata across many NFT collections (only token 70 is documented)
- —Users who cannot settle USDC payments on the Base network
- —Applications requiring detailed response schema guarantees
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/nfts/70/metadata \
-H "X-PAYMENT: <x402_payment_proof>" \
-H "Content-Type: application/json"Endpoint
Quality
The x402 challenge is live and confirms pricing, network, and asset. However, there is no OpenAPI spec, no documented request or response schema, no example payloads, and the endpoint serves metadata for a single hard-coded token ID with no broader documentation. Effectively a stub listing.
Warnings
- —No OpenAPI or schema documentation available for this endpoint
- —Response payload structure is completely unknown — no examples provided
- —Only token ID 70 is referenced; unclear if other token IDs are supported
- —Crawled subpages (/api, /pricing, /README) returned only wallet-connect prompts with no useful content
Citations
- —Endpoint returns HTTP 402 with x402 challenge, confirming it is livehttps://lowpaymentfee.com/api/v1/nfts/70/metadata
- —maxAmountRequired is 20000 base units of USDC (6 decimals) = $0.02 per requesthttps://lowpaymentfee.com/api/v1/nfts/70/metadata
- —Asset contract is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 (USDC on Base)https://lowpaymentfee.com/api/v1/nfts/70/metadata
- —All APIs on the platform are priced at $0.02 per request with no API keys or rate limitshttps://lowpaymentfee.com