NFT metadata endpoint on Base, pay-per-call via x402 with USDC at $0.02/request.
What it does
This x402-enabled endpoint serves NFT metadata for token ID 62 at lowpaymentfee.com. It accepts POST requests and returns JSON. Payment is settled on the Base network using USDC (contract 0x8335…2913) with an exact-payment scheme. The maximum amount required per call is 20,000 base units, which at 6 decimals equals $0.02 USD.
The endpoint is part of a broader platform (lowpaymentfee.com) that offers a variety of pay-per-request APIs spanning data analytics, AI/ML inference (sentiment analysis, summarization, classification, embeddings), finance/Web3 data (price feeds, exchange rates, token quotes, gas estimates), and infrastructure utilities (geocoding, validation, conversion, generation). All endpoints on the platform are priced at $0.02 per request with no API keys, no rate limits, and no minimum commitments.
This specific endpoint (/api/v1/nfts/62/metadata) returns metadata for a particular NFT. No OpenAPI schema or detailed documentation was found describing the request body format or the structure of the returned metadata. The endpoint is live and returns a proper 402 challenge when called without payment.
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 needing NFT metadata without API key management
- —Developers wanting pay-per-use NFT data on Base
- —Automated workflows that need instant access to NFT info
Not for
- —Bulk retrieval of metadata for large NFT collections (no batch endpoint documented)
- —Users who need metadata for NFTs beyond token ID 62 on this specific path
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/nfts/62/metadata \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-header>"Endpoint
Quality
The endpoint is live and returns a valid x402 challenge with clear pricing. However, there is no OpenAPI schema, no documentation on request/response structure, and no examples of the NFT metadata returned. The endpoint path is specific to a single NFT (ID 62), and the broader platform docs don't describe this NFT endpoint category at all.
Warnings
- —No OpenAPI or schema documentation available for this endpoint
- —No request body or response body examples found
- —The endpoint path is hardcoded to NFT ID 62; unclear if other IDs are supported at different paths
- —The NFT-related endpoints are not listed on the provider's landing page, which only shows analytics, AI, finance, and utility APIs
Citations
- —The endpoint returns a 402 challenge with maxAmountRequired of 20000 base units in USDC on Basehttps://lowpaymentfee.com/api/v1/nfts/62/metadata
- —All endpoints on the platform 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/62/metadata