x402-gated account statements endpoint on Base, pay-per-request with USDC.
What it does
This endpoint at lowpaymentfee.com provides access to account statements via a POST request to `/api/v1/accounts/5/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 infrastructure utilities — all gated behind the x402 payment protocol on the Base network.
The specific endpoint probed returns a 402 challenge requesting payment of up to 20,000 base units of USDC (contract `0x8335...2913` on Base). Since USDC uses 6 decimals, this translates to $0.02 per request, consistent with the site's advertised flat pricing of $0.02/request across all endpoints. Payment is settled on-chain to address `0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3` using the "exact" x402 scheme. No API keys or rate limits are advertised; access is granted purely via the x402 payment header.
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, and no example payloads available. The endpoint path suggests it returns financial account statements (for account ID 5), but the actual data format and required POST body are unknown. The platform appears to be a demonstration or early-stage deployment of x402-gated microservices.
Capabilities
Use cases
- —Retrieving account statement data via a single paid API call
- —Demonstrating x402 payment protocol integration for per-request billing
- —Programmatic access to financial account records without API key management
Fit
Best for
- —Developers experimenting with x402 payment-gated APIs
- —Agents that can settle USDC payments on Base for per-call access
- —Use cases requiring keyless, pay-as-you-go API access
Not for
- —Production workloads requiring documented request/response schemas
- —Users who need free or subscription-based access without crypto wallets
- —High-volume batch processing where per-request crypto settlement adds overhead
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/accounts/5/statements \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-token>"Endpoint
Quality
The endpoint is live and returns a valid x402 402 challenge with clear pricing. However, there is no documentation, no OpenAPI spec, no request/response schema, and no examples. The docs pages are empty stubs. The purpose of this specific endpoint (account 5 statements) is unclear and may be a demo. This is effectively a stub listing.
Warnings
- —No OpenAPI spec or schema available for request or response bodies
- —All documentation pages (docs, API, pricing, README) render only 'Connect wallet' with no content
- —The endpoint path references a hardcoded account ID (5), suggesting this may be a demo or placeholder
- —Actual data returned by the endpoint is completely unknown
Citations
- —The endpoint returns a 402 challenge requesting up to 20,000 base units of USDC on Basehttps://lowpaymentfee.com/api/v1/accounts/5/statements
- —USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/accounts/5/statements
- —Platform advertises $0.02/request flat pricing with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —Docs, API, pricing, and README pages show only 'Connect wallet' with no substantive documentationhttps://lowpaymentfee.com/docs