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 #83 via a pay-per-call x402 protocol. The endpoint accepts POST requests and is settled in USDC on the Base network. The x402 challenge advertises a maxAmountRequired of 20,000 base units of USDC (6 decimals), which equals $0.02 per request. No API keys or rate limits are required — callers simply attach an X-PAYMENT header with a valid x402 payment proof.
The broader lowpaymentfee.com platform offers a suite of x402-gated APIs 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 with the same pay-per-use model on the Base network.
This specific endpoint (/api/v1/nfts/83/owner) appears to be an NFT ownership lookup. The response MIME type is application/json. No OpenAPI schema, detailed documentation, or example responses were found in the crawl, so the exact response structure is unknown. The endpoint is live and returning a proper 402 challenge.
Capabilities
Use cases
- —Querying the current owner of a specific NFT programmatically
- —Building NFT portfolio trackers that need ownership verification
- —Agent-driven workflows that need to verify NFT holders before executing actions
- —Integrating NFT ownership checks into marketplace or gallery applications
Fit
Best for
- —Developers needing simple pay-per-call NFT ownership queries without API key management
- —AI agents that can settle x402 payments on Base
- —Low-volume or sporadic NFT data lookups where subscription pricing is wasteful
Not for
- —Bulk or high-throughput NFT indexing across many collections (no batch endpoint documented)
- —Users who need historical ownership data or transfer history (only current owner is implied)
- —Non-crypto-native callers who cannot settle USDC payments on Base
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/nfts/83/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 is operational. However, there is no OpenAPI schema, no documented request/response format, no example payloads, and no detailed documentation beyond a generic landing page listing. The specific NFT endpoint is not even listed on the homepage. The actual behavior and response shape must be inferred entirely from the URL path and MIME type.
Warnings
- —No OpenAPI or schema documentation available for this endpoint
- —No example request or response bodies found in crawl
- —This specific NFT endpoint (/api/v1/nfts/83/owner) is not listed on the provider's homepage — it may be undocumented or experimental
- —The /api, /pricing, and /README pages all returned only 'Connect wallet' with no useful content
- —Response structure is completely unknown — only the MIME type (application/json) is confirmed
Citations
- —The endpoint returns a 402 x402 challenge with maxAmountRequired of 20000 base units of USDC on Basehttps://lowpaymentfee.com/api/v1/nfts/83/owner
- —USDC asset address is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Basehttps://lowpaymentfee.com/api/v1/nfts/83/owner
- —All listed APIs are priced at $0.02 per request with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com