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/174` 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/174` path is not documented — the listing title is simply "Premium API Access" and no schema or documentation describes what this particular route returns. The broader platform advertises categories like ACH (likely related to financial/payment data), but concrete input/output details are unavailable.
Pricing is $0.02 per request (20,000 base units of USDC with 6 decimals = $0.02). Payment is handled inline via the x402 `X-PAYMENT` header — no API keys, accounts, or rate limits are advertised. The endpoint is live and returns a valid 402 challenge when called without payment. The platform's documentation, pricing, and README pages all resolve but contain no substantive content beyond a "Connect wallet" prompt, so the actual behavior of this endpoint remains opaque.
Because there is no OpenAPI spec, no request/response examples, and no description of what data this endpoint provides, agents should treat this as a low-documentation endpoint. It may be useful for experimentation with x402 payment flows on Base, but its practical utility cannot be confirmed without further probing.
Capabilities
Use cases
- —Testing x402 payment protocol integrations on Base
- —Accessing ACH-related financial data (unconfirmed)
- —Agent-driven pay-per-call API consumption without API key management
Fit
Best for
- —Developers experimenting with x402 payment flows
- —Agents that need keyless, pay-per-request API access on Base
- —Prototyping micropayment-gated API architectures
Not for
- —Production use cases requiring documented input/output schemas
- —Users needing detailed API documentation or support
- —High-volume batch processing where per-request pricing is inefficient
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/ach/174 \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-token>"Endpoint
Quality
The endpoint is live and returns a valid x402 402 challenge, but there is zero documentation on what the endpoint actually does, no OpenAPI spec, no request/response examples, and the docs/pricing/README pages are empty. The listing is effectively a stub.
Warnings
- —No documentation exists for /api/v1/ach/174 — its purpose and data returned are unknown
- —All doc pages (docs, pricing, README, api) render only a 'Connect wallet' prompt with no content
- —No OpenAPI or schema available for request or response formats
- —The 'ACH' path segment suggests financial/payment data but this is unconfirmed
Citations
- —Endpoint returns a valid x402 402 challenge with USDC on Base networkhttps://lowpaymentfee.com/api/v1/ach/174
- —Platform advertises $0.02/request pricing with no API keys, no rate limitshttps://lowpaymentfee.com
- —USDC asset contract 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Basehttps://lowpaymentfee.com/api/v1/ach/174
- —maxAmountRequired is 20000 base units (USDC 6 decimals = $0.02)https://lowpaymentfee.com/api/v1/ach/174