NFT metadata endpoint on Base, pay-per-call via x402 with USDC at $0.02/request.
What it does
This endpoint serves NFT metadata for token ID 16 via the x402 payment protocol on the Base network. It accepts POST requests and returns JSON. Payment is settled in USDC (contract 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913) on Base, with a maximum cost of $0.02 per request (20,000 base units at 6 decimals). No API keys or rate limits are required — callers simply attach an X-PAYMENT header with a valid x402 payment proof.
The endpoint is part of a broader suite of pay-per-call APIs hosted at lowpaymentfee.com, which spans data analytics, AI/ML inference, finance/Web3 data, and utility services, all priced uniformly at $0.02 per request. The specific endpoint at /api/v1/nfts/16/metadata appears to return metadata for a particular NFT, though the exact schema of the response body is not documented.
The endpoint is live and returned a proper 402 challenge when probed. However, documentation is minimal — there is no OpenAPI spec, no example request/response payloads, and no detailed description of what fields the NFT metadata contains. The provider's landing page confirms the pricing model and general approach but does not provide endpoint-specific documentation.
Capabilities
Use cases
- —Retrieving metadata for NFT token ID 16 programmatically
- —Integrating NFT display data into wallets or marketplaces
- —Agent-driven NFT data lookups with micropayment settlement
Fit
Best for
- —Agents needing on-demand NFT metadata without API key management
- —Developers testing x402 payment flows on Base
- —Low-volume, pay-as-you-go NFT data retrieval
Not for
- —Bulk NFT metadata indexing across many collections
- —Use cases requiring detailed response schema guarantees upfront
- —Users who need metadata for arbitrary token IDs (this endpoint is scoped to token 16)
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/nfts/16/metadata \
-H "X-PAYMENT: <x402_payment_proof>" \
-H "Content-Type: application/json"Endpoint
Quality
The endpoint is live and returns a valid x402 402 challenge with clear pricing. However, there is no OpenAPI spec, no documented request/response schema, and no examples. The endpoint is narrowly scoped to a single NFT token ID with no explanation of what metadata is returned.
Warnings
- —No OpenAPI or schema documentation available
- —Response payload structure is unknown — no example responses provided
- —Endpoint is scoped to a single NFT (token ID 16); unclear if other token IDs are available at similar paths
- —The broader lowpaymentfee.com site lists many API categories but provides no detailed docs for any of them
Citations
- —The endpoint returns a 402 challenge with maxAmountRequired of 20000 base units in USDC on Basehttps://lowpaymentfee.com/api/v1/nfts/16/metadata
- —All APIs on lowpaymentfee.com are priced at $0.02 per request with no API keys, no rate limits, and instant accesshttps://lowpaymentfee.com
- —USDC asset contract is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Base networkhttps://lowpaymentfee.com/api/v1/nfts/16/metadata