x402basequality 0.35

NFT metadata endpoint on Base, pay-per-call via x402 with USDC (~$0.02/request).

Price
0.02 USDC / call
Protocol
x402
Verified
no

What it does

This endpoint at lowpaymentfee.com serves NFT metadata for token ID 33 via a POST request, gated by the x402 payment protocol. Each call costs up to 20,000 base units of USDC on the Base network, which equals $0.02 (USD Coin uses 6 decimals). No API keys or accounts are required — callers simply attach an X-PAYMENT header with a valid x402 payment proof.

The endpoint is part of a broader platform (lowpaymentfee.com) that offers multiple pay-per-call API categories including data analytics, AI/ML inference (sentiment analysis, summarization, classification, embeddings), finance/Web3 data (price feeds, exchange rates, token quotes, gas estimates), and infrastructure utilities (geocoding, validation, conversion, generation). All endpoints on the platform are advertised at $0.02 per request, settled in USDC on the Base L2 network.

The specific endpoint `/api/v1/nfts/33/metadata` returns application/json content. The x402 challenge confirms the endpoint is live, accepts the "exact" payment scheme, and pays out to address 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3. No OpenAPI schema or detailed documentation for the response format was found in the crawl, so the exact structure of the returned NFT metadata is unknown.

Capabilities

nft-metadatax402-paymentusdc-settlementbase-networkpay-per-callno-api-key

Use cases

  • Retrieving metadata for NFT token ID 33 from this provider
  • Demonstrating x402 micropayment-gated API access
  • Integrating NFT metadata into agent workflows without API key management

Fit

Best for

  • Agents needing NFT metadata with no-signup, pay-per-call access
  • Developers experimenting with x402 payment protocol on Base
  • Automated pipelines that need instant API access without rate limits

Not for

  • Bulk retrieval of metadata across many NFT collections (only token 33 is at this path)
  • Users who need free or subscription-based NFT metadata APIs
  • Production systems requiring documented response schemas and SLAs

Quick start

curl -X POST https://lowpaymentfee.com/api/v1/nfts/33/metadata \
  -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 confirmed) and pricing is clear ($0.02 USDC on Base). However, there is no OpenAPI schema, no documentation of request parameters or response format, and no example responses. The endpoint serves a single NFT token ID with no broader context on what metadata is returned.

Warnings

  • No OpenAPI or response schema available — the structure of the returned NFT metadata is unknown.
  • Only token ID 33 is addressed by this specific endpoint path; unclear if other token IDs are supported at different paths.
  • The /api, /pricing, and /README pages all returned only 'Connect wallet' with no useful documentation.
  • No robots.txt or agents.txt found on the origin.

Citations

Provenance

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

Agent access