x402-gated NFT data endpoint on Base, pay $0.02 per request in USDC.
What it does
This endpoint at `/api/v1/nfts/17` is part of the lowpaymentfee.com platform, which offers a broad suite of x402-protocol pay-per-call APIs spanning data analytics, AI/ML inference, finance/Web3, and infrastructure utilities. The specific resource at `/nfts/17` is labeled "Premium API Access" and returns JSON content. It is gated via the x402 payment protocol on the Base network, accepting USDC (contract 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913) with a maximum charge of $0.02 per request (20,000 base units at 6 decimals).
The platform advertises a uniform $0.02/request pricing model across all its endpoints, with no API keys, no rate limits, and no minimum commitments. Payment is handled entirely through the x402 `X-PAYMENT` header mechanism (version 1, scheme "exact"). The endpoint accepts HTTP POST and is marked as discoverable. The payment recipient address is 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3 with a 300-second payment timeout.
Note: The exact data returned by `/api/v1/nfts/17` is not documented. The endpoint name and path suggest NFT-related data (possibly metadata or details for NFT ID 17), but no output schema or example response is provided in the crawled material. The broader platform lists many endpoint categories but the NFT endpoints are not explicitly listed on the homepage, so the precise functionality should be verified by making a paid request.
Capabilities
Use cases
- —Fetching NFT data or metadata on demand without needing an API key
- —Integrating pay-per-call NFT lookups into agent workflows via x402
- —Programmatic access to NFT information settled in USDC on Base
Fit
Best for
- —Agents or bots that need keyless, on-demand NFT data access
- —Developers prototyping x402 payment flows with low-cost endpoints
- —Micro-payment use cases where $0.02/request is acceptable
Not for
- —High-volume NFT indexing where per-request fees would accumulate significantly
- —Users who need detailed documentation or guaranteed SLAs before integrating
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/nfts/17 \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-token>"Endpoint
Quality
The endpoint is live and returns a valid x402 402 challenge, confirming it is operational. However, there is no documentation of the request body schema, response schema, or what data `/api/v1/nfts/17` actually returns. The NFT endpoint category is not even listed on the provider's homepage. This is effectively a stub listing with confirmed liveness but minimal usable documentation.
Warnings
- —No output schema or example response available for this endpoint
- —The /api/v1/nfts/ path is not listed among the provider's documented API categories on the homepage
- —No request body schema documented; unclear what POST body (if any) is expected
- —Provider pages (/api, /pricing, /README) returned only 'Connect wallet' with no useful content
Citations
- —Endpoint returns HTTP 402 with x402 version 1 challenge, scheme exact, on Base networkhttps://lowpaymentfee.com/api/v1/nfts/17
- —USDC asset contract is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/nfts/17
- —maxAmountRequired is 20000 base units (= $0.02 USDC at 6 decimals)https://lowpaymentfee.com/api/v1/nfts/17
- —Platform advertises $0.02/request uniform pricing with no API keys, no rate limitshttps://lowpaymentfee.com