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 #68. It is part of a broader suite of pay-per-call APIs offered by the same provider, all settled via the x402 protocol on the Base network using USDC. The specific endpoint `/api/v1/nfts/68/owner` accepts POST requests and returns JSON.
The x402 challenge confirms the endpoint is live and requires a payment of up to 20,000 base units of USDC (0x8335…2913 on Base), which equals $0.02 per request (USDC uses 6 decimals). No API keys or rate limits are advertised — access is gated purely by micropayment. The provider's landing page lists many other endpoints across data/analytics, AI/ML, finance/Web3, and infrastructure categories, all at the same $0.02 price point.
Documentation is minimal: there is no OpenAPI spec, no request/response schema beyond the x402 outputSchema stub, and the crawled /api, /pricing, and /README pages all returned only a "Connect wallet" prompt with no additional detail. The actual response format for the NFT owner query is not documented, so consumers should expect a JSON object but cannot confirm its exact shape without making a paid call.
Capabilities
Use cases
- —Querying the current owner of a specific NFT programmatically
- —Integrating NFT ownership checks into agent workflows without API key management
- —Verifying NFT holder status before granting access or rewards
Fit
Best for
- —Agents or bots that need on-demand NFT ownership data without subscription overhead
- —Developers prototyping NFT-gated features who want instant, keyless access
- —Low-volume or sporadic NFT ownership queries where pay-per-call is cost-effective
Not for
- —Bulk or high-frequency NFT indexing across many token IDs (only NFT #68 is exposed at this path)
- —Users who need detailed NFT metadata, transaction history, or collection-level analytics
- —Anyone without a Base-compatible USDC wallet for x402 payments
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/nfts/68/owner \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402_payment_token>"Endpoint
Quality
The endpoint is live (402 challenge confirmed) and pricing is clear ($0.02 USDC on Base). However, there is no OpenAPI spec, no documented request body schema, no example response, and the crawled pages beyond the landing page are empty. The endpoint is also scoped to a single NFT ID (68), limiting general utility. Effectively a stub listing.
Warnings
- —No OpenAPI or request/response schema available — actual response format is unknown.
- —Endpoint is hardcoded to NFT #68; no documentation on whether other NFT IDs are supported at different paths.
- —Provider docs pages (/api, /pricing, /README) returned no useful content beyond a wallet-connect prompt.
- —The provider lists many endpoint categories (AI, finance, infrastructure) but this specific endpoint only covers NFT ownership.
Citations
- —The x402 challenge returns maxAmountRequired of 20000 base units of USDC on Base, equaling $0.02 per request.https://lowpaymentfee.com/api/v1/nfts/68/owner
- —The provider advertises $0.02 per request with no API keys, no rate limits, and instant access on Base network.https://lowpaymentfee.com
- —The USDC asset address is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Base.https://lowpaymentfee.com/api/v1/nfts/68/owner