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 #62 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 or rate limits are required — callers simply attach an X-PAYMENT header with a valid x402 payment proof.
The endpoint accepts POST requests and returns JSON. It is part of a broader platform (lowpaymentfee.com) that offers dozens of pay-per-call APIs across categories including data analytics, AI/ML inference, finance/Web3, and infrastructure utilities, all priced at $0.02 per request. However, this specific endpoint is scoped to NFT owner lookups.
Documentation is minimal: there is no OpenAPI spec, no request/response schema beyond the x402 challenge's outputSchema stub, and the crawled pages beyond the landing page returned only wallet-connect prompts. The endpoint is confirmed live (402 challenge returned successfully), but the exact request body format and response structure are not documented in the available material.
Capabilities
Use cases
- —Look up the current owner of a specific NFT programmatically
- —Verify NFT ownership as part of a gating or access-control workflow
- —Integrate NFT owner data into dashboards or analytics pipelines
Fit
Best for
- —Agents or apps needing on-demand NFT ownership checks without managing API keys
- —Developers who want to pay per call in USDC on Base without subscriptions
- —Automated workflows that need low-cost, low-friction NFT data access
Not for
- —Bulk enumeration of all NFT owners across a collection (single-NFT endpoint, no batch support documented)
- —Users who need detailed NFT metadata beyond ownership (traits, images, history)
- —Applications requiring free or fiat-only payment rails
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/nfts/62/owner \
-H "X-PAYMENT: <x402_payment_proof>" \
-H "Content-Type: application/json"Endpoint
Quality
The endpoint is confirmed live via a valid 402 challenge, but there is no OpenAPI spec, no documented request/response schema, and no examples. The crawled docs pages returned only wallet-connect stubs. The endpoint's purpose (NFT owner lookup) is inferred from the URL path alone.
Warnings
- —No OpenAPI or request/response schema available — request body format and response structure are unknown.
- —Endpoint path is hardcoded to NFT #62; it is unclear whether other NFT IDs are supported via parameterized paths.
- —Documentation pages (/api, /pricing, /README) returned only 'Connect wallet' with no useful content.
- —The broader platform advertises many API categories but none of the other endpoints were probed or verified.
Citations
- —The x402 challenge returns maxAmountRequired of 20000 base units in USDC on Base network.https://lowpaymentfee.com/api/v1/nfts/62/owner
- —USDC asset address 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Base (6 decimals), so 20000 base units = $0.02.https://lowpaymentfee.com/api/v1/nfts/62/owner
- —Platform advertises $0.02/request pricing with no API keys, no rate limits, and instant access on Base network.https://lowpaymentfee.com
- —Platform lists APIs across data/analytics, AI/ML, finance/Web3, and infrastructure categories.https://lowpaymentfee.com