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/133` is part of the lowpaymentfee.com platform, which offers a broad catalog of pay-per-request APIs settled via the x402 protocol on the Base network using USDC. The specific endpoint is listed under "Premium API Access" but its exact functionality is unclear — the path suggests ACH (Automated Clearing House) payment-related data or operations, though no documentation describes the input/output schema for this particular route.
The platform advertises a flat $0.02 per request across all endpoints, with no API keys, no rate limits, and no minimum commitments. The x402 challenge confirms the endpoint is live, accepting POST requests and requiring payment of up to 20,000 base units of USDC (0.02 USDC = $0.02) on the Base network. Payment is made via the x402 `exact` scheme to the specified wallet address.
Documentation is extremely thin — the docs, pricing, API, and README pages all render only a "Connect wallet" prompt with no substantive content. There is no OpenAPI spec, no request/response schema, and no description of what `/api/v1/ach/133` actually returns. The platform lists many other endpoints (analytics, AI/ML, finance, crypto, utilities) at the same price point, but none have visible documentation either. Prospective users should be aware that the actual behavior of this endpoint is unverified beyond the x402 payment challenge.
Capabilities
Use cases
- —Querying ACH-related payment data or initiating ACH operations on a per-call basis
- —Integrating low-cost payment endpoints into agent workflows without managing API keys
- —Testing x402 micropayment flows on the Base network
Fit
Best for
- —Developers experimenting with x402 pay-per-call protocols
- —Agents needing keyless, on-demand API access settled in USDC
- —Low-volume or sporadic ACH-related queries where subscription pricing is wasteful
Not for
- —Production ACH payment processing requiring regulatory compliance and SLAs
- —Users who need detailed documentation or guaranteed uptime before integrating
- —High-volume use cases where per-request pricing may not be cost-effective
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/ach/133 \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-token>" \
-d '{}'Endpoint
Quality
The endpoint is live and returns a valid x402 challenge with clear pricing, but there is zero documentation on what the endpoint actually does, no request/response schema, and the docs pages are empty. The listing is effectively a stub with only the payment challenge as evidence of functionality.
Warnings
- —No documentation available — docs, pricing, API, and README pages all show only 'Connect wallet' with no content.
- —The exact purpose and behavior of /api/v1/ach/133 is unknown; the path suggests ACH payment operations but nothing confirms this.
- —No OpenAPI spec or input/output schema is provided.
- —No examples of successful responses are available.
- —The '133' in the path is unexplained — it may be a resource ID, version, or routing parameter.
Citations
- —The platform charges $0.02 per request with no API keys, no rate limits, and instant access on the Base network.https://lowpaymentfee.com
- —The x402 challenge confirms the endpoint is live, accepting POST, with maxAmountRequired of 20000 base units of USDC on Base.https://lowpaymentfee.com/api/v1/ach/133
- —USDC asset address 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Base network.https://lowpaymentfee.com/api/v1/ach/133
- —Docs, pricing, API, and README pages render only 'Connect wallet' with no substantive content.https://lowpaymentfee.com/docs