x402basequality 0.30

x402-gated account statements endpoint on Base, pay-per-request with USDC.

Price
0.02 USDC / call
Protocol
x402
Verified
no

What it does

This endpoint at lowpaymentfee.com provides access to account statements via a POST request to `/api/v1/accounts/45/statements`. It is part of a broader platform offering data & analytics, AI/ML inference, finance/Web3, and infrastructure utility APIs, all gated behind the x402 payment protocol on the Base network.

The specific endpoint probed returns a 402 challenge requesting payment in USDC (contract `0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913` on Base). The `maxAmountRequired` is 20,000 base units of USDC (6 decimals), which equals $0.02 per request. The platform advertises uniform $0.02/request pricing across all its endpoints, with no API keys, no rate limits, and no minimum commitments required. Payment is settled on-chain via the x402 "exact" scheme.

Documentation is extremely sparse — the docs, API, pricing, and README pages all render only a "Connect wallet" prompt with no further content. There is no OpenAPI schema, no request/response examples, and no description of what the "account statements" resource actually returns. The endpoint is live (402 challenge confirmed), but the lack of documentation makes it difficult to know what data to POST or what shape the response takes. The platform appears to be a demonstration or early-stage x402 marketplace rather than a mature production API.

Capabilities

x402-paymentusdc-settlementbase-networkaccount-statementspay-per-requestno-api-keypost-endpoint

Use cases

  • Retrieving account statement data via a single paid POST request
  • Demonstrating x402 payment protocol integration on Base
  • Programmatic access to financial account records without API key management

Fit

Best for

  • Developers experimenting with x402 payment-gated APIs
  • Agents that can settle USDC payments on Base automatically
  • Use cases requiring keyless, pay-per-request access to account data

Not for

  • Production workloads requiring documented request/response schemas
  • Users who need traditional API-key or OAuth authentication
  • High-volume batch retrieval where per-request pricing is impractical

Quick start

curl -X POST https://lowpaymentfee.com/api/v1/accounts/45/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 live and returns a valid x402 challenge with clear pricing ($0.02 USDC on Base). However, there is no OpenAPI schema, no request/response examples, no documentation beyond a wallet-connect prompt, and the purpose of the 'account statements' resource is undefined. This is effectively a stub listing.

Warnings

  • No documentation available — docs, API, pricing, and README pages all show only 'Connect wallet'
  • No OpenAPI or JSON schema describing request body or response format
  • The specific resource '/api/v1/accounts/45/statements' has a hardcoded account ID (45); unclear if this is parameterizable
  • Platform appears to be early-stage or a demo; production readiness is uncertain

Citations

Provenance

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

Agent access