x402basequality 0.30

x402-gated account balance endpoint on Base, pay-per-call with USDC.

Price
0.02 USDC / call
Protocol
x402
Verified
no

What it does

This endpoint at lowpaymentfee.com provides an account balance lookup (account ID 70) behind an x402 paywall. It is part of a broader platform that offers a variety of pay-per-request APIs spanning data analytics, AI/ML inference, finance/Web3 data, and utility services — all settled on the Base network using USDC via the x402 protocol.

The specific endpoint `/api/v1/accounts/70/balance` accepts POST requests and returns JSON. The x402 challenge advertises a maximum cost of 20,000 base units of USDC (0x8335… on Base), which equals $0.02 per request (USDC uses 6 decimals). The platform's landing page confirms uniform $0.02/request pricing across all endpoints, with no API keys, no rate limits, and no minimum commitments required.

Documentation is extremely sparse — the /docs, /pricing, /api, and /README pages all render only a "Connect wallet" prompt with no further content. There is no OpenAPI spec, no request/response schema documentation, and no usage examples available. The endpoint is confirmed live (returns a proper 402 challenge), but without documentation it is unclear what request body the POST expects or what shape the balance response takes. The platform appears to be a demonstration or early-stage deployment of x402-based API monetization.

Capabilities

x402-paymentusdc-settlementbase-networkaccount-balancepay-per-requestno-api-keyjson-response

Use cases

  • Querying account balance data via a single paid API call
  • Demonstrating x402 protocol payment flows on Base
  • Integrating pay-per-request balance lookups into agent workflows

Fit

Best for

  • Developers experimenting with x402 protocol integrations
  • Agents needing simple pay-per-call balance queries without API key management
  • Testing USDC micropayment flows on Base

Not for

  • Production use requiring documented request/response schemas
  • High-volume balance queries where per-call pricing is inefficient
  • Users who need detailed API documentation before integration

Quick start

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

Endpoint

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 documentation, no OpenAPI spec, no request/response schema, and no examples. The docs pages are empty stubs. The purpose of this specific endpoint (account 70 balance) is unclear beyond its URL path. Effectively a stub listing.

Warnings

  • No API documentation available — /docs, /pricing, /api, and /README pages all show only 'Connect wallet' with no content
  • No OpenAPI or schema definition for request body or response format
  • Purpose of 'account 70 balance' is undocumented — unclear what data is returned
  • Platform appears to be early-stage or a demo; reliability and longevity are unknown

Citations

Provenance

Indexed fromx402_bazaar
Enriched2026-04-19 00:48:52Z · anthropic/claude-opus-4.6 · v2
First seen2026-04-18
Last seen2026-04-28

Agent access