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/106` 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/106` endpoint is not documented beyond the generic label "Premium API Access," so its exact purpose is unclear — the "ach" path segment suggests it may relate to ACH (Automated Clearing House) banking or payment data, but this is speculative.
The endpoint is live and returns a valid x402 challenge. It accepts POST requests and charges a maximum of 20,000 base units of USDC (0.02 USD) per call. Payment is made via the x402 `exact` scheme to the specified payTo address, with a 300-second timeout. The platform advertises no API keys, no rate limits, and instant access — you pay per request using an on-chain USDC micropayment on Base.
Documentation is extremely sparse. The landing page lists available API categories and a uniform $0.02 price, but the /docs, /api, /pricing, 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 usage examples available from the crawl. Without knowing the expected request body or response format, integrating this endpoint requires experimentation or contacting the provider.
Capabilities
Use cases
- —Accessing ACH or payment-related data on a per-request basis without subscription
- —Integrating pay-per-call financial endpoints into agent workflows
- —Testing x402 micropayment protocol integrations on Base
Fit
Best for
- —Developers experimenting with x402 pay-per-request APIs
- —Agents needing on-demand financial or ACH data without API key management
- —Low-volume or sporadic API usage where per-call pricing is preferable
Not for
- —High-volume production workloads where per-request crypto payments add latency and cost
- —Users who need detailed API documentation and guaranteed SLAs before integration
- —Non-crypto-native users who cannot send USDC on Base
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/ach/106 \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-header>" \
-d '{}'Endpoint
Quality
The endpoint is live and returns a valid x402 challenge, but there is zero documentation on what this specific endpoint does, what request body it expects, or what it returns. No OpenAPI spec, no examples, and the docs pages are empty. The 'ach/106' path and 'Premium API Access' label are the only clues to functionality.
Warnings
- —The exact purpose of /api/v1/ach/106 is undocumented — 'ACH' in the path is the only hint
- —All documentation pages (/docs, /api, /pricing, /README) return only 'Connect wallet' with no content
- —No request or response schema is available; integration requires trial and error
- —The 'ach' label may imply regulated financial data — verify compliance requirements
Citations
- —The endpoint returns a valid x402 challenge with maxAmountRequired of 20000 base units of USDC on Basehttps://lowpaymentfee.com/api/v1/ach/106
- —The platform charges $0.02 per request with no API keys, no rate limits, and instant accesshttps://lowpaymentfee.com
- —USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/ach/106
- —Documentation pages render only a 'Connect wallet' prompt with no further contenthttps://lowpaymentfee.com/docs