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 #16. It is part of a broader platform offering pay-per-call APIs across data analytics, AI/ML inference, finance/Web3, and infrastructure categories — all settled via the x402 protocol on the Base network using USDC.
The specific endpoint `/api/v1/nfts/16/owner` accepts POST requests and returns JSON. Payment is handled inline via the X-PAYMENT header using the x402 exact scheme. The maximum amount required is 20,000 base units of USDC (0x8335…2913 on Base), which equals $0.02 per request. There are no API keys, no rate limits, and no subscription commitments — callers pay per request with USDC on Base.
The platform advertises a uniform $0.02/request pricing across all its endpoints. The x402 challenge is live and well-formed, with a 300-second payment timeout. Note that while the landing page lists many endpoint categories (analytics, AI, finance, infrastructure), this specific listing covers only the NFT owner lookup endpoint. Documentation beyond the landing page is sparse — the /api, /pricing, and /README pages all resolve to a wallet-connect stub with no additional technical detail.
Capabilities
Use cases
- —Querying the current owner of a specific NFT programmatically
- —Building NFT portfolio dashboards that need ownership verification
- —Agent workflows that need to verify NFT ownership before executing downstream logic
Fit
Best for
- —Agents needing simple per-call NFT ownership checks without API key management
- —Developers who want to pay with USDC on Base without subscriptions
- —Low-volume or sporadic NFT data lookups where $0.02/call is cost-effective
Not for
- —High-volume bulk NFT ownership scans across thousands of tokens (no batch endpoint documented)
- —Users who need detailed NFT metadata, traits, or transaction history beyond ownership
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/nfts/16/owner \
-H "X-PAYMENT: <x402-payment-token>" \
-H "Content-Type: application/json"Endpoint
Quality
The x402 challenge is live and well-formed, confirming the endpoint exists and accepts payment. However, there is no OpenAPI schema, no documented request/response body, no examples, and no meaningful documentation beyond a landing page listing. The endpoint's actual behavior (what it returns, what input it expects) must be entirely inferred from the URL path.
Warnings
- —No API documentation available — /api, /pricing, and /README all return only a wallet-connect stub with no technical content.
- —No request or response schema is documented; the input/output format is unknown beyond 'application/json'.
- —The endpoint path is hardcoded to NFT #16; it is unclear whether other NFT IDs are supported or how to discover them.
- —The platform lists many endpoint categories (AI, analytics, finance, infrastructure) but none have documented schemas or examples.
Citations
- —The endpoint returns HTTP 402 with an x402 challenge requiring 20,000 base units of USDC on Basehttps://lowpaymentfee.com/api/v1/nfts/16/owner
- —USDC asset address is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Basehttps://lowpaymentfee.com/api/v1/nfts/16/owner
- —Platform advertises $0.02/request uniform pricing with no API keys, no rate limits, and instant accesshttps://lowpaymentfee.com
- —Payment timeout is 300 secondshttps://lowpaymentfee.com/api/v1/nfts/16/owner