x402basequality 0.25

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/65/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 per request (20,000 base units of USDC, which has 6 decimals). Payment is settled on-chain via USDC on Base to the address `0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3`. The x402 challenge confirms the endpoint is live and accepts the `exact` payment scheme with a 300-second timeout. No API keys or rate limits are advertised; access is granted purely through per-call x402 micropayments.

Documentation is extremely sparse. The crawled docs, API, pricing, and README pages all returned only a "Connect wallet" prompt with no substantive content. There is no OpenAPI schema, no request/response examples, and no description of what the "statements" resource actually contains or what parameters it accepts. The endpoint's purpose (account statements for account ID 65) is inferred solely from the URL path. The broader platform lists many endpoints at $0.02 each, but none have documented schemas or usage examples.

Capabilities

x402-paymentusdc-basepay-per-requestaccount-statementspost-methodno-api-key

Use cases

  • Retrieving account statement data via a single paid API call
  • Programmatic access to financial account records without API key management
  • Agent-driven workflows that need on-demand account data with crypto micropayments

Fit

Best for

  • Developers or agents who want keyless, pay-per-call access to account statements
  • Crypto-native applications settling payments on Base with USDC
  • Scenarios where avoiding subscription commitments is preferred

Not for

  • Users who need well-documented APIs with clear request/response schemas
  • High-volume use cases where per-call pricing may be inefficient
  • Anyone who needs to understand the data model before committing to integration

Quick start

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

Endpoint

Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.25/ 1.00

The endpoint is live (402 challenge confirmed) and pricing is clear ($0.02 USDC on Base), 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. This is a stub listing.

Warnings

  • No documentation available — all doc pages return only 'Connect wallet' with no content
  • No OpenAPI or request/response schema provided; request parameters and response format are unknown
  • The endpoint path references a specific account ID (65), which may not be generalizable
  • The purpose and data returned by 'statements' is entirely unclear

Citations

Provenance

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

Agent access

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