x402-gated NFT data endpoint on Base, pay $0.02 per request in USDC.
What it does
This endpoint at `/api/v1/nfts/29` is part of the lowpaymentfee.com platform, a collection of x402-protocol pay-per-call APIs spanning data analytics, AI/ML inference, finance/Web3, and infrastructure utilities. The specific resource appears to serve NFT-related data (inferred from the URL path `/nfts/29`), though the provider's landing page does not explicitly list this particular endpoint among its advertised APIs. The endpoint is live and returns a valid x402 challenge.
Pricing is $0.02 per request, paid in USDC on the Base network. The x402 challenge specifies a `maxAmountRequired` of 20,000 base units of USDC (contract `0x8335…2913`, 6 decimals), which equals $0.02. Payment is made via the `exact` scheme with no API keys, subscriptions, or rate limits required — callers simply attach an `X-PAYMENT` header with a valid x402 payment proof. The response MIME type is `application/json`.
The platform advertises a broad set of endpoints (analytics, AI sentiment/summarization/classification/embeddings, finance price feeds, crypto gas estimates, geocoding, validation, and more), all at the same $0.02 per-call price point. However, documentation beyond the landing page is essentially absent — the `/api`, `/pricing`, and `/README` routes all return only a "Connect wallet" prompt with no further technical detail. There is no OpenAPI spec, no request/response schema documentation, and no examples for any endpoint, including this one.
Capabilities
Use cases
- —Fetching NFT metadata or details for token ID 29 via a single paid request
- —Integrating pay-per-call NFT data into an agent workflow without managing API keys
- —Programmatic access to NFT information settled on Base L2 in USDC
Fit
Best for
- —Developers wanting zero-signup, pay-as-you-go NFT data access
- —AI agents that can settle x402 payments autonomously on Base
- —Prototyping workflows that need on-demand NFT information without rate limits
Not for
- —Production use cases requiring documented request/response schemas and SLAs
- —Bulk NFT data retrieval where per-call costs would accumulate significantly
- —Users who cannot transact in USDC on the Base network
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/nfts/29 \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-proof>"Endpoint
Quality
The endpoint is live and returns a valid x402 challenge with clear pricing, but there is zero documentation on what this NFT endpoint accepts or returns. The /nfts/29 path is not listed on the provider's own landing page, and no OpenAPI spec, examples, or response schemas are available. This is effectively a stub listing.
Warnings
- —The /api/v1/nfts/29 endpoint is not listed among the provider's advertised APIs on the landing page — its purpose and data content are inferred solely from the URL path.
- —No request or response schema documentation exists for any endpoint on this platform.
- —The /api, /pricing, and /README pages all return only a 'Connect wallet' prompt with no useful content.
- —Without documented response schemas, callers cannot know what fields or data structure to expect.
Citations
- —The endpoint returns a valid x402 challenge with maxAmountRequired of 20000 base units of USDC on Basehttps://lowpaymentfee.com/api/v1/nfts/29
- —USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/nfts/29
- —Platform advertises $0.02 per request with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —The landing page lists analytics, AI/ML, finance/Web3, and infrastructure endpoints but does not list /api/v1/nfts/29https://lowpaymentfee.com