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/101` is listed under "Premium API Access" and accepts POST requests. Payment is handled inline: callers attach an X-PAYMENT header with a signed USDC payment on Base, and the server fulfills the request once payment is verified. No API keys, accounts, or rate limits are advertised.
The x402 challenge captured from the endpoint confirms it is live, requesting a maximum of 20,000 base units of USDC (asset 0x8335…2913 on Base). Since USDC uses 6 decimals, this equals $0.02 per request, consistent with the site-wide pricing of $0.02/request. The payment recipient is 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3, and the timeout is 300 seconds.
The broader lowpaymentfee.com platform advertises endpoints across data/analytics, AI/ML (sentiment, summarization, classification, embeddings), finance/Web3 (price feeds, exchange rates, token quotes, gas estimates), and infrastructure utilities (geocoding, validation, conversion, generation). However, the specific functionality behind `/api/v1/ach/101` is not documented beyond the label "Premium API Access." No OpenAPI schema, request/response examples, or detailed docs were found — the docs, pricing, and API pages all render only a "Connect wallet" prompt with no additional content.
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 payment flows into automated pipelines
Fit
Best for
- —Developers or agents already using x402 payment protocol on Base
- —Use cases requiring no-signup, no-API-key access to paid endpoints
- —Micropayment-based API consumption without subscriptions
Not for
- —Users who need detailed documentation or OpenAPI specs before integrating
- —Anyone without a Base-network USDC wallet or x402-compatible client
- —Production workloads requiring SLA guarantees or support
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/ach/101 \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <signed-x402-payment-header>" \
-d '{}'Endpoint
Quality
The endpoint is live and returns a valid x402 challenge with clear pricing ($0.02 USDC on Base). However, there is no documentation of what the /api/v1/ach/101 endpoint actually does, no request/response schema, no OpenAPI spec, and no examples. The docs pages are empty beyond a wallet-connect prompt. The listing is effectively a stub.
Warnings
- —No documentation exists for the specific /api/v1/ach/101 endpoint — its actual functionality is unknown
- —All doc/pricing/API pages render only 'Connect wallet' with no usable content
- —No OpenAPI or request/response schema available
- —The label 'Premium API Access' is generic and does not describe what the endpoint returns
Citations
- —The endpoint returns a 402 challenge requesting 20000 base units of USDC (asset 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913) on Basehttps://lowpaymentfee.com/api/v1/ach/101
- —Site-wide pricing is $0.02 per request with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —The platform lists endpoints across data/analytics, AI/ML, finance/Web3, and infrastructure categorieshttps://lowpaymentfee.com