x402basequality 0.30

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

Price
0.02 USDC / call
Protocol
x402
Verified
no

What it does

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

The specific endpoint `/api/v1/accounts/74/statements` accepts POST requests and returns JSON. The x402 challenge confirms it is live, requiring a maximum of 20,000 base units of USDC (0.02 USD, since USDC uses 6 decimals) per call, paid to address `0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3` on Base. The payment scheme is "exact" with a 300-second timeout. No API keys or rate limits are advertised; access is granted purely via the x402 payment header.

Documentation is extremely sparse. The crawled docs, API, pricing, and README pages all returned only a "Connect wallet" prompt with no further content. There is no OpenAPI schema, no request/response examples, and no description of what "account statements" contain or what parameters the POST body accepts. The endpoint's purpose (financial account statements vs. something else) and its input schema are unknown. The platform appears to be a demonstration or early-stage deployment of x402-gated microservices.

Capabilities

x402-paymentusdc-settlementbase-networkpay-per-requestjson-responseaccount-statements

Use cases

  • Retrieving account statement data via a single micropayment per request
  • Integrating x402-compatible agents with financial data endpoints
  • Demonstrating x402 payment flows on Base with USDC

Fit

Best for

  • Developers experimenting with x402 payment protocol on Base
  • Agents that need pay-per-call access without API key management
  • Low-volume, on-demand account statement retrieval

Not for

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

Quick start

# The endpoint requires an X-PAYMENT header with a valid x402 payment proof.
curl -X POST https://lowpaymentfee.com/api/v1/accounts/74/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, but there is no documentation, no OpenAPI schema, no request/response examples, and no explanation of what the endpoint actually returns. The crawled pages are effectively empty beyond a landing page listing endpoints.

Warnings

  • No API documentation available — docs, pricing, and README pages all render only 'Connect wallet' with no content.
  • No OpenAPI or input/output schema provided; the POST body format is unknown.
  • The purpose and contents of 'account statements' for account 74 are undocumented.
  • Platform appears to be early-stage or a demo; reliability and data quality are unverified.

Citations

Provenance

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

Agent access