Pay-per-call ACH endpoint on Base via x402 — $0.02/request in USDC, no API keys required.
What it does
This endpoint at `/api/v1/ach/137` is part of the lowpaymentfee.com platform, which offers a collection of pay-per-request APIs spanning data & analytics, AI/ML inference, finance/Web3, and infrastructure utilities. All endpoints use the x402 payment protocol, settling in USDC on the Base network. The specific function of the `/api/v1/ach/137` path is not documented — the provider labels it generically as "Premium API Access" — so the exact data or service it returns is unclear.
Pricing is $0.02 per request (maxAmountRequired of 20,000 base units of USDC with 6 decimals = $0.02). Payment is made via the x402 `exact` scheme to address `0x1A2B...85F3` using USDC (`0x8335...2913`) on Base. No API keys, rate limits, or upfront commitments are advertised. The endpoint accepts HTTP POST and returned a valid 402 challenge during probing, confirming it is live.
Documentation is extremely sparse. The docs, pricing, API, and README pages all render only a "Connect wallet" prompt with no additional content. There is no OpenAPI spec, no request/response schema, and no description of what the `/ach/137` route specifically does. The site lists many other endpoints (analytics, AI, finance, utilities) at $0.02 each, but none share the `/ach/` path prefix, making it difficult to infer the purpose of this particular route.
Capabilities
Use cases
- —Programmatic access to an ACH-related service with per-call USDC payment
- —Agent-driven API consumption without pre-registration or API keys
- —Integrating x402-compatible payment flows into automated workflows
Fit
Best for
- —Developers or agents wanting zero-signup, pay-as-you-go API access
- —x402-compatible wallets and agents on Base network
- —Low-volume or exploratory usage where $0.02/call is acceptable
Not for
- —Users who need detailed documentation or guaranteed SLAs before integrating
- —High-volume batch processing where per-call pricing may add up
- —Anyone needing clarity on what the endpoint actually returns before paying
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/ach/137 \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-header>" \
-d '{}'Endpoint
Quality
The endpoint is live (valid 402 challenge captured) and pricing is clear ($0.02 USDC on Base), but there is no documentation, no OpenAPI spec, no request/response schema, and no description of what /api/v1/ach/137 actually does. The generic label 'Premium API Access' provides no useful information. This is effectively a stub listing.
Warnings
- —The specific purpose of /api/v1/ach/137 is completely undocumented — the provider only labels it 'Premium API Access'
- —No request or response schema is available; callers cannot know what to send or what to expect back
- —All documentation pages (docs, pricing, API, README) render only 'Connect wallet' with no content
- —The /ach/ path prefix does not appear among any of the other listed endpoints on the site, making it an outlier
- —ACH may relate to regulated financial services (Automated Clearing House); verify compliance requirements
Citations
- —Endpoint returns a valid x402 402 challenge with maxAmountRequired of 20000 USDC base units on Basehttps://lowpaymentfee.com/api/v1/ach/137
- —Site advertises $0.02/request pricing with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —USDC asset address 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Basehttps://lowpaymentfee.com/api/v1/ach/137
- —Docs, pricing, API, and README pages show only 'Connect wallet' with no documentation contenthttps://lowpaymentfee.com/docs