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 #49. It is part of a broader platform offering pay-per-request APIs across data analytics, AI/ML, finance/Web3, and infrastructure categories — all priced at $0.02 per call and settled via x402 using USDC on the Base network.
The specific endpoint `/api/v1/nfts/49/owner` accepts POST requests and returns JSON. Payment is handled inline via the x402 protocol: callers include an `X-PAYMENT` header with a signed payment of up to 20,000 base units of USDC (i.e., $0.02, since USDC uses 6 decimals). No API keys, accounts, or rate limits are advertised — access is gated purely by micropayment. The payment is directed to address `0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3` on Base, using the USDC contract at `0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913`.
Documentation is minimal. The landing page lists many endpoints but provides no request/response schemas, example payloads, or detailed descriptions of what data is returned. The NFT endpoint path suggests it returns the owner address of a specific NFT (ID 49), but the collection, contract, or chain being queried is not documented. The platform appears to be a demonstration or early-stage x402 API marketplace.
Capabilities
Use cases
- —Querying the current owner of a specific NFT programmatically
- —Integrating NFT ownership checks into agent workflows without API key management
- —Paying per-request for on-chain data lookups using USDC on Base
Fit
Best for
- —Agents needing one-off NFT ownership queries without subscription commitments
- —Developers prototyping x402-based payment flows
- —Low-volume, on-demand NFT data retrieval
Not for
- —Bulk or high-throughput NFT indexing (no batch endpoint documented)
- —Querying arbitrary NFT collections or IDs (endpoint is hardcoded to NFT #49)
- —Users who need detailed NFT metadata beyond ownership
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/nfts/49/owner \
-H "X-PAYMENT: <x402-signed-payment>" \
-H "Content-Type: application/json"Endpoint
Quality
The endpoint is live and returns a valid x402 challenge, confirming it is operational. However, there is no documentation on request parameters, response schema, which NFT collection is being queried, or any example payloads. The endpoint path is hardcoded to a single NFT ID, limiting utility. Effectively a stub listing.
Warnings
- —No request or response schema documented — callers must guess at the payload format.
- —The endpoint is specific to NFT #49; it is unclear how to query other NFT IDs or collections.
- —The underlying NFT collection/contract being queried is not identified anywhere in the docs.
- —Landing page lists many API categories but /api, /pricing, and /README pages are empty (just 'Connect wallet').
Citations
- —Endpoint returns HTTP 402 with x402 challenge requiring USDC payment on Basehttps://lowpaymentfee.com/api/v1/nfts/49/owner
- —Platform advertises $0.02 per request, no API keys, no rate limits, Base networkhttps://lowpaymentfee.com
- —USDC asset contract is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Basehttps://lowpaymentfee.com/api/v1/nfts/49/owner
- —maxAmountRequired is 20000 base units (= $0.02 with 6 decimals)https://lowpaymentfee.com/api/v1/nfts/49/owner