x402basequality 0.25

x402-gated account statements endpoint on Base, paid 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 statements via a POST request to `/api/v1/accounts/163/statements`. It is part of a broader platform (lowpaymentfee.com) that offers a variety of x402-gated APIs spanning data analytics, AI/ML inference, finance/Web3 data, and infrastructure utilities — all payable per-request in USDC on the Base network.

The specific endpoint probed here returns an x402 challenge requesting up to 20,000 base units of USDC (0.02 USD) per call, settled on-chain to the specified payTo address. The asset contract (`0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913`) is the canonical USDC contract on Base. No API keys or rate limits are advertised; access is gated purely by the x402 payment protocol. The response MIME type is `application/json`.

Documentation is extremely sparse — the docs, API, pricing, and README pages all render only a "Connect wallet" prompt with no further content. There is no OpenAPI schema, no request/response examples, and no description of what the "account statements" endpoint actually returns or what input parameters it expects. The platform's landing page lists many endpoints across multiple categories, all priced at $0.02/request, but provides no technical documentation for any of them. The exact purpose and data format of this particular endpoint remain unclear.

Capabilities

x402-paymentusdc-settlementbase-networkaccount-statementsper-request-pricingno-api-keyjson-response

Use cases

  • Retrieving account statement data via a single paid API call
  • Programmatic access to financial account information without API key management
  • Agent-driven data retrieval with on-chain USDC micropayments

Fit

Best for

  • Developers or agents who want keyless, pay-per-call access to account statements
  • Use cases requiring on-chain payment settlement on Base
  • Scenarios where traditional API key provisioning is undesirable

Not for

  • Users who need detailed API documentation or guaranteed SLAs before integrating
  • High-volume batch retrieval where per-call pricing may add up
  • Anyone without a Base-compatible USDC wallet

Quick start

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

Endpoint

Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.25/ 1.00

The endpoint is live and returns a valid x402 challenge, but there is zero documentation on request parameters, response schema, or what 'account statements' actually contains. Docs pages are empty. No OpenAPI spec or examples exist. This is effectively a stub listing.

Warnings

  • No documentation available — docs, API, pricing, and README pages all show only 'Connect wallet' with no content.
  • No request or response schema provided; it is unknown what parameters the POST endpoint accepts or what data it returns.
  • The purpose of 'account statements' for account ID 163 is entirely undocumented.
  • The broader platform lists many endpoints but none have technical documentation.

Citations

Provenance

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

Agent access