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. The specific resource `/api/v1/accounts/60/statements` accepts POST requests and returns JSON. Payment is settled on the Base network using USDC (contract 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913) with a maximum amount of 20,000 base units, which equals $0.02 per request (USDC uses 6 decimals).

The broader lowpaymentfee.com platform advertises a suite of x402-payable APIs spanning data & analytics, AI & machine learning (sentiment analysis, summarization, classification, embeddings), finance & Web3 (price feeds, exchange rates, token quotes, gas estimates), and infrastructure utilities (geocoding, validation, conversion, generation). All endpoints are listed at $0.02 per request with no API keys, no rate limits, and no minimum commitments required.

Documentation is extremely sparse — the docs, API, pricing, and README pages all render only a "Connect wallet" prompt with no further technical detail. There is no OpenAPI schema, no request/response examples, and no description of what fields the statements endpoint expects or returns. The endpoint is confirmed live via a valid 402 challenge, but the actual functionality and data model remain unclear.

Capabilities

x402-paymentusdc-settlementbase-networkaccount-statementsjson-responsepost-methodno-api-keyper-request-billing

Use cases

  • Retrieving account statement data on a pay-per-request basis
  • Programmatic access to financial account records without API key management
  • Agent-driven financial data retrieval settled in USDC on Base

Fit

Best for

  • Agents needing on-demand account statement data with crypto micropayments
  • Developers who want keyless, pay-per-use API access
  • Use cases where avoiding subscription commitments is important

Not for

  • Users who need detailed API documentation or schema guarantees before integrating
  • High-volume consumers who would benefit from bulk pricing or subscriptions
  • Anyone requiring non-crypto payment methods

Quick start

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

Endpoint

Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.30/ 1.00

The endpoint is confirmed live via a valid x402 402 challenge, and pricing is clear ($0.02/request in USDC on Base). However, there is no OpenAPI schema, no request/response examples, no documentation beyond a wallet-connect prompt, and no clarity on what the statements endpoint actually returns. This is effectively a stub listing.

Warnings

  • No API documentation available — docs, pricing, and README pages all show only 'Connect wallet'
  • No OpenAPI or JSON schema describing request parameters or response format
  • The specific resource path '/api/v1/accounts/60/statements' has a hardcoded account ID (60); unclear if this is parameterizable
  • Cannot verify what data the endpoint actually returns without making a paid request

Citations

Provenance

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

Agent access