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/26` 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/26` path is not documented — the listing title is simply "Premium API Access" and the endpoint lives under an `/ach/` path prefix that doesn't appear in the site's public API catalog. It may relate to ACH (Automated Clearing House) payment processing or financial data, but this is speculative.
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 `0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3` on Base. The platform advertises no API keys, no rate limits, and instant access. The endpoint accepts HTTP POST and returns `application/json`.
Documentation is extremely sparse. The docs, pricing, API, and README pages all render only a "Connect wallet" prompt with no substantive content. There is no OpenAPI schema, no request/response examples, and no description of what this specific endpoint does or what parameters it accepts. Users should proceed with caution and expect to experiment to discover the endpoint's actual functionality.
Capabilities
Use cases
- —Programmatic access to an ACH-related endpoint with per-call USDC micropayments
- —Agent-driven API consumption without API key management
- —Exploring x402 payment protocol integrations on Base
Fit
Best for
- —Developers experimenting with x402 pay-per-call protocols
- —Agents that need keyless, on-demand API access settled in USDC
- —Users comfortable with undocumented endpoints who can reverse-engineer request formats
Not for
- —Production workloads requiring well-documented, stable API contracts
- —Users who need detailed request/response schemas before integration
- —Anyone without a Base-network USDC wallet
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/ach/26 \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-header>" \
-d '{}'Endpoint
Quality
The endpoint is live (returns a valid 402 x402 challenge), but there is no documentation, no OpenAPI schema, no request/response examples, and the specific purpose of /api/v1/ach/26 is unknown. The crawled docs/pricing/API pages are all empty beyond a wallet-connect prompt. This is effectively a stub listing.
Warnings
- —The specific function of /api/v1/ach/26 is undocumented and not listed in the site's public API catalog
- —All documentation pages (docs, pricing, API, README) render only a 'Connect wallet' prompt with no content
- —No request parameters or response schema are available — callers must experiment blind
- —The /ach/ path prefix suggests possible financial/payment processing, which may involve regulated activity
Citations
- —Pricing is $0.02 per request with no API keys, no rate limits, and instant accesshttps://lowpaymentfee.com
- —maxAmountRequired is 20000 base units of USDC (USD Coin) on Base networkhttps://lowpaymentfee.com/api/v1/ach/26
- —The endpoint accepts HTTP POST and returns application/jsonhttps://lowpaymentfee.com/api/v1/ach/26
- —Payment is sent to address 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3https://lowpaymentfee.com/api/v1/ach/26
- —USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/ach/26