NFT metadata endpoint on Base, pay-per-call via x402 with USDC at $0.02/request.
What it does
This endpoint at lowpaymentfee.com serves NFT metadata for token ID 67 via a POST request, gated by the x402 payment protocol. Each call costs $0.02 in USDC on the Base network (maxAmountRequired of 20,000 base units with 6 decimals = $0.02). No API keys or accounts are required — callers attach an X-PAYMENT header with a valid x402 payment proof and receive JSON metadata in return.
The provider, lowpaymentfee.com, hosts a broader suite of pay-per-call APIs spanning data analytics, AI/ML inference, finance/Web3 data, and utility services, all priced at $0.02 per request and settled in USDC on Base. This specific endpoint is part of an NFT-related resource path (`/api/v1/nfts/67/metadata`), though the exact schema of the returned metadata is not documented. The x402 challenge confirms the endpoint is live, accepts the "exact" payment scheme, and responds with `application/json` content.
Because no OpenAPI spec, request/response schema, or detailed documentation is available beyond the x402 challenge and the provider's landing page, the actual structure of the NFT metadata response and any POST body parameters remain unknown. Callers should expect standard NFT metadata fields (name, description, image, attributes) but this is an inference, not a documented guarantee.
Capabilities
Use cases
- —Fetching NFT metadata for token ID 67 from this provider
- —Demonstrating x402 micropayment-gated API access
- —Integrating pay-per-call NFT data into agent workflows
- —Building walletless NFT explorers that pay per query
Fit
Best for
- —Agents or apps needing NFT metadata with no signup or API key
- —Developers experimenting with x402 payment protocol on Base
- —Low-volume, on-demand NFT data retrieval
Not for
- —Bulk NFT metadata scraping across many collections
- —Users without USDC on Base network
- —Applications requiring well-documented response schemas
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/nfts/67/metadata \
-H "X-PAYMENT: <x402_payment_proof>" \
-H "Content-Type: application/json"Endpoint
Quality
The x402 challenge confirms the endpoint is live and pricing is clear ($0.02 USDC on Base). However, there is no OpenAPI spec, no documented request body schema, no example response, and no description of what NFT metadata is actually returned. The endpoint is effectively a stub listing with minimal information.
Warnings
- —No OpenAPI or schema documentation available — request and response formats are unknown
- —The specific NFT (token ID 67) purpose and collection are undocumented
- —No examples of successful responses are available
- —Other pages on the site (pricing, README, api) returned only 'Connect wallet' with no useful content
Citations
- —Endpoint returns HTTP 402 with x402 challenge, confirming it is livehttps://lowpaymentfee.com/api/v1/nfts/67/metadata
- —maxAmountRequired is 20000 base units of USDC (6 decimals) = $0.02 per request on Basehttps://lowpaymentfee.com/api/v1/nfts/67/metadata
- —Provider advertises $0.02/request pricing with no API keys, no rate limits, instant access on Base networkhttps://lowpaymentfee.com
- —Asset address 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 is USDC on Basehttps://lowpaymentfee.com/api/v1/nfts/67/metadata