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/197` is part of the lowpaymentfee.com platform, which offers a broad catalog 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/197` path is not documented — the "ACH" prefix and numeric ID suggest it may relate to ACH (Automated Clearing House) payment processing or lookup, but this is speculative since the provider's landing page does not list this particular route among its advertised APIs.
The endpoint is live and returns a valid x402 challenge (HTTP 402) requesting up to 20,000 base units of USDC (0x8335…2913 on Base), which equals $0.02 per request (USDC uses 6 decimals). The payment scheme is "exact" with a 300-second timeout. No API key or account registration is required — callers simply attach an X-PAYMENT header with a valid x402 payment proof. The response MIME type is `application/json`.
The broader lowpaymentfee.com platform advertises uniform $0.02/request pricing across all endpoints, with no rate limits and no minimum commitments. Documentation pages (`/docs`, `/pricing`, `/README`) returned only a "Connect wallet" prompt with no substantive content, so detailed request/response schemas for this endpoint are unavailable.
Capabilities
Use cases
- —Programmatic ACH payment data retrieval or processing
- —Agent-driven financial operations requiring per-call payment
- —Integrating low-cost API calls settled on-chain via USDC on Base
Fit
Best for
- —Developers wanting keyless, pay-as-you-go API access
- —AI agents that can settle x402 payments autonomously on Base
- —Projects needing low-cost per-request financial endpoints without subscriptions
Not for
- —Users who need detailed API documentation or OpenAPI schemas before integrating
- —High-volume use cases where per-request crypto settlement overhead is impractical
- —Anyone requiring non-crypto payment methods
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/ach/197 \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-proof>" \
-d '{}'Endpoint
Quality
The endpoint is live and returns a valid x402 challenge, but the specific purpose of /api/v1/ach/197 is undocumented. No request/response schema, no docs content (all doc pages show only 'Connect wallet'), and the endpoint is not listed among the provider's advertised APIs. Effectively a stub with confirmed liveness.
Warnings
- —The /api/v1/ach/197 endpoint is not listed among the provider's advertised APIs — its specific function is unknown.
- —All documentation pages (/docs, /pricing, /README) returned no substantive content, only a 'Connect wallet' prompt.
- —No request or response schema is available; callers must discover behavior empirically.
- —The 'ACH' label may imply regulated financial services — verify compliance requirements before use.
Citations
- —The endpoint returns a valid x402 challenge with maxAmountRequired of 20000 base units of USDC on Basehttps://lowpaymentfee.com/api/v1/ach/197
- —The platform advertises $0.02/request pricing with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/ach/197
- —Documentation pages returned only 'Connect wallet' with no substantive contenthttps://lowpaymentfee.com/docs