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 47 at lowpaymentfee.com. It accepts POST requests and returns JSON. Payment is settled on the Base network using USDC (contract 0x8335…2913) with the x402 exact-payment scheme. The per-request cost is $0.02 (20,000 base units of USDC with 6 decimals). No API keys, accounts, or rate limits are required — callers simply attach an X-PAYMENT header with a valid x402 payment proof.
The provider (lowpaymentfee.com) hosts a broader catalog of pay-per-call APIs spanning data analytics, AI/ML inference, finance/Web3 data, and utility services, all priced at $0.02 per request on the same x402 infrastructure. This specific endpoint is scoped to NFT metadata retrieval. The response schema is not documented beyond the MIME type (application/json), so the exact shape of the returned metadata object is unknown.
Because there is no OpenAPI spec, no request/response schema documentation, and no sample payloads available, the precise fields accepted in the POST body and returned in the response cannot be confirmed from the crawled material. The endpoint is confirmed live via a 402 challenge captured during probing.
Capabilities
Use cases
- —Retrieving on-chain NFT metadata without needing an API key
- —Agent-driven NFT data lookups with micropayment settlement
- —Integrating NFT metadata into wallets or marketplaces via x402
Fit
Best for
- —Agents or apps that need NFT metadata with zero signup friction
- —Developers experimenting with x402 pay-per-call patterns on Base
- —Low-volume or sporadic NFT metadata queries where subscriptions are overkill
Not for
- —Bulk or high-throughput NFT indexing (no batch endpoint documented)
- —Users who need detailed request/response schema guarantees before integrating
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/nfts/47/metadata \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402_payment_proof>"Endpoint
Quality
The endpoint is confirmed live via a valid 402 challenge, and pricing is clear ($0.02 USDC on Base). However, there is no OpenAPI spec, no documented request body schema, no response schema, and no example payloads. The crawl pages beyond the homepage returned only 'Connect wallet' with no useful content. This is effectively a stub listing.
Warnings
- —No OpenAPI or schema documentation available — request and response formats are unknown.
- —No example request or response payloads could be sourced.
- —The endpoint is specific to NFT token ID 47; it is unclear whether other token IDs are supported at similar paths.
- —Provider site pages (/api, /pricing, /README) returned no useful content beyond a wallet-connect prompt.
Citations
- —Endpoint returns 402 with x402 challenge advertising USDC payment on Base networkhttps://lowpaymentfee.com/api/v1/nfts/47/metadata
- —maxAmountRequired is 20000 base units of USDC (6 decimals) = $0.02https://lowpaymentfee.com/api/v1/nfts/47/metadata
- —Provider advertises $0.02/request pricing with no API keys, no rate limits, and instant access on Basehttps://lowpaymentfee.com
- —USDC asset contract is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Basehttps://lowpaymentfee.com/api/v1/nfts/47/metadata