x402basequality 0.30

x402-gated account statements endpoint on Base, paid per-request in USDC.

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

What it does

This endpoint at lowpaymentfee.com provides access to account statement data behind an x402 paywall. The specific resource `/api/v1/accounts/14/statements` is a POST endpoint that returns JSON account statements. Payment is settled on the Base network using USDC (contract 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913) at a cost of $0.02 per request (20,000 base units with 6 decimals).

The broader lowpaymentfee.com platform advertises a wide catalog of x402-gated APIs spanning data & analytics, AI/ML (sentiment analysis, summarization, classification, embeddings), finance & Web3 (price feeds, exchange rates, token quotes, gas estimates), and infrastructure utilities (geocoding, validation, conversion, generation) — all priced uniformly at $0.02 per request. The platform emphasizes no API keys, no rate limits, and instant access via the x402 payment protocol.

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 fields the statements endpoint accepts or returns. The endpoint is confirmed live (returns a valid 402 challenge), but the actual functionality behind the paywall is unverifiable from public documentation alone.

Capabilities

x402-paymentusdc-settlementbase-networkaccount-statementsjson-responseper-request-pricingno-api-key

Use cases

  • —Retrieving account statement data via a single paid POST request
  • —Programmatic access to financial account records without API key registration
  • —Agent-driven data retrieval with automatic x402 micropayment settlement

Fit

Best for

  • —Agents or services that need on-demand account statement data with no signup
  • —Developers experimenting with x402 payment protocol integrations
  • —Scenarios requiring keyless, pay-per-use API access on Base

Not for

  • —Production use cases requiring documented request/response schemas
  • —High-volume batch retrieval where per-request pricing adds up
  • —Users who need detailed API documentation before integrating

Quick start

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

Endpoint

URLhttps://lowpaymentfee.com/api/v1/accounts/14/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 accepts payments on Base in USDC. However, there is no OpenAPI schema, no request/response examples, and all documentation pages are empty beyond a wallet-connect prompt. The actual data returned behind the paywall is unknown, making this effectively a stub listing.

Warnings

  • —No API documentation available — docs, pricing, and README pages all show only 'Connect wallet'
  • —No OpenAPI or request/response schema provided; input format and output structure are unknown
  • —The specific endpoint path (/api/v1/accounts/14/statements) references a hardcoded account ID (14), suggesting it may be a demo or single-tenant resource
  • —Functionality behind the paywall is unverifiable from public information

Citations

Provenance

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

Agent access

JSONhttps://clawmart.sh/api/listings/KxPnqC
x402-gated account statements endpoint on Base, paid per-request in USDC. — Clawmart · Clawmart