x402basequality 0.30

x402-gated account statements endpoint on Base, pay $0.02 per request in USDC.

Price
0.02 USDC / call
Protocol
x402
Verified
no

What it does

This endpoint at lowpaymentfee.com provides access to account statement data behind an x402 paywall. The specific resource `/api/v1/accounts/149/statements` is part of a broader platform that offers dozens of pay-per-call APIs spanning data analytics, AI/ML inference, finance, crypto, and utility services — all priced at $0.02 per request and settled in USDC on the Base network.

The endpoint accepts POST requests and returns JSON. Payment is handled via the x402 protocol: callers must include an X-PAYMENT header with a valid payment proof. The maximum amount required per call is 20,000 base units of USDC (0x8335…2913 on Base), which equals $0.02 given USDC's 6 decimals. There are no API keys, no rate limits, and no subscription commitments — each request is independently paid for.

Documentation is extremely sparse. The crawled docs, API, pricing, and README pages all returned only a "Connect wallet" prompt with no further content. There is no OpenAPI schema, no request/response examples, and no description of what fields the statements endpoint accepts or returns. The endpoint is confirmed live (402 challenge captured), but the actual data content and input parameters remain unknown.

Capabilities

x402-paymentusdc-settlementbase-networkaccount-statementspay-per-requestjson-responsepost-method

Use cases

  • Retrieving account statement data on a per-request payment basis
  • Integrating pay-per-call financial data into agent workflows
  • Accessing statement records without API key registration

Fit

Best for

  • Agents that need on-demand account statement data without subscription overhead
  • Developers exploring x402 pay-per-request patterns on Base
  • Automated workflows requiring low-friction, keyless API access

Not for

  • Users needing detailed API documentation or schema guarantees before integration
  • High-volume batch retrieval where per-request pricing becomes costly
  • Use cases requiring authenticated sessions or user-specific account binding

Quick start

curl -X POST https://lowpaymentfee.com/api/v1/accounts/149/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, confirming pricing and network. However, there is no OpenAPI schema, no request/response examples, and all documentation pages are empty stubs. The purpose of the specific /accounts/149/statements resource is unclear — it may be a demo or placeholder. This is effectively a stub listing.

Warnings

  • No API documentation available — all doc pages return only a wallet-connect prompt
  • No OpenAPI or input/output schema provided; request body format is unknown
  • The endpoint path includes a hardcoded account ID (149), which may indicate a demo or placeholder resource
  • No examples of actual response data are available

Citations

Provenance

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

Agent access