Query NFT ownership data via x402 micropayment on Base for $0.02 per request.
What it does
This endpoint at lowpaymentfee.com returns the owner of NFT #61 via a pay-per-call x402 protocol. The payment is settled on the Base network using USDC (contract 0x8335…2913). Each request costs a maximum of 20,000 base units of USDC, which at 6 decimals equals $0.02. No API keys, rate limits, or subscriptions are required — callers simply attach an X-PAYMENT header with a valid x402 payment proof.
The provider's landing page advertises a broad suite of APIs spanning data analytics, AI/ML inference, finance/Web3 data, and infrastructure utilities, all priced at $0.02 per request on the Base network. This specific endpoint (/api/v1/nfts/61/owner) falls under what appears to be an NFT data category, returning ownership information for a specific NFT. The endpoint accepts POST requests and returns application/json.
Documentation is minimal — the site offers no OpenAPI spec, no detailed request/response schemas, and the /api, /pricing, and /README pages all resolve to a bare "Connect wallet" prompt. The actual response format for this NFT owner endpoint is unknown beyond the declared MIME type. Callers should expect a JSON object containing an owner address, but the exact shape is unverified.
Capabilities
Use cases
- —Querying the current owner of a specific NFT without needing an API key
- —Integrating NFT ownership checks into agent workflows with automatic micropayments
- —Verifying NFT provenance or ownership in a Web3 application
Fit
Best for
- —AI agents that need on-demand NFT ownership data with no subscription
- —Developers prototyping x402 payment flows on Base
- —Low-volume NFT data lookups where per-call pricing is preferable to a subscription
Not for
- —High-volume NFT indexing across many collections (no bulk/batch endpoint documented)
- —Querying NFTs beyond ID 61 on this specific endpoint (path is hardcoded to NFT 61)
- —Users who need detailed NFT metadata beyond ownership
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/nfts/61/owner \
-H "X-PAYMENT: <x402-payment-proof>" \
-H "Content-Type: application/json"Endpoint
Quality
The endpoint is live and returns a valid x402 402 challenge with clear pricing. However, there is no OpenAPI spec, no documented request/response schema, no examples, and the broader site pages are empty beyond a wallet connect prompt. The specific functionality (NFT #61 owner) is narrow and undocumented.
Warnings
- —No OpenAPI or schema documentation available — request and response formats are unknown beyond MIME type application/json.
- —The endpoint path is hardcoded to NFT ID 61; it is unclear whether other NFT IDs are supported via similar paths.
- —The /api, /pricing, and /README pages all return only a 'Connect wallet' prompt with no useful documentation.
- —The provider lists many API categories on the landing page but none appear to include an explicit NFT section — this endpoint's purpose is inferred from the URL path alone.
Citations
- —Endpoint returns HTTP 402 with x402 challenge requiring USDC payment on Base networkhttps://lowpaymentfee.com/api/v1/nfts/61/owner
- —Max amount required is 20000 base units of USDC (6 decimals = $0.02)https://lowpaymentfee.com/api/v1/nfts/61/owner
- —USDC asset contract is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Basehttps://lowpaymentfee.com/api/v1/nfts/61/owner
- —Site advertises $0.02/request pricing with no API keys, no rate limits, and instant accesshttps://lowpaymentfee.com
- —Documentation pages (/api, /pricing, /README) contain only a 'Connect wallet' prompthttps://lowpaymentfee.com/api