Pay-per-request ACH endpoint on Base via x402 — $0.02/call in USDC, no API keys required.
What it does
This endpoint at `/api/v1/ach/141` is part of the lowpaymentfee.com platform, which offers a collection of pay-per-call 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 platform advertises a flat $0.02 per request with no API keys, no rate limits, and no minimum commitments.
The specific endpoint `/api/v1/ach/141` is listed under the title "Premium API Access" but its exact functionality is unclear — the path suggests ACH (Automated Clearing House) banking-related data or operations, but no documentation, request/response schema, or usage examples are available. The x402 challenge confirms the endpoint is live, accepts POST requests, and requires up to 20,000 base units of USDC (0.02 USDC, i.e., $0.02) per call on the Base network. Payment is made via the x402 `exact` scheme to address `0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3`.
The provider's documentation pages (`/docs`, `/pricing`, `/api`, `/README`) all returned only a "Connect wallet" prompt with no substantive content, so the actual request format, expected input parameters, and response structure for this endpoint remain unknown.
Capabilities
Use cases
- —Programmatic access to ACH-related data or operations via a single micropayment per call
- —Agent-driven financial workflows that need keyless, pay-as-you-go API access
- —Integrating low-cost banking/payment data into automated pipelines
Fit
Best for
- —Developers wanting keyless, pay-per-use API access settled in USDC on Base
- —AI agents that can pay per call via x402 without pre-registration
- —Prototyping financial integrations with minimal upfront cost
Not for
- —Users who need detailed API documentation or guaranteed SLAs before integrating
- —High-volume production workloads where per-call pricing may not be cost-effective
- —Anyone requiring non-crypto payment methods
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/ach/141 \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-header>" \
-d '{}'Endpoint
Quality
The endpoint is confirmed live via a valid x402 402 challenge, but there is no documentation, no request/response schema, no examples, and the endpoint's actual functionality ("ACH/141") is unexplained. All doc pages return only a wallet-connect prompt. This is effectively a stub listing.
Warnings
- —No documentation available — all doc pages return only 'Connect wallet' with no content
- —Exact functionality of /api/v1/ach/141 is unknown; 'Premium API Access' is a generic label
- —No request or response schema provided; callers cannot know what parameters to send or what to expect
- —The endpoint path suggests ACH banking operations but this is unconfirmed
Citations
- —The endpoint returns a valid x402 challenge with maxAmountRequired of 20000 base units of USDC on Basehttps://lowpaymentfee.com/api/v1/ach/141
- —Platform advertises $0.02/request, no API keys, no rate limits, instant access on Base networkhttps://lowpaymentfee.com
- —USDC asset contract on Base: 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/ach/141
- —Documentation pages (/docs, /pricing, /api, /README) returned only 'Connect wallet' with no substantive contenthttps://lowpaymentfee.com/docs