NFT metadata endpoint on Base, pay-per-call via x402 with USDC (~$0.02/request).
What it does
This x402-enabled endpoint at lowpaymentfee.com serves NFT metadata for token ID 32 via a POST request. Payment is settled on the Base network using USDC (contract 0x8335…2913) through the x402 exact-payment scheme. The maximum amount required per call is 20,000 base units of USDC, which equals $0.02 (USDC uses 6 decimals). No API keys or rate limits are advertised; access is granted instantly upon valid payment.
The provider operates a broader platform offering dozens of pay-per-call endpoints 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 listed endpoints share the same $0.02-per-request pricing model on the Base network.
Documentation is minimal — there is no OpenAPI spec, no request/response schema beyond the x402 challenge's outputSchema stub, and the crawled pages beyond the landing page returned only a wallet-connect prompt. The endpoint is confirmed live (HTTP 402 challenge returned successfully), but the actual response payload structure for NFT metadata is unknown.
Capabilities
Use cases
- —Retrieve metadata for a specific NFT (token 32) programmatically
- —Integrate NFT metadata lookups into agent workflows without API key management
- —Pay-per-call NFT data access settled on Base L2
Fit
Best for
- —Agents needing on-demand NFT metadata without subscription commitments
- —Developers experimenting with x402 payment-gated APIs
- —Low-volume NFT metadata lookups at $0.02 per request
Not for
- —Bulk or high-volume NFT metadata scraping (no batch endpoint documented)
- —Querying arbitrary token IDs (this endpoint is scoped to token 32)
- —Users who need detailed response schema documentation before integrating
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/nfts/32/metadata \
-H "X-PAYMENT: <x402_payment_token>" \
-H "Content-Type: application/json"Endpoint
Quality
The endpoint is confirmed live via a valid 402 challenge, but there is no OpenAPI spec, no documented request body schema, no example responses, and the crawled docs pages are empty beyond a landing page listing. The endpoint is narrowly scoped to a single NFT token ID with no explanation of what metadata is returned.
Warnings
- —No OpenAPI or request/response schema available — actual payload structure is unknown
- —Endpoint is scoped to a single NFT token ID (32); unclear if other token IDs are supported at different paths
- —Documentation pages (/api, /pricing, /README) returned only a wallet-connect prompt with no useful content
- —The provider lists many other endpoints on the landing page but none have documented schemas
Citations
- —Endpoint returns HTTP 402 with x402 challenge requiring USDC payment on Base networkhttps://lowpaymentfee.com/api/v1/nfts/32/metadata
- —maxAmountRequired is 20000 base units of USDC (USD Coin, 6 decimals) = $0.02https://lowpaymentfee.com/api/v1/nfts/32/metadata
- —Provider advertises $0.02/request pricing, no API keys, no rate limits, instant access on Base networkhttps://lowpaymentfee.com
- —USDC asset contract is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Basehttps://lowpaymentfee.com/api/v1/nfts/32/metadata