x402basequality 0.30

x402-gated account statements endpoint on Base, paid per-request in 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/136/statements`. It is part of a broader platform (lowpaymentfee.com) that offers a variety of x402-protocol APIs spanning data analytics, AI/ML inference, finance/Web3 data, and utility services — all payable per-request in USDC on the Base network with no API keys or rate limits required.

The specific endpoint probed here returns an x402 challenge requesting up to 20,000 base units of USDC (0x8335…2913 on Base). Since USDC uses 6 decimals, this translates to $0.02 per request, consistent with the site's advertised flat pricing of $0.02/request across all endpoints. Payment is made via the x402 exact scheme, settling to address 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3 with a 300-second timeout.

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 spec, no request/response schema, and no example payloads available. The endpoint's purpose ("account statements") and expected input/output format are not documented beyond the title "Premium API Access" and the MIME type `application/json`. The platform appears live and functional based on the 402 challenge, but without documentation it is difficult to know what data the statements endpoint actually returns or what POST body it expects.

Capabilities

x402-paymentusdc-baseper-request-billingaccount-statementsjson-api

Use cases

  • Retrieving account statement data via a pay-per-request model without API keys
  • Integrating x402-compatible agents that can autonomously pay for financial data
  • Accessing account-level financial records programmatically

Fit

Best for

  • Agents or applications that support x402 payment protocol on Base
  • Users who want keyless, pay-as-you-go access to account data
  • Developers experimenting with x402 micropayment-gated APIs

Not for

  • Users needing detailed API documentation or schema before integration
  • High-volume consumers who need bulk/subscription pricing
  • Anyone without a Base-network USDC wallet

Quick start

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

Endpoint

Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.30/ 1.00

The endpoint is live and returns a valid x402 challenge with clear pricing, but there is zero documentation on request/response schemas, no OpenAPI spec, and no examples. The /docs and other pages are empty. The purpose of the 'account statements' endpoint is unclear beyond its name.

Warnings

  • No API documentation available — /docs, /api, /pricing, and /README pages all show only 'Connect wallet' with no content.
  • No request or response schema is published; callers cannot know what POST body to send or what data is returned.
  • The endpoint path includes a hardcoded account ID (136); it is unclear whether other account IDs are supported or how they are obtained.
  • The platform lists many endpoints on its homepage but none have documented schemas or examples.

Citations

Provenance

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

Agent access