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/28/statements

What it does

This endpoint at lowpaymentfee.com provides access to account statements via a POST request to `/api/v1/accounts/28/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, and utility services — 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 maximum amount required is 20,000 base units of USDC, which equals $0.02 (USDC uses 6 decimals). Payment is made via the x402 "exact" scheme to address `0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3`, with a timeout of 300 seconds. The response MIME type is `application/json`.

The platform advertises a flat $0.02 per request across all its endpoints, with no API keys, no rate limits, and no minimum commitments. However, documentation beyond the landing page is essentially empty (all sub-pages just show "Connect wallet"), so the actual request/response schemas for this endpoint are unknown. The endpoint path suggests it retrieves financial statements for a specific account (ID 28), but no further details on input parameters or response structure are available.

Capabilities

x402-paymentusdc-on-baseaccount-statementspay-per-requestjson-response

Use cases

  • —Retrieving account statement data on a per-request payment basis
  • —Programmatic access to financial account records without API key registration
  • —Agent-driven financial data retrieval using x402 micropayments

Fit

Best for

  • —Agents or applications needing on-demand account statement data without subscription overhead
  • —Developers wanting keyless, pay-as-you-go API access settled in USDC on Base
  • —Low-friction integration where no signup or rate-limit management is desired

Not for

  • —Use cases requiring detailed API documentation or well-defined request/response schemas
  • —High-volume batch retrieval where per-request pricing may add up
  • —Users who need non-crypto payment options

Quick start

# 1. Send a POST with x402 payment header to get account statements
curl -X POST https://lowpaymentfee.com/api/v1/accounts/28/statements \
  -H "Content-Type: application/json" \
  -H "X-PAYMENT: <x402_payment_token>"

Endpoint

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

Quality

0.30/ 1.00

The endpoint is live and returns a valid x402 402 challenge, confirming it is operational. However, there is no documentation, no OpenAPI schema, no request/response examples, and the docs/pricing/API pages are all blank beyond a 'Connect wallet' prompt. The endpoint path (/accounts/28/statements) is oddly specific (hardcoded account ID), and the actual functionality is unclear.

Warnings

  • —No API documentation available — all doc pages return only 'Connect wallet'
  • —No request or response schema provided; input parameters and output format are unknown
  • —The endpoint path contains a hardcoded account ID (28), which may indicate a demo or placeholder rather than a general-purpose API
  • —Platform appears to be a generic multi-category API storefront with minimal substance behind the landing page

Citations

Provenance

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

Agent access

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