x402basequality 0.30

x402-gated account statements endpoint on Base, paid per-request in USDC.

Price
0.02 USDC / call
Protocol
x402
Verified
no
Endpoint
https://lowpaymentfee.com/api/v1/accounts/160/statements

What it does

This endpoint at lowpaymentfee.com provides access to account statements via a POST request to `/api/v1/accounts/160/statements`. It is part of a broader platform (lowpaymentfee.com) that offers a variety of x402-protocol pay-per-call APIs spanning data analytics, AI/ML inference, finance/Web3 data, and infrastructure utilities.

The specific endpoint probed returns a 402 challenge requesting payment of up to 20,000 base units of USDC (0x8335…2913 on Base network), which equals $0.02 per request (USDC uses 6 decimals). Payment is settled on-chain via the x402 "exact" scheme to address 0x1A2B…85F3. The platform advertises uniform $0.02/request pricing across all its endpoints, with no API keys, no rate limits, and no minimum commitments required.

Documentation is extremely sparse — the /docs, /api, /pricing, and /README pages all render only a "Connect wallet" prompt with no substantive content. There is no OpenAPI spec, no request/response schema documentation, and no example payloads available. The endpoint's purpose ("account statements") and expected input/output formats must be inferred from the URL path and the generic description "Premium API Access." The platform appears to be a demonstration or early-stage deployment of x402-based micropayment APIs.

Capabilities

x402-paymentusdc-settlementbase-networkpay-per-requestaccount-statementspost-endpoint

Use cases

  • —Retrieving account statement data via a single paid API call
  • —Demonstrating x402 protocol micropayment flows on Base
  • —Agent-driven financial data retrieval with on-chain settlement

Fit

Best for

  • —Developers experimenting with x402 payment protocol
  • —Agents that can settle USDC payments on Base L2
  • —Use cases needing keyless, pay-per-call API access

Not for

  • —Production workloads requiring documented request/response schemas
  • —Users who need fiat or non-crypto payment options
  • —High-volume batch retrieval where per-call pricing is inefficient

Quick start

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

Endpoint

URLhttps://lowpaymentfee.com/api/v1/accounts/160/statements
Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.30/ 1.00

The endpoint is live and returns a valid x402 402 challenge, but there is zero documentation on request/response schemas, no OpenAPI spec, and all doc pages are empty stubs. The purpose of the specific endpoint (account 160 statements) is unclear and may be a demo placeholder.

Warnings

  • —No OpenAPI or schema documentation available — request and response formats are unknown
  • —All documentation pages (/docs, /api, /pricing, /README) return only 'Connect wallet' with no content
  • —The endpoint path references a specific account ID (160), suggesting this may be a demo or placeholder rather than a general-purpose API
  • —No examples or descriptions of what 'account statements' contain

Citations

Provenance

Indexed fromx402_bazaar
Enriched2026-04-19 01:31:48Z · anthropic/claude-opus-4.6 · v2
First seen2026-04-18
Last seen2026-04-29

Agent access

JSONhttps://clawmart.sh/api/listings/QQdnDv
x402-gated account statements endpoint on Base, paid per-request in USDC. — Clawmart · Clawmart