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 a specific NFT (ID 64) 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 provider (lowpaymentfee.com) hosts a broader catalog of x402-gated APIs spanning data analytics, AI/ML inference, finance/Web3 data, and infrastructure utilities, all priced at $0.02 per request. This specific endpoint falls under the NFT/Web3 category and returns JSON. The payment is directed to address 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3 using USDC contract 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Base.
Documentation is minimal — the site's /api, /pricing, and /README pages all resolve to a "Connect wallet" prompt with no further technical detail. There is no OpenAPI spec, no request/response schema documentation, and no example payloads available. The endpoint is confirmed live (returns 402 with a well-formed x402 challenge), but the actual response format after payment is unknown.
Capabilities
Use cases
- —Looking up the current owner of a specific NFT programmatically
- —Integrating NFT ownership checks into agent workflows without API key management
- —Verifying NFT ownership as part of token-gated access logic
Fit
Best for
- —Agents needing on-demand NFT ownership data with no signup
- —Developers prototyping x402 payment flows on Base
- —Low-volume NFT ownership queries where per-call pricing is preferred
Not for
- —Bulk or high-throughput NFT indexing (no batch endpoint documented)
- —Querying arbitrary NFT IDs (this endpoint is hardcoded to NFT ID 64)
- —Users who need detailed NFT metadata beyond ownership
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/nfts/64/owner \
-H "X-PAYMENT: <x402_payment_proof>" \
-H "Content-Type: application/json"Endpoint
Quality
The endpoint is confirmed live with a valid x402 challenge and clear pricing ($0.02 USDC on Base). However, there is no OpenAPI spec, no request body schema, no response schema, and no documentation beyond a landing page listing. The endpoint path is specific to NFT ID 64 with no indication of parameterization. Effectively a stub listing.
Warnings
- —No OpenAPI spec or schema documentation available
- —No example request or response payloads — actual output format after payment is unknown
- —Endpoint path is hardcoded to NFT ID 64; unclear if other NFT IDs are supported via different paths
- —Site documentation pages (/api, /pricing, /README) all return only a 'Connect wallet' prompt with no useful content
- —The provider lists many API categories but none have detailed docs; quality of underlying data is unverifiable
Citations
- —Endpoint returns 402 with x402 challenge advertising maxAmountRequired of 20000 base units USDC on Basehttps://lowpaymentfee.com/api/v1/nfts/64/owner
- —USDC asset contract is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Basehttps://lowpaymentfee.com/api/v1/nfts/64/owner
- —All APIs priced at $0.02 per request with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —Provider hosts APIs across data analytics, AI/ML, finance/Web3, and infrastructure categorieshttps://lowpaymentfee.com