x402basequality 0.25

Pay-per-call ACH endpoint on Base via x402 — $0.02/request in USDC, no API keys required.

Price
0.02 USDC / call
Protocol
x402
Verified
no

What it does

This endpoint at `/api/v1/ach/54` is part of the lowpaymentfee.com platform, which offers a collection of pay-per-request APIs spanning data analytics, AI/ML inference, finance, crypto, and utility services. All endpoints use the x402 payment protocol, settling in USDC on the Base network. The specific function of the `/api/v1/ach/54` path is not documented — the provider labels it generically as "Premium API Access" — so the exact data or service it returns is unclear. The `ach` path segment suggests it may relate to ACH (Automated Clearing House) banking or payment data, but this is speculative.

Pricing is $0.02 per request (20,000 base units of USDC with 6 decimals = $0.02). Payment is handled inline via the x402 `X-PAYMENT` header; no API keys, accounts, or rate limits are advertised. The x402 challenge was successfully captured, confirming the endpoint is live and accepting POST requests on the Base network. The payment recipient address is `0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3`, and the USDC asset contract is `0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913` (canonical Base USDC).

Documentation is extremely thin. The docs, API, pricing, and README pages all render only a "Connect wallet" prompt with no substantive content. There is no OpenAPI spec, no request/response schema, and no description of what this specific endpoint returns. The landing page lists many other endpoints at $0.02 each but does not include `/api/v1/ach/54` in the visible catalog, making its purpose even less clear.

Capabilities

x402-paymentusdc-basepay-per-requestno-api-keypost-method

Use cases

  • Accessing a premium ACH-related data or service endpoint with per-call USDC payment
  • Integrating pay-per-request APIs into agent workflows without managing API keys
  • Testing x402 payment protocol integrations on Base

Fit

Best for

  • Developers experimenting with x402 pay-per-call protocols
  • Agents needing keyless, on-demand API access settled in USDC on Base
  • Low-volume or sporadic API usage where subscription pricing is wasteful

Not for

  • Users who need detailed API documentation or guaranteed SLAs before integrating
  • High-volume consumers who would benefit from bulk pricing or subscriptions
  • Anyone needing a clearly specified request/response contract upfront

Quick start

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

Endpoint

Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.25/ 1.00

The endpoint is live (402 challenge confirmed) and pricing is clear ($0.02 USDC on Base), but there is no documentation, no OpenAPI schema, no request/response examples, and the specific function of /api/v1/ach/54 is undocumented. The endpoint does not appear in the provider's own catalog. This is effectively a stub listing.

Warnings

  • The exact purpose and data returned by /api/v1/ach/54 is completely undocumented
  • No OpenAPI spec, request schema, or response schema available
  • Docs, pricing, and README pages render only 'Connect wallet' with no content
  • This endpoint path is not listed in the provider's own API catalog on the landing page
  • The 'ach' path segment may relate to regulated financial (ACH) data — verify compliance requirements

Citations

Provenance

Indexed fromx402_bazaar
Enriched2026-04-19 02:03:12Z · anthropic/claude-opus-4.6 · v2
First seen2026-04-18
Last seen2026-04-27

Agent access

Pay-per-call ACH endpoint on Base via x402 — $0.02/request in USDC, no API keys required. — Clawmart · Clawmart