x402basequality 0.30

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 statement data behind an x402 paywall. The specific resource `/api/v1/accounts/34/statements` accepts POST requests and returns JSON. Payment is settled on the Base network using USDC (contract 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913) with a maximum cost of $0.02 per request (20,000 base units at 6 decimals).

The broader lowpaymentfee.com platform advertises a wide catalog of x402-gated APIs spanning data & analytics, AI/ML (sentiment analysis, summarization, classification, embeddings), finance & Web3 (price feeds, exchange rates, token quotes, gas estimates), and infrastructure utilities (geocoding, validation, conversion, generation). All endpoints are listed at $0.02 per request with no API keys, no rate limits, and no minimum commitments.

Documentation is extremely sparse — the /docs, /pricing, /api, and /README 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 usage examples available from the crawl. The endpoint is confirmed live via a valid x402 402 challenge, but the actual functionality behind the paywall cannot be verified from public materials alone.

Capabilities

x402-paymentusdc-settlementbase-networkaccount-statementsjson-responsepost-methodper-request-pricing

Use cases

  • Retrieving account statement data on a pay-per-request basis
  • Programmatic access to financial account records without API key management
  • Agent-driven financial data retrieval settled in USDC on Base

Fit

Best for

  • Agents or services needing on-demand account statement access without subscription
  • Developers wanting keyless, pay-per-use financial data endpoints
  • Crypto-native applications that can settle payments on Base L2

Not for

  • Users needing detailed API documentation or request/response schemas before purchasing
  • High-volume batch retrieval where per-request pricing may add up
  • Applications that cannot handle x402 payment flows or USDC on Base

Quick start

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

Endpoint

Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.30/ 1.00

The endpoint is confirmed live via a valid x402 402 challenge, but there is zero documentation on request parameters, response schema, or what 'account 34 statements' actually contains. The docs, pricing, and README pages are all empty beyond a wallet connect prompt. Without any schema or examples, this is effectively a stub listing.

Warnings

  • No OpenAPI spec or request/response schema available
  • All documentation pages (/docs, /pricing, /api, /README) render only 'Connect wallet' with no content
  • The specific resource '/api/v1/accounts/34/statements' references a hardcoded account ID (34) with no explanation of what data it returns
  • Cannot verify actual functionality behind the paywall from public materials

Citations

Provenance

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

Agent access