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 93 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 on the same x402 model. This specific endpoint is scoped to NFT metadata retrieval. The x402 challenge confirms the endpoint is live, accepts USDC (contract 0x8335…2913) on Base, and pays out to address 0x1A2B…85F3 with a 300-second payment timeout.
Documentation is minimal — there is no OpenAPI spec, no request/response schema beyond the x402 outputSchema stub, and no examples of the actual metadata payload returned. The endpoint is confirmed live via a 402 challenge, but the exact structure of the NFT metadata response is unknown.
Capabilities
Use cases
- —Retrieving metadata for NFT token ID 93 programmatically
- —Integrating NFT metadata into wallets or marketplaces without API key management
- —Agent-driven NFT data lookups with automatic micropayment settlement
Fit
Best for
- —Developers needing keyless, pay-per-call NFT metadata access
- —AI agents that can settle x402 payments on Base
- —Projects already using USDC on Base for micropayments
Not for
- —Bulk metadata retrieval across many NFT collections (only token 93 at this path)
- —Users who need free or subscription-based API access
- —Applications requiring detailed OpenAPI documentation or SLAs
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/nfts/93/metadata \
-H "X-PAYMENT: <x402-payment-proof>" \
-H "Content-Type: application/json"Endpoint
Quality
The x402 challenge is live and pricing is clear ($0.02 USDC on Base), but there is no OpenAPI spec, no request body schema, no response examples, and no documentation beyond a landing page listing. The actual NFT metadata payload structure is entirely unknown.
Warnings
- —No OpenAPI or schema documentation available for request or response bodies
- —Only a single NFT token ID (93) is addressed by this specific endpoint path — unclear if other IDs are supported at different paths
- —No examples of the returned metadata payload exist in crawled material
- —The /api, /pricing, and /README pages all returned only a 'Connect wallet' prompt with no useful content
Citations
- —Endpoint returns 402 with x402 challenge confirming it is livehttps://lowpaymentfee.com/api/v1/nfts/93/metadata
- —maxAmountRequired is 20000 base units of USDC (6 decimals) = $0.02https://lowpaymentfee.com/api/v1/nfts/93/metadata
- —USDC asset contract on Base: 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/nfts/93/metadata
- —Provider advertises $0.02/request pricing with no API keys, no rate limitshttps://lowpaymentfee.com
- —Payment timeout is 300 secondshttps://lowpaymentfee.com/api/v1/nfts/93/metadata