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
Endpoint
https://lowpaymentfee.com/api/v1/accounts/119/statements

What it does

This endpoint at lowpaymentfee.com provides access to account statements via a POST request to `/api/v1/accounts/119/statements`. It is part of a broader platform offering numerous x402-protocol pay-per-call APIs spanning data analytics, AI/ML inference, finance, crypto, and utility services — all priced at $0.02 per request settled in USDC on the Base network.

The specific endpoint probed here (`/accounts/119/statements`) returned a valid x402 challenge with `maxAmountRequired` of 20,000 base units of USDC (0x8335… on Base, 6 decimals), which equals $0.02. Payment is made via the x402 exact scheme: callers attach an `X-PAYMENT` header containing a signed payment authorization, and the server fulfills the request upon verification. No API keys, subscriptions, or rate limits are advertised — access is purely pay-per-request.

Documentation is extremely sparse. The crawled docs, API, pricing, and README pages all rendered only a "Connect wallet" prompt with no additional content. There is no OpenAPI schema, no request/response examples, and no description of what the statements endpoint actually returns or what parameters it accepts. The endpoint is live (402 challenge confirmed), but without documentation it is difficult to know the expected input format or output structure beyond `application/json`.

Capabilities

x402-paymentusdc-basepay-per-requestaccount-statementsjson-apino-api-key

Use cases

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

Fit

Best for

  • —Agents or services that need occasional account statement lookups without committing to a subscription
  • —Developers experimenting with x402 pay-per-request protocols
  • —Workflows requiring keyless, on-demand financial data access

Not for

  • —Production use cases requiring well-documented request/response schemas
  • —High-volume bulk data retrieval where per-request pricing is inefficient
  • —Users without a Base-network USDC wallet

Quick start

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

Endpoint

URLhttps://lowpaymentfee.com/api/v1/accounts/119/statements
Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.30/ 1.00

The endpoint is live and returns a valid x402 challenge, but documentation is essentially nonexistent — all doc pages render only a wallet-connect prompt. There is no OpenAPI schema, no request/response examples, and no description of what the statements endpoint accepts or returns. The listing is effectively a stub.

Warnings

  • —No documentation available — all doc/pricing/README pages show only 'Connect wallet' with no content.
  • —No OpenAPI or input/output schema provided; request format and response structure are unknown.
  • —The specific endpoint path includes a hardcoded account ID (119); it is unclear whether this is parameterizable or a fixed demo resource.
  • —Purpose and data returned by the 'statements' endpoint are not described anywhere in the crawled material.

Citations

Provenance

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

Agent access

JSONhttps://clawmart.sh/api/listings/fXw9xy
x402-gated account statements endpoint on Base, pay $0.02 per request in USDC. — Clawmart · Clawmart