x402basequality 0.25

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/103/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 returns a 402 Payment Required challenge, confirming it is live and operational. Payment is settled in USDC (contract `0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913` on Base) using the "exact" scheme. The max amount required is 20,000 base units, which at 6 decimals for USDC equals $0.02 per request. The platform advertises uniform $0.02/request pricing across all its endpoints, with no API keys, no rate limits, and no minimum commitments.

Documentation is extremely sparse — the /docs, /api, /pricing, and /README pages all render only a "Connect wallet" prompt with no further content. There is no OpenAPI schema, no request/response examples, and no description of what the statements endpoint actually returns or what input parameters it accepts. The specific endpoint path (`/accounts/103/statements`) suggests it retrieves financial statements for a particular account ID, but the exact data format and required POST body are unknown.

Capabilities

x402-paymentusdc-settlementbase-networkaccount-statementspost-endpointpay-per-request

Use cases

  • Retrieving account statement data via a single paid API call
  • Programmatic access to financial account records without API key registration
  • Agent-driven financial data retrieval with on-chain USDC micropayments

Fit

Best for

  • Developers wanting keyless, pay-per-request access to account statements
  • AI agents that can settle x402 payments in USDC on Base
  • Prototyping financial data integrations without subscription commitments

Not for

  • Users needing detailed API documentation or request/response schemas before integrating
  • High-volume production workloads where per-request pricing may not be cost-effective
  • Anyone without a Base-compatible USDC wallet

Quick start

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

Endpoint

Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.25/ 1.00

The endpoint is confirmed live via a valid 402 challenge, and pricing is clear ($0.02 USDC on Base). However, there is no OpenAPI schema, no documentation of request parameters or response format, and no examples. The docs pages are empty. This is effectively a stub listing.

Warnings

  • No API documentation available — /docs, /pricing, /api, and /README pages all show only 'Connect wallet' with no content
  • No OpenAPI or input/output schema provided; request body format and response structure are completely unknown
  • The endpoint path includes a hardcoded account ID (103); it is unclear whether other account IDs are supported or how to discover them
  • No robots.txt or agents.txt found

Citations

Provenance

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

Agent access