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/139` 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 protocol on the Base network, accepting USDC payments with no API keys, no rate limits, and no upfront commitments.
The specific endpoint `/api/v1/ach/139` is listed under the title "Premium API Access" but its exact functionality is not documented in the available crawl material. The provider's site groups endpoints into categories (Data & Analytics, AI & Machine Learning, Finance & Web3, Infrastructure), but this particular path (`/ach/139`) does not appear in any of those listed categories. The x402 challenge confirms the endpoint is live, accepts POST requests, and requires a maximum of 20,000 base units of USDC (0.02 USD) per call on the Base network, settling to address `0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3`.
Documentation is extremely sparse — the docs, pricing, API, and README pages all render only a "Connect wallet" prompt with no further content. Without additional documentation, the request schema, response format, and actual purpose of this endpoint remain unknown. Prospective callers should be aware that the endpoint's function cannot be verified from public materials alone.
Capabilities
Use cases
- —Programmatic access to an ACH-related service with per-call USDC micropayments
- —Agent-driven API consumption without pre-registration or API key management
- —Integrating pay-as-you-go endpoints into automated workflows on Base
Fit
Best for
- —Developers wanting keyless, pay-per-request API access
- —AI agents that can settle x402 payments in USDC on Base
- —Users who prefer no-commitment, usage-based pricing
Not for
- —Users who need detailed documentation or guaranteed SLAs before integrating
- —Applications requiring free or subscription-based access
- —Anyone needing clarity on what the endpoint actually returns before paying
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/ach/139 \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-header>" \
-d '{}'Endpoint
Quality
The endpoint is live and returns a valid x402 challenge, but there is no documentation, no request/response schema, and the actual functionality of /api/v1/ach/139 is completely undocumented. The 'Premium API Access' title is generic and uninformative. This is effectively a stub listing.
Warnings
- —The exact purpose and functionality of /api/v1/ach/139 is unknown — it does not appear in the provider's listed API catalog.
- —All documentation pages (docs, pricing, API, README) render only 'Connect wallet' with no usable content.
- —No request or response schema is available; callers cannot know what to send or what to expect back.
- —The endpoint path suggests ACH (Automated Clearing House) banking functionality, which may involve regulated financial services — exercise caution.
Citations
- —The endpoint returns a valid x402 challenge with maxAmountRequired of 20000 base units of USDC on Basehttps://lowpaymentfee.com/api/v1/ach/139
- —The platform advertises $0.02/request pricing with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —The /api/v1/ach/139 path does not appear in the provider's listed API catalog on the homepagehttps://lowpaymentfee.com
- —Documentation pages render only 'Connect wallet' with no further contenthttps://lowpaymentfee.com/docs