x402basequality 0.25

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/61/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, which at 6 decimals for USDC equals $0.02 per request. 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 crawled docs, API, pricing, and README pages all rendered only a "Connect wallet" prompt with no substantive content. There is no OpenAPI schema, no request/response examples, and no description of what the "account statements" resource actually contains or what parameters the POST body expects. The platform landing page lists many endpoints at $0.02 each but provides no technical detail beyond endpoint paths and short labels. Without documentation or example payloads, the actual functionality and data returned by this endpoint remain unclear.

Capabilities

x402-paymentusdc-paymentbase-networkpay-per-requestaccount-statementspost-endpoint

Use cases

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

Fit

Best for

  • Developers wanting keyless, pay-per-use access to account statements
  • AI agents that can settle x402 payments on Base automatically
  • Users who prefer crypto micropayments over subscription billing

Not for

  • Anyone needing detailed API documentation or request/response schemas before integrating
  • High-volume batch retrieval where per-request pricing may add up
  • Users without a Base-compatible USDC wallet

Quick start

curl -X POST https://lowpaymentfee.com/api/v1/accounts/61/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 live and returns a valid x402 challenge with clear pricing ($0.02 USDC on Base). However, there is no OpenAPI schema, no request/response examples, no documentation beyond a wallet-connect prompt, and no description of what data the endpoint actually returns. This is effectively a stub listing.

Warnings

  • No documentation available — docs, API, pricing, and README pages all show only 'Connect wallet'
  • No OpenAPI or JSON schema for request or response bodies
  • The specific resource '/api/v1/accounts/61/statements' has a hardcoded account ID (61); unclear if this is parameterizable
  • No information on what 'account statements' contain or what POST body is expected
  • Platform lists many endpoints but none have technical documentation

Citations

Provenance

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

Agent access

x402-gated account statements endpoint on Base, pay-per-request with USDC. — Clawmart · Clawmart