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 72 via a POST request, gated behind 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 needed — 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 (sentiment, summarization, classification, embeddings), finance/Web3 data (price feeds, exchange rates, gas estimates), and infrastructure utilities (geocoding, validation, conversion). All endpoints share the same $0.02/request pricing model, settle in USDC on Base, and require no rate-limit management or subscription. However, this specific listing covers only the NFT metadata endpoint at /api/v1/nfts/72/metadata.
The endpoint is live and returns a proper 402 challenge with x402 version 1. No OpenAPI schema or detailed documentation was found beyond the landing page listing. The actual structure of the NFT metadata response is unknown — the outputSchema only specifies the HTTP method (POST) and discoverability flag. Callers should expect a JSON response but should verify the payload shape empirically.
Capabilities
Use cases
- —Fetching metadata for NFT token #72 programmatically
- —Integrating NFT display data into wallets or marketplaces
- —Agent-driven NFT data retrieval with micropayments
- —Demonstrating x402 payment-gated API access
Fit
Best for
- —Developers needing on-demand NFT metadata without API key management
- —AI agents that can settle x402 payments on Base
- —Projects exploring micropayment-gated API patterns
Not for
- —Bulk retrieval of metadata across many NFT collections (only token 72 is documented)
- —Users who cannot transact in USDC on the Base network
- —Applications requiring detailed OpenAPI documentation or guaranteed SLAs
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/nfts/72/metadata \
-H "X-PAYMENT: <x402_payment_proof>" \
-H "Content-Type: application/json"Endpoint
Quality
The endpoint is live and returns a valid x402 402 challenge, confirming it is operational. However, there is no OpenAPI schema, no documentation of request/response bodies, and the NFT metadata content is entirely unknown. The listing is effectively a stub with pricing and liveness confirmed but little else.
Warnings
- —No OpenAPI or detailed documentation available for this endpoint
- —Response schema for NFT metadata is unknown — outputSchema only specifies HTTP method
- —Only token ID 72 is referenced; unclear if other token IDs are supported at similar paths
- —The broader site lists many API categories but none have detailed docs beyond the landing page
Citations
- —Endpoint returns HTTP 402 with x402 version 1 challenge, confirming it is livehttps://lowpaymentfee.com/api/v1/nfts/72/metadata
- —maxAmountRequired is 20000 base units of USDC (asset 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913) on Base network, equaling $0.02https://lowpaymentfee.com/api/v1/nfts/72/metadata
- —All endpoints priced at $0.02/request with no API keys, no rate limits, and instant access on Basehttps://lowpaymentfee.com