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 API endpoints across data analytics, AI/ML inference, finance/Web3, and infrastructure utilities — all priced at $0.02 per request and settled in USDC on the Base network.

The specific endpoint `/api/v1/accounts/36/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 an X-PAYMENT header with a valid payment proof.

Documentation on the site 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 schema, no request/response examples, and no description of what "account statements" contain or what parameters the POST body expects. The endpoint appears live (402 challenge returned successfully), but the lack of documentation makes it difficult to use without experimentation.

Capabilities

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

Use cases

  • Retrieving account statement data on a per-request payment basis
  • Programmatic access to financial account records without subscription commitments
  • Agent-driven workflows that need on-demand account data with crypto micropayments

Fit

Best for

  • Developers wanting pay-per-use account data without API key management
  • AI agents that can settle x402 payments on Base in USDC
  • Low-volume or sporadic access to account statements

Not for

  • Users needing detailed API documentation or request/response schemas before integration
  • High-volume batch retrieval where per-request pricing is inefficient
  • Users who cannot transact in USDC on the Base network

Quick start

curl -X POST https://lowpaymentfee.com/api/v1/accounts/36/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 live and returns a valid x402 challenge, but there is no OpenAPI schema, no documentation, no request/response examples, and no explanation of what 'account statements' actually returns or what POST body it expects. The docs pages are empty. This is effectively a stub listing.

Warnings

  • No API documentation available — docs, pricing, and README pages all render only 'Connect wallet' with no content
  • No OpenAPI or JSON schema describing request parameters or response format
  • The meaning of 'accounts/36/statements' is unclear — it may be a demo or placeholder resource
  • No request or response examples available anywhere in the crawled material

Citations

Provenance

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

Agent access