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 30 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-decimal USDC). No API keys, rate limits, or subscriptions are required — callers simply attach an X-PAYMENT header with a valid x402 payment proof.
The provider's landing page advertises a broad suite of APIs spanning data analytics, AI/ML inference, finance/Web3, and infrastructure utilities, all priced uniformly at $0.02 per request. This specific endpoint falls under an NFT metadata category (path: /api/v1/nfts/30/metadata). The response MIME type is application/json, and the payment timeout is 300 seconds.
Because the endpoint returned a well-formed 402 challenge with x402 version 1, it is confirmed live. However, no OpenAPI schema, detailed documentation, or example responses were found in the crawl. The actual structure of the returned NFT metadata is unknown — callers should expect a JSON object but will need to discover the exact fields empirically.
Capabilities
Use cases
- —Retrieving on-chain NFT metadata for display in wallets or marketplaces
- —Programmatic lookup of NFT attributes for indexing or analytics
- —Agent-driven NFT data fetching without pre-registration or API keys
Fit
Best for
- —Developers needing quick, keyless access to NFT metadata
- —AI agents that can settle micropayments via x402 on Base
- —Prototyping NFT-aware applications without subscription overhead
Not for
- —Bulk retrieval of metadata for large NFT collections (no batch endpoint evident)
- —Users who cannot settle USDC payments on the Base network
- —Applications requiring detailed OpenAPI documentation or guaranteed SLAs
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/nfts/30/metadata \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402_payment_proof>"Endpoint
Quality
The endpoint is confirmed live via a valid 402 challenge with clear pricing and network details. However, there is no OpenAPI schema, no example request/response, and no documentation beyond the landing page listing. The actual NFT metadata structure is entirely unknown.
Warnings
- —No OpenAPI or schema documentation available — response format must be discovered empirically
- —Only token ID 30 is referenced in this endpoint path; unclear if other token IDs are supported at different paths
- —No example responses or field descriptions found in crawl material
- —Provider site pages beyond the landing page returned only 'Connect wallet' with no useful content
Citations
- —Endpoint returns a 402 challenge with x402 version 1, confirming it is livehttps://lowpaymentfee.com/api/v1/nfts/30/metadata
- —maxAmountRequired is 20000 base units of USDC (0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913) on Base, equaling $0.02https://lowpaymentfee.com/api/v1/nfts/30/metadata
- —Provider advertises $0.02/request, no API keys, no rate limits, instant access on Base networkhttps://lowpaymentfee.com
- —Payment timeout is 300 seconds and response MIME type is application/jsonhttps://lowpaymentfee.com/api/v1/nfts/30/metadata