x402basequality 0.35

x402-payable account statements endpoint on Base, settled in USDC at $0.02/request.

Price
0.02 USDC / call
Protocol
x402
Verified
no

What it does

This endpoint at lowpaymentfee.com provides account statement data for a specific account (ID 141) via the x402 payment protocol. It accepts POST requests and returns JSON. Payment is settled on the Base network using USDC (contract 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913) with a maximum cost of 20,000 base units, which equals $0.02 per request (USDC uses 6 decimals).

The endpoint is part of a broader platform (lowpaymentfee.com) that offers multiple API categories including Data & Analytics, AI & Machine Learning, Finance & Web3, and Infrastructure utilities — all priced at $0.02 per request with no API keys, no rate limits, and no minimum commitments. The platform uses the x402 protocol (version 1) with the "exact" payment scheme, meaning each request requires a one-time micropayment.

The specific functionality of this particular endpoint — account statements — is not well documented. The crawled landing page lists many other endpoints but does not include this `/api/v1/accounts/141/statements` path among its advertised APIs. The request and response schemas are not documented, and the docs/pricing/API pages returned only a wallet-connect prompt with no additional content. As a result, the exact input parameters and output format remain unclear.

Capabilities

x402-paymentusdc-settlementbase-networkaccount-statementsjson-responsepost-methodmicropayment

Use cases

  • Retrieving account statement data for account 141 via a single micropayment
  • Integrating pay-per-request financial data into agent workflows
  • Demonstrating x402 protocol micropayment flows on Base

Fit

Best for

  • Agents needing on-demand account statement data without API key management
  • Developers experimenting with x402 micropayment protocol on Base
  • Low-volume, pay-as-you-go access to financial statement data

Not for

  • High-volume bulk data retrieval where per-request pricing is inefficient
  • Use cases requiring well-documented request/response schemas upfront
  • Accessing accounts other than ID 141 (endpoint is account-specific)

Quick start

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

Endpoint

Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.35/ 1.00

The endpoint is live and returns a valid x402 challenge with clear pricing, but there is no documentation of request parameters, response schema, or what 'account statements' actually returns. The docs, pricing, and API pages are empty beyond a wallet-connect prompt. The endpoint path itself is not listed among the platform's advertised APIs.

Warnings

  • No request or response schema documented — input format and output structure are unknown
  • This specific endpoint (/api/v1/accounts/141/statements) is not listed among the platform's advertised APIs on the landing page
  • All documentation pages (docs, pricing, API, README) returned only a wallet-connect prompt with no substantive content
  • The endpoint is hardcoded to account ID 141; unclear if other account IDs are supported

Citations

Provenance

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

Agent access

x402-payable account statements endpoint on Base, settled in USDC at $0.02/request. — Clawmart · Clawmart