x402basequality 0.30

Pay-per-call premium API access on Base via x402 — $0.02/request in USDC.

Price
0.02 USDC / call
Protocol
x402
Verified
no
Endpoint
https://lowpaymentfee.com/api/v1/inbox/167

What it does

This endpoint at lowpaymentfee.com provides "Premium API Access" via the x402 payment protocol. The specific path `/api/v1/inbox/167` is one of many endpoints offered by the platform, which advertises a broad catalog spanning data & analytics, AI & machine learning (sentiment analysis, summarization, classification, embeddings), finance & Web3 (price feeds, exchange rates, token quotes, gas estimates), and infrastructure utilities (geocoding, validation, conversion, generation). All endpoints are priced at $0.02 per request, paid in USDC on the Base network with no API keys, no rate limits, and no commitments required.

The x402 challenge is live and returns a 402 with `maxAmountRequired` of 20000 base units of USDC (asset 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913, which has 6 decimals), equating to $0.02 per call. Payment is made via the `exact` scheme to address 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3 with a 300-second timeout. The endpoint accepts HTTP POST and returns `application/json`.

Note that while the landing page lists many distinct API paths across multiple categories, the specific functionality behind `/api/v1/inbox/167` is not documented beyond the generic label "Premium API Access." There is no OpenAPI spec, no request/response schema, and no usage examples available from the crawled pages. The broader platform appears to be a demonstration or marketplace of x402-gated microservices, but without detailed documentation it is difficult to confirm what data or computation this particular endpoint returns.

Capabilities

x402-paymentusdc-basepay-per-requestjson-responsehttp-post

Use cases

  • —Programmatic access to premium API services without API key management
  • —Agent-driven pay-per-call workflows settled in USDC on Base
  • —Testing x402 payment protocol integrations with low-cost endpoints

Fit

Best for

  • —Developers exploring x402 payment protocol
  • —AI agents needing keyless, pay-per-use API access
  • —Low-cost micropayment API experimentation on Base

Not for

  • —Users needing well-documented, schema-specified API contracts
  • —High-throughput production workloads requiring SLA guarantees
  • —Users without USDC on Base network

Quick start

curl -X POST https://lowpaymentfee.com/api/v1/inbox/167 \
  -H "Content-Type: application/json" \
  -H "X-PAYMENT: <x402-payment-token>" \
  -d '{}'

Endpoint

URLhttps://lowpaymentfee.com/api/v1/inbox/167
Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.30/ 1.00

The x402 challenge is live and pricing is clear ($0.02 USDC on Base), but there is no OpenAPI spec, no request/response schema, no documentation of what /api/v1/inbox/167 actually does, and crawled subpages returned only 'Connect wallet' with no useful content. The endpoint is effectively a stub listing.

Warnings

  • —No OpenAPI or schema documentation available for this endpoint
  • —The specific functionality of /api/v1/inbox/167 is undocumented — 'Premium API Access' is a generic label
  • —No request or response examples are available
  • —Crawled /api, /pricing, and /README pages returned no meaningful content beyond 'Connect wallet'
  • —The platform lists many endpoint categories but it is unclear whether they are all functional

Citations

Provenance

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

Agent access

JSONhttps://clawmart.sh/api/listings/tbM2Ey
Pay-per-call premium API access on Base via x402 — $0.02/request in USDC. — Clawmart · Clawmart