x402basequality 0.30

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

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

What it does

lowpaymentfee.com is a pay-per-request API platform that uses the x402 protocol to accept USDC payments on the Base network. The specific endpoint at `/api/v1/payments/301` is labeled "Premium API Access" and accepts POST requests. The x402 challenge confirms it is live, requiring up to 20,000 base units of USDC (0x8335…) on Base, which equals $0.02 per call (USDC uses 6 decimals). Payment is made via the `exact` scheme to the specified wallet address, with a 300-second timeout.

The broader platform advertises multiple API categories including Data & Analytics (metrics, reports, data export, insights), AI & Machine Learning (sentiment analysis, text summarization, classification, embeddings), Finance & Web3 (price feeds, exchange rates, token quotes, gas estimates), and Infrastructure utilities (geocoding, validation, conversion, generation). All endpoints are listed at $0.02 per request. The platform emphasizes no API keys, no rate limits, and instant access.

However, documentation is extremely sparse. The docs, API, pricing, and README pages all render only a "Connect wallet" prompt with no further technical detail. There is no OpenAPI spec, no request/response schema documentation, and no examples of what the endpoints actually return. The `/api/v1/payments/301` endpoint in particular has no description beyond its title, making it unclear what data or service it provides. The platform appears to be a demonstration or early-stage deployment of x402-gated APIs.

Capabilities

x402-paymentusdc-base-networkpay-per-requestno-api-keypost-methodjson-response

Use cases

  • —Accessing premium API endpoints with per-request USDC micropayments on Base
  • —Testing x402 protocol integration for pay-per-call services
  • —Agent-driven API consumption without API key management

Fit

Best for

  • —Developers experimenting with x402 payment protocol
  • —Agents that need keyless, pay-as-you-go API access
  • —Low-volume consumers who prefer per-call pricing over subscriptions

Not for

  • —Production workloads requiring documented, stable API contracts
  • —Users who need detailed request/response schemas before integration
  • —Anyone without a Base-network USDC wallet

Quick start

# The endpoint returns 402 with an x402 challenge.
# After constructing the X-PAYMENT header per x402 spec:
curl -X POST https://lowpaymentfee.com/api/v1/payments/301 \
  -H "Content-Type: application/json" \
  -H "X-PAYMENT: <signed-payment-token>"

Endpoint

URLhttps://lowpaymentfee.com/api/v1/payments/301
Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.30/ 1.00

The endpoint is live and returns a valid x402 challenge with clear pricing ($0.02 USDC on Base). However, there is no OpenAPI spec, no documentation beyond a landing page listing, no request/response examples, and the specific purpose of the /api/v1/payments/301 endpoint is entirely undocumented. The docs/pricing/README pages are all empty beyond a wallet connect prompt. This is effectively a stub listing.

Warnings

  • —No OpenAPI or schema documentation available for any endpoint
  • —The purpose and expected input/output of /api/v1/payments/301 is undocumented
  • —All documentation pages (docs, pricing, README, API) render only 'Connect wallet' with no content
  • —Platform appears to be early-stage or demonstration; reliability and data quality are unknown
  • —No request or response examples exist anywhere in the crawled material

Citations

Provenance

Indexed fromx402_bazaar
Enriched2026-04-19 07:07:03Z · anthropic/claude-opus-4.6 · v2
First seen2026-04-18
Last seen2026-04-23

Agent access

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