Query NFT ownership data via x402 micropayment on Base for $0.02 per request.
What it does
This endpoint at lowpaymentfee.com returns NFT ownership information for NFT ID 18. It is part of a broader suite of x402-protocol APIs offered by the same provider, spanning data analytics, AI/ML inference, finance/Web3, and infrastructure utilities. All endpoints on the platform share a uniform $0.02-per-request pricing model settled in USDC on the Base network.
The specific endpoint `/api/v1/nfts/18/owner` accepts POST requests and is gated by the x402 payment protocol. When called without payment, it returns a 402 challenge specifying the accepted payment scheme (exact), the USDC asset contract on Base (0x8335…2913), and a max amount of 20,000 base units (i.e., $0.02 given USDC's 6 decimals). Payment is sent to address 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3 with a 300-second timeout. The response MIME type is application/json.
No OpenAPI schema, request body schema, or response body schema is published beyond the x402 challenge metadata. The provider's landing page advertises no API keys, no rate limits, and instant access. Documentation pages (/api, /pricing, /README) all resolve to a minimal "Connect wallet" page with no additional technical detail. Because of this lack of documentation, the actual structure of the NFT owner response and any required POST body fields are unknown.
Capabilities
Use cases
- —Checking the current owner of a specific NFT (ID 18) programmatically
- —Integrating NFT ownership verification into agent workflows without API keys
- —Demonstrating x402 pay-per-call patterns for on-chain data retrieval
Fit
Best for
- —Agents needing one-off NFT ownership checks without subscription commitments
- —Developers experimenting with x402 micropayment protocol integrations
- —Lightweight NFT ownership verification where no API key management is desired
Not for
- —Bulk or batch NFT ownership queries across many token IDs (only NFT 18 is exposed at this path)
- —Use cases requiring detailed NFT metadata, transfer history, or collection-level data
- —Users who need comprehensive documentation or guaranteed SLAs
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/nfts/18/owner \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-header>"Endpoint
Quality
The endpoint is live and returns a valid x402 402 challenge, confirming it is operational. However, there is no published OpenAPI schema, no documented request/response body structure, and all documentation pages are empty beyond 'Connect wallet'. The endpoint path is hard-coded to a single NFT ID (18), limiting utility. Pricing is clear but everything else must be inferred.
Warnings
- —No request body schema documented — unknown what POST body fields (if any) are required
- —No response body schema documented — the structure of the NFT owner response is unknown
- —Documentation pages (/api, /pricing, /README) contain no useful content
- —Endpoint is scoped to a single NFT ID (18); no evidence of parameterized NFT lookup
Citations
- —The endpoint returns a 402 challenge with maxAmountRequired of 20000 base units in USDC on Base networkhttps://lowpaymentfee.com/api/v1/nfts/18/owner
- —USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/nfts/18/owner
- —All APIs on the platform are priced at $0.02 per request with no API keys, no rate limits, and instant accesshttps://lowpaymentfee.com
- —The provider offers endpoints across Data & Analytics, AI & ML, Finance & Web3, and Infrastructure categorieshttps://lowpaymentfee.com