x402basequality 0.35

x402-gated NFT data endpoint on Base, pay $0.02 per request in USDC.

Price
0.02 USDC / call
Protocol
x402
Verified
no

What it does

This endpoint at `/api/v1/nfts/13` is part of the lowpaymentfee.com platform, a collection of x402-protocol pay-per-request APIs spanning data analytics, AI/ML inference, finance/Web3, and infrastructure utilities. The specific endpoint appears to serve NFT-related data (resource ID 13), though the exact response payload is not documented. Payment is settled on the Base network using USDC (contract `0x8335…2913`) via the x402 "exact" scheme.

The x402 challenge advertises a `maxAmountRequired` of 20,000 base units. Since USDC uses 6 decimals, this converts to $0.02 per request — consistent with the site-wide flat pricing of $0.02/request. The endpoint accepts POST requests, requires no API keys, and claims no rate limits. The payment recipient address is `0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3`, with a max timeout of 300 seconds.

Documentation is minimal: the landing page lists available endpoints and pricing, but there is no OpenAPI spec, no request/response schema, and no usage examples. The `/api`, `/pricing`, and `/README` pages all resolve to a "Connect wallet" prompt with no additional content. Because the NFT endpoint is not listed on the homepage (which focuses on analytics, AI, finance, and utility APIs), its exact functionality is unclear and must be treated as partially documented.

Capabilities

x402-paymentusdc-settlementbase-networknft-datapay-per-requestno-api-keypost-method

Use cases

  • Fetching NFT metadata or details for a specific token/collection
  • Integrating pay-per-request NFT data into agent workflows
  • Programmatic access to NFT information without API key management

Fit

Best for

  • Agents or bots that need on-demand NFT data without subscription overhead
  • Developers experimenting with x402 payment protocol integrations
  • Low-volume, pay-as-you-go NFT data retrieval

Not for

  • High-volume NFT data ingestion where per-call costs add up quickly
  • Use cases requiring well-documented request/response schemas upfront
  • Users who cannot pay in USDC on the Base network

Quick start

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

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 spec, no documented request/response schema, no examples, and the specific NFT endpoint is not even listed on the provider's homepage. Functionality must be guessed from the URL path alone.

Warnings

  • No OpenAPI or schema documentation available for this endpoint
  • The /api/v1/nfts/13 path is not listed among the provider's advertised endpoints on the homepage — its exact purpose is unknown
  • No response examples or field descriptions exist anywhere in the crawled material
  • The /api, /pricing, and /README pages return only a 'Connect wallet' prompt with no useful content

Citations

Provenance

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

Agent access