x402basequality 0.30

x402-gated account statements endpoint on Base, pay $0.02 per request in USDC.

Price
0.02 USDC / call
Protocol
x402
Verified
no

What it does

This endpoint at lowpaymentfee.com provides access to account statements via a POST request to `/api/v1/accounts/182/statements`. It is part of a broader platform offering data & analytics, AI/ML inference, finance/Web3, and infrastructure utility APIs, all gated behind the x402 payment protocol on the Base network.

The endpoint is live and returns a standard x402 challenge (HTTP 402) requiring payment in USDC (contract `0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913` on Base). The maximum amount required per call is 20,000 base units of USDC, which equals $0.02 (USDC uses 6 decimals). Payment is made via the `exact` scheme to address `0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3`, with a timeout of 300 seconds. No API keys or rate limits are advertised; access is granted purely through per-request micropayment.

Documentation is extremely sparse. The crawled docs, API, pricing, and README pages all returned only a "Connect wallet" prompt with no further content. The specific data schema for account statements (request body format, response fields) is not documented anywhere in the crawl material. The endpoint's purpose — "account statements" — suggests financial or transactional record retrieval, but without documentation it is unclear what data is actually returned or what parameters the POST body accepts.

Capabilities

x402-paymentusdc-micropaymentbase-networkaccount-statementsper-request-billingno-api-key

Use cases

  • Retrieving account statement data via a single micropayment
  • Integrating pay-per-request financial data into agent workflows
  • Accessing gated data without API key registration

Fit

Best for

  • Agents that can settle x402 payments in USDC on Base
  • Use cases requiring on-demand account statement retrieval without subscriptions
  • Developers exploring x402 micropayment-gated APIs

Not for

  • Users who need detailed API documentation or schema guarantees before integrating
  • High-volume batch retrieval where per-request fees add up
  • Anyone without a Base-compatible USDC wallet

Quick start

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

Endpoint

Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.30/ 1.00

The endpoint is live and returns a valid x402 challenge, but documentation is essentially nonexistent — all doc/pricing/API pages show only 'Connect wallet'. There is no OpenAPI schema, no request/response examples, and no description of what 'account statements' actually contains. The listing is largely inferred from the 402 challenge and the homepage.

Warnings

  • No API documentation available — all doc pages return only 'Connect wallet'
  • Request body schema and response format for account statements are completely unknown
  • The specific endpoint path includes a hardcoded account ID (182); unclear if this is parameterizable
  • Platform appears to be a demo or early-stage project with many listed endpoints but no substantive docs

Citations

Provenance

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

Agent access