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 57 via a pay-per-request x402 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 call (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 platform at lowpaymentfee.com that offers dozens of pay-per-call APIs spanning data analytics, AI/ML inference, finance/Web3 data, and utility services, all priced at $0.02 per request. This specific route (/api/v1/nfts/57/metadata) appears to be an NFT metadata service, though the exact schema of the returned metadata (e.g., name, image, attributes) is not documented. The platform advertises no minimums, no commitments, and instant access.
The x402 challenge was successfully captured with version 1, confirming the endpoint is live. The payment recipient is 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3 and the maximum timeout is 300 seconds. No OpenAPI spec, detailed documentation, or example responses were found in the crawl, so the exact structure of the metadata response remains unknown.
Capabilities
Use cases
- —Fetching metadata (name, image, attributes) for a specific NFT
- —Integrating NFT display data into wallets or marketplaces
- —Programmatic access to NFT metadata without API key management
- —Agent-driven NFT data retrieval with micropayments
Fit
Best for
- —Developers needing quick, keyless access to NFT metadata
- —AI agents that can settle x402 payments on Base
- —Applications that prefer pay-per-call over subscription billing
Not for
- —Bulk retrieval of metadata for large NFT collections (single token ID per endpoint)
- —Users who need free or subscription-based NFT metadata access
- —Querying metadata across multiple chains (Base only)
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/nfts/57/metadata \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-proof>"Endpoint
Quality
The x402 challenge is live and pricing is clear ($0.02 USDC on Base), but there is no OpenAPI spec, no documentation of request/response schemas, no example responses, and the endpoint is scoped to a single NFT token ID. The crawl pages beyond the homepage returned only 'Connect wallet' with no useful content.
Warnings
- —No OpenAPI or schema documentation available for this endpoint
- —Response format for NFT metadata is entirely undocumented — field names and structure are unknown
- —Endpoint is hardcoded to token ID 57; unclear if other token IDs are available at similar paths
- —Most crawled pages (api, pricing, README) returned no meaningful content
Citations
- —The endpoint returns a 402 challenge with x402Version 1, accepting USDC on Base with maxAmountRequired of 20000 base unitshttps://lowpaymentfee.com/api/v1/nfts/57/metadata
- —USDC asset contract is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Basehttps://lowpaymentfee.com/api/v1/nfts/57/metadata
- —Platform advertises $0.02 per request, no API keys, no rate limits, instant access on Base networkhttps://lowpaymentfee.com
- —Payment recipient address is 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3 with maxTimeoutSeconds of 300https://lowpaymentfee.com/api/v1/nfts/57/metadata