x402basequality 0.30

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

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

What it does

This endpoint at lowpaymentfee.com provides account statement data behind an x402 paywall. It is part of a broader platform offering dozens of pay-per-request APIs spanning data analytics, AI/ML inference, finance/Web3 data, and infrastructure utilities — all priced at $0.02 per request and settled in USDC on the Base network.

The specific endpoint `/api/v1/accounts/55/statements` accepts POST requests and returns JSON. The x402 challenge confirms the endpoint is live, advertising a max amount of 20,000 base units of USDC (0x8335…2913 on Base, 6 decimals), which equals $0.02. Payment is made via the x402 exact scheme with no API keys or rate limits required — callers simply attach an X-PAYMENT header with a valid payment proof.

Documentation is extremely sparse. The crawled docs, pricing, and API pages all render only a "Connect wallet" prompt with no further technical detail. There is no OpenAPI spec, no request/response schema documentation, and no explanation of what "account statements" contain or what parameters the POST body accepts. The endpoint path includes a hardcoded account ID (55), and it is unclear whether other account IDs are supported or what data model underlies the statements resource.

Capabilities

x402-paymentusdc-settlementbase-networkaccount-statementspay-per-requestno-api-keyjson-response

Use cases

  • —Retrieving account statement data programmatically via a single paid request
  • —Integrating pay-per-use financial data 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 documented request/response schemas
  • —High-volume bulk data retrieval where per-request pricing is inefficient
  • —Users who need detailed API documentation before integration

Quick start

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

Endpoint

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

Quality

0.30/ 1.00

The endpoint is live and returns a valid x402 challenge with clear pricing, but there is no OpenAPI spec, no request/response schema, no documentation beyond a wallet-connect prompt, and no explanation of what data the endpoint actually returns. The listing is effectively a stub.

Warnings

  • —No API documentation available — docs, pricing, and API pages all render only 'Connect wallet'
  • —No request body schema or response schema documented anywhere
  • —Endpoint path contains a hardcoded account ID (55); unclear if other IDs are valid
  • —The purpose and data model of 'account statements' is entirely undocumented
  • —No OpenAPI or machine-readable spec found

Citations

Provenance

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

Agent access

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