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

What it does

This endpoint at lowpaymentfee.com provides access to account statements via a POST request, gated behind the x402 payment protocol. The specific resource `/api/v1/accounts/111/statements` returns JSON data and accepts payment in USDC on the Base network. The maximum amount required per call is 20,000 base units of USDC (6 decimals), which equals $0.02 per request.

The broader lowpaymentfee.com platform advertises a suite of APIs spanning data & analytics, AI & machine learning (sentiment analysis, summarization, classification, embeddings), finance & Web3 (price feeds, exchange rates, token quotes, gas estimates), and infrastructure utilities (geocoding, validation, conversion, generation) — all priced at $0.02 per request. However, this specific listing covers only the `/api/v1/accounts/111/statements` endpoint. No OpenAPI schema, request/response examples, or detailed documentation were found during the crawl; the docs, API, pricing, and README pages all returned only a "Connect wallet" prompt with no substantive content.

The endpoint is live and returned a valid x402 challenge (HTTP 402) with version 1 of the protocol. Payment is settled on Base via the USDC contract at `0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913`. There are no API keys or rate limits advertised. The lack of documentation about what the statements endpoint actually returns (schema, fields, account context) is a significant gap.

Capabilities

x402-paymentusdc-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 keys
  • —Agent-driven account data retrieval settled in USDC on Base

Fit

Best for

  • —Agents or services needing on-demand account statement access with crypto micropayments
  • —Developers who want keyless, pay-per-call API access
  • —Use cases where avoiding subscription commitments is preferred

Not for

  • —Users who need detailed API documentation or schema guarantees before integrating
  • —High-volume consumers who would benefit from bulk pricing or subscriptions
  • —Anyone requiring non-crypto payment methods

Quick start

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

Endpoint

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

Quality

0.30/ 1.00

The endpoint is live and returns a valid x402 challenge, but there is no OpenAPI schema, no request/response examples, and no meaningful documentation — the docs pages are empty beyond a wallet-connect prompt. The purpose of the 'account statements' endpoint is unclear and the account ID '111' appears hardcoded. Effectively a stub listing.

Warnings

  • —No OpenAPI schema or detailed documentation available; docs pages return only 'Connect wallet' with no content.
  • —The endpoint path includes a hardcoded account ID (111); unclear if this is parameterizable or a demo.
  • —No request body schema or response schema documented anywhere.
  • —The broader platform lists many API categories but none have visible documentation.

Citations

Provenance

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

Agent access

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