x402-gated NFT data endpoint on Base, pay $0.02 per request in USDC.
What it does
This endpoint at `/api/v1/nfts/38` is part of the lowpaymentfee.com platform, which offers a collection of x402-protocol pay-per-request APIs spanning data analytics, AI/ML inference, finance/Web3, and infrastructure utilities. The specific endpoint appears to serve NFT-related data (resource ID 38), though the exact response payload is not documented. Payment is settled on the Base network using USDC (contract `0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913`) via the x402 "exact" scheme.
The x402 challenge advertises a `maxAmountRequired` of 20,000 base units. USDC uses 6 decimals, so this translates to $0.02 per request — consistent with the site-wide flat pricing of $0.02/request shown on the landing page. The endpoint accepts POST requests and returns `application/json`. No API keys or rate limits are advertised; access is gated purely by the x402 payment header. The payment address is `0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3` with a max timeout of 300 seconds.
Documentation is extremely sparse. The landing page lists many endpoints across categories but provides no request/response schemas, parameter descriptions, or example payloads for any of them — including this NFT endpoint. The `/api`, `/pricing`, and `/README` pages all render only a "Connect wallet" prompt with no additional content. Without documentation of what data this endpoint returns or what parameters it accepts, usage requires experimentation.
Capabilities
Use cases
- —Fetching NFT metadata or details for a specific token/collection
- —Integrating NFT data into agent workflows without API key management
- —Programmatic pay-per-request access to NFT information on Base
Fit
Best for
- —Agents that can settle x402 payments in USDC on Base
- —Quick one-off NFT data lookups without subscription overhead
- —Developers experimenting with x402 protocol integrations
Not for
- —High-volume NFT data needs where per-request pricing adds up
- —Users who need detailed API documentation before integrating
- —Applications requiring non-USDC or non-Base payment rails
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/nfts/38 \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-header>"Endpoint
Quality
The endpoint is live and returns a valid x402 challenge with clear pricing, but there is zero documentation on request parameters, response schema, or what NFT data is actually returned. The /api, /pricing, and /README pages are empty. This is effectively a stub listing.
Warnings
- —No request or response schema documented for this endpoint
- —No examples or parameter descriptions available anywhere on the site
- —The specific data returned by /api/v1/nfts/38 is unknown — the endpoint name suggests NFT data but this is inferred
- —All documentation pages (/api, /pricing, /README) render only a 'Connect wallet' prompt with no content
Citations
- —Site-wide pricing is $0.02 per request with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —x402 challenge shows maxAmountRequired of 20000 base units in USDC on Base with exact schemehttps://lowpaymentfee.com/api/v1/nfts/38
- —USDC asset contract is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/nfts/38