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/81` 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/81` path is not documented — the listing title is simply "Premium API Access" — so the exact data or service it returns is unclear. It may relate to ACH (Automated Clearing House) banking data or routing information given the URL path, but this is speculative.
The endpoint is live and returns a valid x402 challenge. Pricing is $0.02 per request (20,000 base units of USDC with 6 decimals = $0.02), consistent with the site-wide flat rate. Payment is made via the x402 `exact` scheme to a specified wallet address on Base. No API keys, rate limits, or subscriptions are required — callers simply attach an `X-PAYMENT` header with a valid x402 payment proof.
Documentation is extremely sparse. The docs, pricing, API, and README pages all render only a "Connect wallet" prompt with no additional content. There is no OpenAPI schema, no request/response examples, and no description of what this specific endpoint accepts or returns beyond `application/json`. Prospective users should be aware that the actual functionality behind this path is undocumented.
Capabilities
Use cases
- —Programmatic access to an ACH-related data endpoint with per-call USDC payment
- —Agent-driven API consumption without pre-registration or API key management
- —Integrating pay-as-you-go API calls into crypto-native workflows on Base
Fit
Best for
- —Developers wanting zero-signup, pay-per-request API access
- —Crypto-native agents that can settle USDC on Base
- —Exploring x402 protocol integrations with minimal commitment
Not for
- —Users needing well-documented, production-grade ACH banking integrations
- —Anyone requiring detailed OpenAPI specs or request/response schemas before integration
- —High-volume use cases where per-call pricing may be inefficient
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/ach/81 \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-proof>" \
-d '{}'Endpoint
Quality
The endpoint is live and returns a valid x402 402 challenge, but there is zero documentation on what /api/v1/ach/81 actually does, no request/response schema, no examples, and all doc pages are empty. The listing is effectively a stub with confirmed liveness and pricing.
Warnings
- —The specific functionality of /api/v1/ach/81 is completely undocumented — the 'ACH' path segment is the only hint at its purpose.
- —All documentation pages (docs, pricing, API, README) render only 'Connect wallet' with no usable content.
- —No OpenAPI schema, no request body schema, and no response examples are available.
- —The endpoint description 'Premium API Access' is generic and does not describe the service.
Citations
- —The endpoint returns a valid x402 challenge with maxAmountRequired of 20000 in USDC on Basehttps://lowpaymentfee.com/api/v1/ach/81
- —Site-wide pricing is $0.02 per request with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/ach/81
- —Documentation pages render only 'Connect wallet' with no additional contenthttps://lowpaymentfee.com/docs