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 #71 via a pay-per-call x402 protocol. The payment is settled in USDC on the Base network. The x402 challenge advertises a maxAmountRequired of 20,000 base units; since USDC uses 6 decimals, this equals $0.02 per request. No API keys, rate limits, or subscriptions are required — callers simply attach an X-PAYMENT header with a valid x402 payment proof.
The broader lowpaymentfee.com platform hosts a variety of x402-gated endpoints spanning data analytics, AI/ML inference (sentiment analysis, summarization, classification, embeddings), finance/Web3 data (price feeds, exchange rates, token quotes, gas estimates), and infrastructure utilities (geocoding, validation, conversion, generation). All endpoints are listed at $0.02 per request and settle on the Base network in USDC.
This specific endpoint (/api/v1/nfts/71/owner) is a POST endpoint that returns JSON. The exact response schema is not documented, so the structure of the owner data returned is unknown. The endpoint is live and returning a proper 402 challenge as expected for x402 protocol.
Capabilities
Use cases
- —Querying the current owner of a specific NFT programmatically
- —Building NFT portfolio dashboards that need ownership verification
- —Agent-driven workflows that need to verify NFT ownership before taking action
Fit
Best for
- —Agents needing quick NFT ownership checks without API key setup
- —Pay-per-use NFT data queries settled in USDC on Base
- —Lightweight integrations that want to avoid subscription overhead
Not for
- —Bulk enumeration of all NFT owners across a collection (single-NFT endpoint)
- —Querying NFTs on networks other than Base
- —Users who need detailed NFT metadata beyond ownership
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/nfts/71/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, confirming it works. However, there is no OpenAPI schema, no documented request body format, no example response, and the endpoint path is hardcoded to NFT #71 with no indication of parameterization. The crawl pages beyond the homepage returned only 'Connect wallet' with no useful documentation.
Warnings
- —No response schema or example response documented — the structure of the returned owner data is unknown.
- —No request body schema documented — unclear what (if any) POST body is expected.
- —Endpoint path is hardcoded to NFT #71; it is unclear whether other NFT IDs are supported or how to parameterize.
- —Documentation pages (/api, /pricing, /README) returned no useful content beyond 'Connect wallet'.
- —The platform lists many endpoint categories but none appear to have detailed docs.
Citations
- —The x402 challenge advertises maxAmountRequired of 20000 base units in USDC on Base networkhttps://lowpaymentfee.com/api/v1/nfts/71/owner
- —USDC asset address 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Basehttps://lowpaymentfee.com/api/v1/nfts/71/owner
- —All endpoints priced at $0.02 per request with no API keys, no rate limits, instant access on Base networkhttps://lowpaymentfee.com
- —Platform offers endpoints across Data & Analytics, AI & ML, Finance & Web3, and Infrastructure categorieshttps://lowpaymentfee.com