x402basequality 0.30

x402-payable account statements endpoint on Base, settled in USDC at $0.02/request.

Price
0.02 USDC / call
Protocol
x402
Verified
no

What it does

This endpoint at lowpaymentfee.com provides account statement data behind an x402 paywall. It is part of a broader platform offering dozens of pay-per-call APIs spanning data analytics, AI/ML inference, finance/Web3 data, and infrastructure utilities — all priced at $0.02 per request and settled in USDC on the Base network.

The specific endpoint `/api/v1/accounts/145/statements` accepts POST requests and returns JSON. The x402 challenge advertises a maxAmountRequired of 20,000 base units of USDC (0x8335…2913 on Base), which equals $0.02 given USDC's 6 decimals. Payment is made via the x402 exact scheme with no API keys or rate limits required — callers simply attach the X-PAYMENT header with a valid payment proof.

Documentation is extremely sparse. The crawled docs, API, pricing, and README pages all render only a "Connect wallet" prompt with no further content. There is no OpenAPI spec, no request/response schema documentation, and no examples of what the statements endpoint actually returns. The endpoint is confirmed live (402 challenge captured), but the lack of documentation makes it difficult to know what input parameters are expected or what shape the response takes.

Capabilities

x402-paymentusdc-settlementbase-networkaccount-statementspay-per-requestno-api-keyjson-response

Use cases

  • Retrieving account statement data programmatically with per-call USDC payment
  • Integrating financial statement access into agent workflows without API key management
  • Paying for on-demand account data using x402 protocol on Base

Fit

Best for

  • Agents or apps that need on-demand account statement data with crypto micropayments
  • Developers wanting keyless, pay-per-use API access settled on Base
  • Workflows requiring no subscription commitment for occasional statement retrieval

Not for

  • Users who need detailed API documentation or request/response schemas before integrating
  • High-volume consumers who would benefit from bulk pricing or subscription plans
  • Developers who cannot transact in USDC on the Base network

Quick start

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

Endpoint

Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.30/ 1.00

The endpoint is confirmed live via a valid 402 challenge, but documentation is essentially nonexistent — all doc pages render only 'Connect wallet'. There is no OpenAPI spec, no request/response examples, and no description of what 'account statements' actually contains. The endpoint path includes a hardcoded account ID (145), raising questions about generality. Pricing is clear ($0.02/request in USDC on Base).

Warnings

  • No API documentation available — all doc pages show only 'Connect wallet'
  • No OpenAPI or schema definition for request parameters or response format
  • The endpoint path contains a hardcoded account ID (145); unclear if other account IDs are supported or what data is returned
  • No request or response examples exist in any crawled material
  • The nature of the 'statements' data is completely undocumented

Citations

Provenance

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

Agent access