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 serves NFT metadata for token ID 60 via a POST request. Payment is settled on the Base network using USDC (contract 0x8335…2913) through the x402 exact-payment scheme. The advertised maximum cost per request is 20,000 base units of USDC, which equals $0.02 (USDC uses 6 decimals). No API keys or rate limits are required — callers simply attach an X-PAYMENT header with a valid x402 payment proof.
The provider's landing page lists a broad catalog of pay-per-call APIs spanning 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 endpoints are priced uniformly at $0.02 per request. However, this specific listing covers only the `/api/v1/nfts/60/metadata` endpoint, which returns NFT metadata in JSON format.
Documentation is minimal: there is no OpenAPI spec, no request/response schema beyond the x402 challenge's outputSchema stub, and no example payloads. The endpoint is confirmed live (returns 402 with a well-formed x402 challenge), but the actual structure of the NFT metadata response is unknown.
Capabilities
Use cases
- —Retrieving metadata for a specific NFT (token 60) programmatically
- —Integrating NFT display data into wallets or marketplaces without API key management
- —Agent-driven NFT data lookups with micropayment settlement on Base
Fit
Best for
- —Developers needing keyless, pay-per-call NFT metadata access
- —AI agents that can settle x402 payments on Base
- —Projects already using USDC on Base that want frictionless API access
Not for
- —Bulk retrieval of metadata across many NFT collections (only token 60 is exposed at this path)
- —Users who need free or subscription-based API access
- —Applications requiring detailed documentation or guaranteed SLAs
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/nfts/60/metadata \
-H "X-PAYMENT: <x402-payment-proof>" \
-H "Content-Type: application/json"Endpoint
Quality
The endpoint is confirmed live with a valid x402 402 challenge, but there is no OpenAPI spec, no request body schema, no response examples, and no documentation beyond the landing page's generic catalog listing. The specific NFT metadata content and expected POST body are entirely unknown.
Warnings
- —No OpenAPI or schema documentation available for this endpoint
- —Request body format is undocumented — unclear what POST payload is expected
- —Response structure is unknown; no example metadata provided
- —Only token ID 60 is exposed at this specific path; generalizability unclear
- —Landing page lists many endpoints but none have detailed docs
Citations
- —Endpoint returns HTTP 402 with x402 challenge on Base network using USDChttps://lowpaymentfee.com/api/v1/nfts/60/metadata
- —Max amount required is 20000 base units of USDC (asset 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913)https://lowpaymentfee.com/api/v1/nfts/60/metadata
- —All endpoints priced at $0.02 per request with no API keys, no rate limitshttps://lowpaymentfee.com