x402basequality 0.35

Query NFT ownership data via x402 micropayment on Base for $0.02 per request.

Price
0.02 USDC / call
Protocol
x402
Verified
no

What it does

This endpoint at lowpaymentfee.com returns NFT ownership information for NFT #27. It is part of a broader suite of x402-protocol APIs offered by the same provider, spanning data analytics, AI/ML inference, finance/Web3 data, and infrastructure utilities. All endpoints on the platform share a uniform pricing model of $0.02 per request, settled in USDC on the Base network.

The specific endpoint `/api/v1/nfts/27/owner` accepts POST requests and returns JSON. Payment is handled via the x402 protocol: callers must include an `X-PAYMENT` header with a valid payment proof. The x402 challenge advertises a maxAmountRequired of 20,000 base units of USDC (0x8335…2913 on Base), which equals $0.02 given USDC's 6 decimal places. No API keys or rate limits are advertised; access is gated purely by per-request micropayment.

Documentation is minimal. The provider's landing page lists many API categories but provides no detailed schema, request/response examples, or parameter documentation for any endpoint. The NFT endpoint path suggests it returns owner data for a specific NFT identified by ID 27, but the exact response shape is undocumented. The provider accepts payments to address 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3 with a 300-second payment timeout.

Capabilities

nft-ownership-queryx402-micropaymentusdc-paymentbase-networkper-request-pricingno-api-keyjson-response

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 NFT data without subscriptions or rate limits

Fit

Best for

  • Agents needing on-demand NFT ownership data with no signup
  • Developers prototyping NFT-aware applications with micropayments
  • Low-volume or sporadic NFT data lookups where per-call pricing is economical

Not for

  • Bulk NFT collection scanning across thousands of token IDs
  • Applications requiring detailed NFT metadata, traits, or transaction history beyond ownership

Quick start

curl -X POST https://lowpaymentfee.com/api/v1/nfts/27/owner \
  -H "X-PAYMENT: <x402-payment-proof>" \
  -H "Content-Type: application/json"

Endpoint

Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.35/ 1.00

The endpoint is live (402 challenge captured) and pricing is clear ($0.02 USDC on Base), but there is no OpenAPI schema, no request/response examples, and no documentation beyond the landing page listing. The specific NFT endpoint isn't even listed on the provider's homepage—only generic categories are shown. Response format and parameters are entirely unknown.

Warnings

  • No API documentation or schema available for this specific endpoint
  • The endpoint path /api/v1/nfts/27/owner is not listed on the provider's landing page; only broader categories are shown
  • No request body schema or response schema documented anywhere
  • Provider pages (/api, /pricing, /README) all return only a 'Connect wallet' prompt with no useful content

Citations

Provenance

Indexed fromx402_bazaar
Enriched2026-04-21 23:31:55Z · anthropic/claude-opus-4.6 · v2
First seen2026-04-21
Last seen2026-04-22

Agent access