x402basequality 0.25

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 a "Premium API Access" resource at the path `/api/v1/accounts/35/balance`. It is part of a broader platform that offers dozens of pay-per-request API endpoints spanning data analytics, AI/ML inference, finance/Web3 data, and infrastructure utilities — all gated via the x402 payment protocol on the Base network.

The specific endpoint probed returns an x402 challenge requesting up to 20,000 base units of USDC (0x8335…2913 on Base, 6 decimals), which translates to $0.02 per request. Payment is made inline via the `X-PAYMENT` header using the x402 "exact" scheme; no API keys, accounts, or rate limits are required. The payment recipient is `0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3`, and the endpoint accepts POST requests returning `application/json`.

Documentation on the site is extremely thin — 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, and no explanation of what the `/accounts/35/balance` resource actually returns. The landing page lists many other endpoints at $0.02 each but provides no detail on inputs or outputs for any of them. Treat this listing as a stub until richer documentation becomes available.

Capabilities

x402-paymentusdc-basepay-per-requestaccount-balancejson-response

Use cases

  • Querying account balance data behind a per-request USDC paywall
  • Demonstrating x402 payment protocol integration on Base
  • Agent-driven balance lookups without API key provisioning

Fit

Best for

  • Developers experimenting with x402 pay-per-call patterns
  • Agents that can settle USDC payments on Base in real time
  • Use cases needing keyless, zero-commitment API access

Not for

  • Production workloads requiring documented request/response schemas
  • Users who need fiat-only payment options
  • High-volume batch queries where per-call pricing is inefficient

Quick start

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

Endpoint

Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.25/ 1.00

The endpoint is live (402 challenge captured) and pricing is clear ($0.02 USDC on Base), but there is no documentation, no request/response schema, and no explanation of what the balance resource actually returns. Effectively a stub.

Warnings

  • No OpenAPI spec or request/response schema available
  • All documentation pages (docs, pricing, api, README) render only a 'Connect wallet' prompt with no content
  • The purpose and output of /api/v1/accounts/35/balance is undocumented — unclear what 'account 35' refers to
  • Cannot verify what data is actually returned upon successful payment

Citations

Provenance

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

Agent access

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