x402basequality 0.35

x402-gated account statements endpoint on Base, pay-per-request with 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/25/statements`. It is part of a broader platform (lowpaymentfee.com) that offers a variety of pay-per-call APIs spanning data analytics, AI/ML inference, finance/Web3 data, and utility services — all gated behind the x402 payment protocol on the Base network.

The specific endpoint probed returns a 402 challenge requesting payment in USDC (contract `0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913` on Base). The `maxAmountRequired` is 20,000 base units of USDC (6 decimals), which equals $0.02 per request. Payment is made via the x402 `exact` scheme to address `0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3`, with a timeout of 300 seconds. The response MIME type is `application/json`.

The platform advertises a uniform $0.02/request pricing model across all endpoints, with no API keys, no rate limits, and no minimum commitments. Documentation pages (`/docs`, `/pricing`, `/api`, `/README`) all appear to require a wallet connection and contain no substantive content when crawled without one. As a result, there is no detailed documentation available about request/response schemas, input parameters, or the specific data returned by the statements endpoint. The endpoint title "Premium API Access" is generic and does not clarify what account statements contain or what account ID 25 refers to.

Capabilities

x402-paymentusdc-settlementbase-networkaccount-statementspay-per-requestjson-response

Use cases

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

Fit

Best for

  • Agents or applications needing on-demand account statement data with crypto micropayments
  • Developers who want keyless, pay-per-use API access on Base
  • Workflows requiring x402-compatible financial data endpoints

Not for

  • Users who need detailed API documentation before integrating
  • Applications requiring free or subscription-based access to financial data
  • Use cases needing high-volume bulk data export at lower per-unit cost

Quick start

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

Endpoint

Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.35/ 1.00

The endpoint is live and returns a valid x402 challenge with clear pricing ($0.02 USDC on Base). However, there is no documentation, no request/response schema, no examples, and the endpoint purpose ('account statements' for account 25) is unexplained. The docs, pricing, and README pages are all empty behind a wallet-connect gate.

Warnings

  • No API documentation available — all doc pages require wallet connection and return no content when crawled
  • The endpoint path references a specific account ID (25); it is unclear whether this is parameterized or fixed
  • No request body schema or response schema is documented anywhere
  • The description 'Premium API Access' is generic and does not describe what data is returned
  • Cannot verify what 'account statements' actually contain without authenticated access

Citations

Provenance

Indexed fromx402_bazaar
Enriched2026-04-19 00:17:13Z · anthropic/claude-opus-4.6 · v2
First seen2026-04-18
Last seen2026-04-29

Agent access