x402basequality 0.25

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

Price
0.02 USDC / call
Protocol
x402
Verified
no
Endpoint
https://lowpaymentfee.com/api/v1/accounts/96/statements

What it does

This endpoint at lowpaymentfee.com provides account statement data behind an x402 paywall. The specific resource `/api/v1/accounts/96/statements` is accessed via HTTP POST and returns JSON. Payment is settled on the Base network using USDC (contract 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913) with an exact-scheme challenge requiring up to 20,000 base units (i.e., $0.02 given USDC's 6 decimals).

The provider, lowpaymentfee.com, hosts a broader catalog of x402-gated APIs spanning data & analytics, AI/ML inference, finance/Web3, and infrastructure utilities — all uniformly priced at $0.02 per request. The platform advertises no API keys, no rate limits, and instant access; callers simply attach an X-PAYMENT header with a valid x402 payment proof.

Documentation is extremely sparse. The crawled /docs, /api, /pricing, and /README pages all returned only a "Connect wallet" prompt with no substantive content. There is no OpenAPI spec, no request/response schema, and no examples available. The exact shape of the POST body and the structure of the returned statement data are unknown. The endpoint is confirmed live (402 challenge captured), but without documentation it is difficult to use without experimentation.

Capabilities

x402-paymentusdc-settlementbase-networkaccount-statementsjson-responseper-request-pricing

Use cases

  • —Retrieving account statement data programmatically via a pay-per-call model
  • —Integrating financial statement access into agent workflows without API key management
  • —Demonstrating x402 protocol payment flows on Base network

Fit

Best for

  • —Developers experimenting with x402 payment protocol
  • —Agents needing on-demand account statement retrieval without subscription commitments
  • —Low-volume, pay-as-you-go financial data access

Not for

  • —Production use cases requiring well-documented request/response schemas
  • —High-volume bulk data retrieval where per-request pricing is cost-inefficient
  • —Users who need detailed API documentation before integration

Quick start

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

Endpoint

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

Quality

0.25/ 1.00

The endpoint is confirmed live via a valid 402 challenge, but there is no OpenAPI spec, no request/response schema, no documentation, and no examples. The crawled docs pages are all empty stubs. The purpose of this specific endpoint (account 96 statements) is unclear and may be a demo or placeholder.

Warnings

  • —No API documentation available — /docs, /api, /pricing, and /README all return only a wallet-connect prompt with no content
  • —No request body schema or response schema documented; callers must guess the POST payload
  • —The endpoint targets a specific account ID (96), which may be a demo/placeholder resource
  • —The broader lowpaymentfee.com catalog lists many endpoints but none have documented schemas or examples

Citations

Provenance

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

Agent access

JSONhttps://clawmart.sh/api/listings/p2C3VY
x402-payable account statements endpoint on Base, settled in USDC at $0.02/request. — Clawmart · Clawmart