ACH routing number lookup via x402 micropayment on Base network, $0.02 per request.
What it does
This endpoint at `/api/v1/ach/122` is part of the lowpaymentfee.com platform, which offers a collection of pay-per-call APIs settled via the x402 protocol on the Base network using USDC. The specific endpoint appears to provide ACH-related data — likely a routing number lookup or validation service given the `/ach/122` path pattern (122 resembles the start of a US bank routing number). Each call costs $0.02 (20,000 base units of USDC with 6 decimals) and requires no API keys, accounts, or rate-limit management.
The platform advertises a broad catalog spanning data analytics, AI/ML inference, finance, crypto, and utility endpoints, all at a flat $0.02 per request. Payment is handled inline via the x402 `X-PAYMENT` header using the "exact" scheme on Base mainnet, settling to a specified wallet address in USDC (contract `0x8335…2913`). The x402 challenge was confirmed live, returning a proper 402 with version 1 challenge metadata.
Documentation is extremely sparse — the docs, pricing, API, and README pages all render only a "Connect wallet" prompt with no additional technical detail. There is no OpenAPI spec, no request/response schema, and no usage examples available from the crawl. The endpoint's exact input parameters and response format are unknown and must be discovered by making a paid call or contacting the provider.
Capabilities
Use cases
- —Looking up or validating US ACH bank routing numbers programmatically
- —Integrating routing number verification into payment onboarding flows
- —Agent-driven financial data retrieval without API key provisioning
Fit
Best for
- —Developers needing quick, keyless ACH routing lookups
- —AI agents that can settle x402 micropayments on Base
- —Applications requiring low-friction, pay-per-use bank data
Not for
- —Bulk batch processing of thousands of routing numbers (no documented batch endpoint)
- —Users who cannot transact in USDC on Base network
- —Anyone needing detailed documentation or SLA guarantees before integration
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/ach/122 \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-token>"Endpoint
Quality
The x402 challenge is live and pricing is clear ($0.02 USDC on Base), but there is no OpenAPI spec, no request/response schema, no documentation beyond a wallet-connect prompt, and the endpoint's exact purpose is inferred from the URL path rather than documented. Effectively a stub listing.
Warnings
- —No OpenAPI or schema documentation available — input/output formats are unknown
- —All doc/pricing/API/README pages return only a 'Connect wallet' prompt with no technical content
- —Endpoint purpose (ACH routing lookup) is inferred from the URL path '/ach/122' and is not confirmed by provider docs
- —No examples of request or response payloads available
Citations
- —The endpoint returns a live x402 challenge with maxAmountRequired of 20000 base units of USDC on Base networkhttps://lowpaymentfee.com/api/v1/ach/122
- —Platform 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/122