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 statements via a POST request to `/api/v1/accounts/113/statements`. It is part of a broader platform offering data & analytics, AI/ML inference, finance/Web3, and infrastructure utility APIs, all gated behind the x402 payment protocol on the Base network.

The endpoint returns a 402 Payment Required challenge, confirming it is live and operational. Payment is settled in USDC (contract `0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913` on Base) using the "exact" scheme. The maximum amount required per request is 20,000 base units, which at 6 decimals for USDC equals $0.02. The platform advertises uniform $0.02/request pricing across all its endpoints, with no API keys, no rate limits, and no minimum commitments.

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 "statements" resource actually returns or what input parameters it expects. The specific endpoint path (`/accounts/113/statements`) suggests it retrieves financial statements for a particular account (ID 113), but the exact data format and any required POST body fields are unknown.

Capabilities

x402-paymentusdc-settlementbase-networkaccount-statementspost-apipay-per-request

Use cases

  • Retrieving account statement data via a single paid API call
  • Programmatic access to financial account records without API key registration
  • Agent-driven workflows that need on-demand account statement retrieval

Fit

Best for

  • Developers wanting keyless, pay-per-request access to account statements
  • AI agents that can settle x402 payments in USDC on Base
  • Prototyping integrations where low per-call cost and no signup are priorities

Not for

  • Production use cases requiring documented request/response schemas and SLAs
  • Users who need bulk or subscription-based access to large volumes of statements
  • Anyone unable to pay with USDC on the Base network

Quick start

curl -X POST https://lowpaymentfee.com/api/v1/accounts/113/statements
# Returns 402 with x402 challenge; attach X-PAYMENT header with valid USDC payment on Base to access.

Endpoint

Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.30/ 1.00

The endpoint is live (402 challenge confirmed) and pricing is clear ($0.02 USDC on Base). However, there is no documentation, no OpenAPI schema, no request/response examples, and no explanation of what the statements endpoint actually returns or accepts. The crawled docs pages are empty. 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 OpenAPI or request/response schema provided; input parameters and output format are unknown.
  • The endpoint path references a specific account ID (113); it is unclear whether this is parameterized or fixed.
  • The platform lists many endpoint categories (AI, finance, infrastructure) but none have documented schemas.

Citations

Provenance

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

Agent access

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