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/183/statements`. It is part of a broader platform offering dozens of x402-protocol pay-per-call APIs spanning data analytics, AI/ML inference, finance/Web3 data, and infrastructure utilities — all priced at $0.02 per request settled in USDC on the Base network.

The specific endpoint probed (`/accounts/183/statements`) returned a valid x402 challenge (HTTP 402) confirming it is live. The challenge specifies payment of up to 20,000 base units of USDC (asset `0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913`, 6 decimals), which equals $0.02. Payment is made via the x402 "exact" scheme to address `0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3`, with a 300-second timeout. No API keys or rate limits are advertised; access is purely payment-gated.

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 schema, no request/response examples, and no description of what the statements endpoint actually returns or what parameters it accepts. The endpoint path suggests it retrieves financial or account statement data for account ID 183, but the actual payload structure is unknown.

Capabilities

x402-paymentusdc-settlementbase-networkaccount-statementspay-per-requestno-api-key

Use cases

  • Retrieving account statement data on a per-request payment basis
  • Programmatic access to financial records without subscription or API key
  • Agent-driven data retrieval settled in USDC on Base

Fit

Best for

  • Agents or services needing on-demand account statement access without signup
  • Crypto-native workflows that can settle USDC on Base
  • Low-volume, pay-as-you-go data retrieval

Not for

  • Users who need detailed API documentation or schema before integrating
  • High-volume batch retrieval where per-request pricing is inefficient
  • Non-crypto users who cannot settle payments on Base

Quick start

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

Endpoint

Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.30/ 1.00

The endpoint is live and returns a valid x402 challenge with clear pricing, but there is zero documentation on request parameters, response schema, or what data is actually returned. Docs pages are empty. No OpenAPI spec or examples exist.

Warnings

  • No documentation available — all doc pages render only 'Connect wallet' with no content
  • No OpenAPI or request/response schema provided; input and output formats are unknown
  • The endpoint path references a specific account ID (183); it is unclear whether this is parameterized or fixed
  • Purpose of 'account statements' is inferred from the URL path only; no authoritative description exists

Citations

Provenance

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

Agent access