NFT metadata endpoint on Base, pay-per-call via x402 with USDC at $0.02/request.
What it does
This x402-enabled endpoint at lowpaymentfee.com returns NFT metadata for a given token (in this case token ID 10) 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, rate limits, or upfront commitments are needed — each request is individually paid at the protocol level.
The provider, lowpaymentfee.com, hosts a broader catalog of pay-per-request APIs spanning data analytics, AI/ML inference (sentiment, 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 and x402 payment flow on Base.
Because the specific endpoint path is `/api/v1/nfts/10/metadata`, it appears to serve metadata for NFT token #10. No OpenAPI schema, request body schema, or example response was found in the crawl, so the exact fields returned are unknown. The output MIME type is declared as `application/json`. The payment challenge timeout is 300 seconds.
Capabilities
Use cases
- —Retrieve NFT metadata for display in a marketplace or wallet UI
- —Programmatic lookup of NFT attributes for indexing or analytics
- —Agent-driven NFT data retrieval with automatic micropayment
Fit
Best for
- —Developers needing NFT metadata without managing API keys
- —AI agents that can settle x402 payments autonomously on Base
- —Low-volume or sporadic NFT data lookups where per-call pricing is economical
Not for
- —Bulk NFT metadata ingestion across thousands of tokens (no batch endpoint documented)
- —Users who cannot transact in USDC on the Base network
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/nfts/10/metadata \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-header>"Endpoint
Quality
The endpoint is live (402 challenge captured) with clear pricing and network info, but there is no OpenAPI schema, no documented request/response body, and no examples. The NFT metadata content is entirely opaque from the crawl material.
Warnings
- —No OpenAPI or request/response schema available — input and output fields are unknown.
- —Only a single token ID (10) is in the probed path; it is unclear whether other token IDs are supported or how the path is parameterized.
- —Provider landing page lists many API categories but crawled sub-pages (/api, /pricing, /README) returned only 'Connect wallet' with no additional documentation.
Citations
- —The endpoint returns HTTP 402 with an x402 challenge requiring USDC payment on Basehttps://lowpaymentfee.com/api/v1/nfts/10/metadata
- —maxAmountRequired is 20000 base units of USDC (USD Coin, 6 decimals) = $0.02https://lowpaymentfee.com/api/v1/nfts/10/metadata
- —All endpoints on the site are priced at $0.02/request with no API keys or rate limitshttps://lowpaymentfee.com
- —Payment timeout is 300 seconds and the USDC asset contract is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/nfts/10/metadata