NFT metadata endpoint on Base, pay-per-call via x402 with USDC (~$0.02/request).
What it does
This endpoint serves NFT metadata for token ID 83 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 amount of 20,000 base units — which, at 6 decimals for USDC, equals $0.02 per request.
The endpoint is part of a broader platform at lowpaymentfee.com that offers a variety of pay-per-call APIs spanning data & analytics, AI/ML inference, finance & Web3, and infrastructure utilities — all priced at $0.02 per request. The platform advertises no API keys, no rate limits, and instant access; callers authenticate and pay solely through the x402 payment header.
Because this specific endpoint path targets `/nfts/83/metadata`, it appears to return metadata for a single NFT (token 83). 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 `application/json`. The x402 challenge is live and well-formed, confirming the endpoint is operational.
Capabilities
Use cases
- —Retrieving on-chain NFT metadata for display in wallets or marketplaces
- —Programmatic access to NFT attributes for indexing or analytics
- —Agent-driven NFT data retrieval with automatic micropayment
Fit
Best for
- —Agents or bots that need NFT metadata without managing API keys
- —Developers wanting pay-as-you-go NFT data on Base
- —Low-volume or sporadic NFT metadata lookups at $0.02 each
Not for
- —Bulk NFT metadata scraping (no documented batch endpoint; per-call cost adds up)
- —Users who need metadata for arbitrary token IDs (this endpoint is scoped to token 83)
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/nfts/83/metadata \
-H "X-PAYMENT: <x402-payment-header>" \
-H "Content-Type: application/json"Endpoint
Quality
The x402 challenge is live and well-formed, confirming the endpoint works and pricing is clear ($0.02 USDC on Base). However, there is no OpenAPI spec, no request/response schema, no example payloads, and no documentation beyond the landing page listing. The endpoint is scoped to a single NFT token ID with no explanation of what metadata is returned.
Warnings
- —No OpenAPI or request/response schema available — exact request body and response fields are unknown.
- —Endpoint is hardcoded to token ID 83; unclear whether other token IDs are available at similar paths.
- —Landing page lists many API categories but crawled sub-pages (/api, /pricing, /README) returned only 'Connect wallet' with no useful content.
- —No documentation on error handling, response format, or supported POST body fields.
Citations
- —The x402 challenge returns maxAmountRequired of 20000 in USDC (6 decimals) on Base, equaling $0.02 per request.https://lowpaymentfee.com/api/v1/nfts/83/metadata
- —The platform advertises $0.02/request pricing with no API keys, no rate limits, and instant access on Base network.https://lowpaymentfee.com
- —USDC asset contract is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Base.https://lowpaymentfee.com/api/v1/nfts/83/metadata