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/12/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. The endpoint is confirmed live (returns a valid x402 402 challenge), but the actual data returned after payment is unknown. The account ID "12" in the URL path appears to be a fixed resource identifier, and it is unclear whether other account IDs are available or what the statement data structure looks like.

Capabilities

x402-paymentusdc-settlementbase-networkaccount-statementsjson-responseper-request-pricingno-api-key

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 data with crypto micropayments

Fit

Best for

  • Agents or developers who want keyless, pay-per-use access to account data
  • Crypto-native applications settling microtransactions on Base in USDC
  • Prototyping x402 payment flows against a live endpoint

Not for

  • Production use requiring documented request/response schemas
  • Bulk data retrieval where per-request pricing would be costly
  • Users who need fiat-only payment options

Quick start

curl -X POST https://lowpaymentfee.com/api/v1/accounts/12/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 with a valid x402 402 challenge, but there is zero documentation on request parameters, response schema, or what 'account statements' actually contain. The docs, pricing, and README pages are all blank 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 actual data returned after payment is completely undocumented
  • Account ID '12' is hardcoded in the URL; unclear if other accounts exist or what data is served
  • The broad catalog of endpoints listed on the homepage (AI, finance, utils) cannot be verified for functionality

Citations

Provenance

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

Agent access

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