x402basequality 0.30

x402-payable account statements endpoint on Base, settled in USDC at $0.02 per 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-request APIs spanning data analytics, AI/ML inference, finance, crypto, and utility services — all priced at $0.02 per call and settled in USDC on the Base network.

The specific endpoint `/api/v1/accounts/29/statements` accepts POST requests and returns JSON. The x402 challenge confirms it is live, requiring a maximum of 20,000 base units of USDC (0x8335…2913 on Base, 6 decimals = $0.02) per request. Payment is made via the x402 exact scheme to the specified payTo address, with a 300-second timeout. No API keys or rate limits are advertised; access is granted purely through per-request micropayment.

Documentation on the site is extremely thin — the docs, pricing, API, and README pages all render only a "Connect wallet" prompt with no further technical detail. There is no OpenAPI spec, no request/response schema, and no explanation of what fields the statements endpoint accepts or returns. The endpoint's purpose ("account statements") and the meaning of account ID 29 are not documented. Prospective users should expect to experiment or contact the provider for integration details.

Capabilities

x402-paymentusdc-settlementbase-networkaccount-statementsper-request-micropaymentjson-responsepost-method

Use cases

  • Retrieving account statement data via a single micropayment per request
  • Integrating pay-per-use financial data into agent workflows without API keys
  • Programmatic access to statement records settled on-chain in USDC

Fit

Best for

  • Agents or developers who want keyless, pay-per-call access to account statements
  • Crypto-native workflows that can sign x402 USDC payments on Base
  • Scenarios requiring no subscription commitment — pure usage-based billing

Not for

  • Users needing detailed API documentation or OpenAPI specs before integrating
  • High-volume batch retrieval where per-request fees would accumulate significantly
  • Non-crypto users who cannot settle payments in USDC on Base

Quick start

# The endpoint returns 402 with an x402 challenge.
# After constructing and signing the USDC payment on Base,
# include it in the X-PAYMENT header:

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

Endpoint

Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.30/ 1.00

The endpoint is live (402 challenge captured) and pricing is clear ($0.02 USDC on Base), but there is no documentation, no OpenAPI schema, no request/response examples, and no explanation of what the endpoint actually returns. This is effectively a stub listing.

Warnings

  • No API documentation available — docs, pricing, API, and README pages all show only 'Connect wallet'
  • No OpenAPI or JSON schema for request or response bodies
  • The meaning of account ID 29 and what 'statements' contain is undocumented
  • No request or response examples available from any source

Citations

Provenance

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

Agent access