x402basequality 0.30

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

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

What it does

This endpoint at lowpaymentfee.com provides access to account statements via a POST request to `/api/v1/accounts/35/statements`. It is part of a broader platform (lowpaymentfee.com) that offers a variety of pay-per-call APIs spanning data analytics, AI/ML inference, finance/Web3 data, and infrastructure utilities — all gated behind the x402 payment protocol on the Base network.

The specific endpoint probed charges up to 0.02 USDC per request (maxAmountRequired of 20,000 base units with USDC's 6 decimals). Payment is settled on-chain on Base using USDC (contract 0x8335…2913) to the payTo address 0x1A2B…85F3. The endpoint uses the "exact" payment scheme with a 300-second timeout. No API keys or rate limits are advertised; access is granted purely through the x402 payment header.

Documentation is extremely sparse. The landing page lists available API categories and a uniform $0.02/request price, but 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 detailed description of what the account statements endpoint returns or what parameters it accepts. The endpoint is confirmed live (returns a valid 402 challenge), but the lack of documentation makes it difficult to use without experimentation.

Capabilities

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

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 via on-chain USDC payments

Fit

Best for

  • —Developers or agents needing account statement data with zero signup friction
  • —Use cases where per-call crypto micropayments are preferred over subscriptions
  • —Automated workflows on Base that can natively settle USDC payments

Not for

  • —Users who need detailed API documentation or request/response schemas before integrating
  • —High-volume consumers who would benefit from bulk pricing or subscription plans
  • —Users without access to USDC on the Base network

Quick start

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

Endpoint

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

Quality

0.30/ 1.00

The endpoint is confirmed live with a valid x402 402 challenge, but documentation is essentially nonexistent — docs/pricing/README pages all show only 'Connect wallet'. There is no OpenAPI schema, no request/response examples, and no description of what the statements endpoint actually returns or accepts. The endpoint path includes a hardcoded account ID (35), raising questions about generalizability.

Warnings

  • —Documentation pages (docs, pricing, README, api) all render only 'Connect wallet' with no usable content
  • —No OpenAPI or request/response schema available — input parameters and output format are unknown
  • —The endpoint path contains a hardcoded account ID (/accounts/35/statements); unclear if other account IDs are supported or what this represents
  • —The broader platform lists many API categories but this specific endpoint (account statements) is not listed on the landing page

Citations

Provenance

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

Agent access

JSONhttps://clawmart.sh/api/listings/bEngev
x402-gated account statements endpoint on Base, pay-per-request with USDC. — Clawmart · Clawmart