x402basequality 0.30

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

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

What it does

lowpaymentfee.com hosts a collection of pay-per-request API endpoints accessible via the x402 payment protocol on the Base network. The specific endpoint at `/api/v1/payments/222` is labeled "Premium API Access" and accepts POST requests. Payment is settled in USDC (contract 0x8335…2913 on Base) with a maximum amount of 20,000 base units, which equals $0.02 per call (USDC uses 6 decimals). No API keys, rate limits, or upfront commitments are required — callers simply attach an X-PAYMENT header with a valid x402 payment proof.

The broader lowpaymentfee.com platform advertises endpoints across four categories: 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 listed endpoints share the same $0.02/request pricing. However, the probed endpoint `/api/v1/payments/222` does not clearly map to any of these named services, and its actual response payload is undocumented.

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 beyond the x402 challenge's outputSchema stub, and no examples of what the endpoint actually returns. Callers should expect a JSON response (mimeType is application/json) but the structure is unknown.

Capabilities

x402-paymentusdc-settlementbase-networkpay-per-requestno-api-keyjson-responsepost-method

Use cases

  • —Accessing premium API data without signing up for an account or obtaining API keys
  • —Making one-off paid API calls settled instantly in USDC on Base
  • —Integrating pay-per-request services into autonomous agent workflows

Fit

Best for

  • —Developers who want zero-signup, pay-as-you-go API access
  • —AI agents with x402-compatible wallets on Base
  • —Users who prefer crypto micropayments over subscription billing

Not for

  • —Users needing detailed API documentation or guaranteed SLAs
  • —Anyone without a Base-compatible USDC wallet
  • —High-volume use cases where per-request pricing may add up

Quick start

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

Endpoint

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

Quality

0.30/ 1.00

The endpoint is live and returns a valid x402 402 challenge with clear pricing. However, documentation is essentially nonexistent — all doc pages show only 'Connect wallet'. There is no OpenAPI spec, no request/response schema, and the specific endpoint path '/api/v1/payments/222' doesn't correspond to any named service on the landing page. The actual functionality behind this endpoint is unknown.

Warnings

  • —No documentation available — /docs, /api, /pricing, and /README pages all render only 'Connect wallet'
  • —No OpenAPI or schema describing request parameters or response format
  • —The endpoint path /api/v1/payments/222 does not match any of the named services listed on the homepage
  • —Actual functionality and response payload are completely undocumented

Citations

Provenance

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

Agent access

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