x402-gated NFT data endpoint on Base, pay $0.02 per request in USDC.
What it does
This endpoint at `/api/v1/nfts/60` 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 at path `/nfts/60` appears to serve NFT-related data (likely for NFT ID 60), though the provider's landing page labels it generically as "Premium API Access" without further documentation on the response payload.
The endpoint is live and returns a valid x402 challenge. Payment is settled on the Base network using USDC (contract `0x8335…2913`) with a maximum amount of 20,000 base units, which equals $0.02 (USDC uses 6 decimals). The payment scheme is "exact," meaning the caller pays a fixed amount per request. No API keys or rate limits are advertised — access is gated entirely by the x402 payment header. The endpoint accepts POST requests.
Documentation is minimal. The provider's homepage lists many endpoints at $0.02 each across categories but does not include `/api/v1/nfts/60` in the visible catalog, nor does it describe request parameters or response schemas for any endpoint. The `/api`, `/pricing`, and `/README` pages all resolve to a bare "Connect wallet" prompt with no additional content. Without an OpenAPI spec, example responses, or detailed docs, the actual data returned by this endpoint remains unclear.
Capabilities
Use cases
- —Fetching NFT metadata or details for a specific token ID via a single paid call
- —Integrating NFT data into an agent workflow without managing API keys
- —Programmatic access to NFT information settled on-chain via USDC on Base
Fit
Best for
- —Agents or bots that need keyless, pay-per-call NFT data access
- —Developers experimenting with x402 protocol integrations
- —Micro-payment workflows where $0.02 per request is acceptable
Not for
- —Bulk NFT data retrieval (no documented batch endpoints or volume discounts)
- —Users who need detailed documentation or guaranteed SLAs before integrating
- —Non-crypto-native callers who cannot construct x402 payment headers
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/nfts/60 \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-token>"Endpoint
Quality
The endpoint is live and returns a valid x402 challenge, but there is no OpenAPI spec, no documented request/response schema, no example payloads, and the specific /nfts/60 path is not even listed on the provider's own homepage. The description is generic ("Premium API Access") and provides no insight into what data is actually returned. Effectively a stub listing.
Warnings
- —No OpenAPI or schema documentation available for this endpoint
- —The /api/v1/nfts/60 path is not listed on the provider's homepage catalog — purpose is inferred from the URL path only
- —Response format and fields are completely unknown; no example responses available
- —Provider's /api, /pricing, and /README pages are empty beyond a wallet-connect prompt
- —Cannot confirm what data (if any) is actually returned after payment
Citations
- —The endpoint returns a valid x402 challenge with maxAmountRequired of 20000 base units in USDC on Basehttps://lowpaymentfee.com/api/v1/nfts/60
- —USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/nfts/60
- —Platform advertises $0.02 per request, no API keys, no rate limits, instant access on Base networkhttps://lowpaymentfee.com
- —The /api/v1/nfts/60 endpoint is not listed among the available APIs on the homepagehttps://lowpaymentfee.com