Pay-per-call ACH endpoint on Base via x402 — $0.02/request in USDC, no API keys required.
What it does
lowpaymentfee.com hosts a collection of pay-per-request API endpoints settled via the x402 protocol on the Base network using USDC. The specific endpoint at `/api/v1/ach/24` is listed under "Premium API Access" and accepts POST requests. Payment is made per-call by attaching an X-PAYMENT header; no API keys, accounts, or rate limits are advertised.
The x402 challenge confirms the endpoint is live, requesting up to 20,000 base units of USDC (0x8335…2913 on Base). Since USDC uses 6 decimals, this translates to $0.02 per request, consistent with the site-wide pricing of $0.02/request. The payment is sent to address 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3 with a 300-second timeout.
The broader lowpaymentfee.com platform advertises endpoints across several categories — data/analytics, AI/ML (sentiment, summarization, classification, embeddings), finance/Web3 (price feeds, exchange rates, gas estimates), and infrastructure utilities (geocoding, validation, conversion). However, documentation is extremely sparse: the docs, API, pricing, and README pages all render only a "Connect wallet" prompt with no further technical detail. There is no OpenAPI spec, no request/response schema documentation, and no example payloads available for this or any other endpoint. The exact functionality of the `/api/v1/ach/24` path — what "ACH" refers to or what the `24` parameter means — is not documented anywhere in the crawled material.
Capabilities
Use cases
- —Programmatic access to an ACH-related service with per-call USDC micropayments
- —Agent-driven workflows that need keyless, pay-as-you-go API access on Base
- —Integrating x402-compatible endpoints into automated pipelines without subscription overhead
Fit
Best for
- —Developers or agents already using x402-compatible wallets on Base
- —Use cases requiring no-signup, no-rate-limit API access
- —Micropayment-settled one-shot API calls
Not for
- —Users who need detailed API documentation or response schemas before integrating
- —High-volume use cases where per-call pricing may add up without volume discounts
- —Anyone without a Base-compatible USDC wallet
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/ach/24 \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-header>" \
-d '{}'Endpoint
Quality
The endpoint is live (402 challenge confirmed) and pricing is clear ($0.02 USDC on Base), but there is zero documentation on what the endpoint actually does, no request/response schemas, no examples, and the docs pages are empty. The purpose of '/api/v1/ach/24' is entirely unclear.
Warnings
- —No documentation exists for this endpoint — docs, API, pricing, and README pages all show only 'Connect wallet'
- —The meaning of 'ach/24' in the path is undocumented; it is unclear what this endpoint returns or expects
- —No OpenAPI spec or output schema is provided
- —No request body or response body examples are available anywhere in the crawled material
- —The platform lists many endpoint categories but none have visible documentation
Citations
- —The x402 challenge returns maxAmountRequired of 20000 base units of USDC on Base (= $0.02)https://lowpaymentfee.com/api/v1/ach/24
- —Site-wide pricing is listed as $0.02/request with no API keys, no rate limits, instant accesshttps://lowpaymentfee.com
- —The USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/ach/24
- —Docs, API, pricing, and README pages render only 'Connect wallet' with no further contenthttps://lowpaymentfee.com/docs