x402basequality 0.25

Pay-per-call ACH endpoint on Base via x402 — $0.02/request in USDC, no API keys required.

Price
0.02 USDC / call
Protocol
x402
Verified
no
Endpoint
https://lowpaymentfee.com/api/v1/ach/162

What it does

This endpoint at `/api/v1/ach/162` 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/162` path is not documented — the provider labels it generically as "Premium API Access" — so its exact capabilities are unclear. It may relate to ACH (Automated Clearing House) payment processing or data, but this is speculative based solely on the URL path.

Pricing is $0.02 per request (20,000 base units of USDC with 6 decimals = $0.02), consistent with the platform's uniform pricing across all listed endpoints. The x402 challenge confirms the endpoint is live, accepts POST requests, and settles payments to address `0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3` on Base. No API keys, rate limits, or upfront commitments are required — callers simply attach an x402 payment header to each request.

Documentation is extremely sparse. The docs, API, pricing, and README pages all render only a "Connect wallet" prompt with no substantive content. There is no OpenAPI schema, no request/response examples, and no description of what this specific endpoint accepts or returns. The platform lists many other endpoints on its landing page, but `/api/v1/ach/162` is not among them, making it difficult to determine its intended use case.

Capabilities

x402-paymentusdc-settlementbase-networkpay-per-requestno-api-keyach-endpoint

Use cases

  • —Accessing ACH-related data or functionality on a per-request basis
  • —Integrating pay-per-call financial endpoints into agent workflows
  • —Testing x402 payment protocol integrations with low-cost endpoints

Fit

Best for

  • —Developers experimenting with x402 payment protocol
  • —Agents needing low-cost per-call API access without API key management
  • —Use cases requiring USDC-settled micropayments on Base

Not for

  • —Users who need documented request/response schemas before integrating
  • —High-volume production workloads where endpoint behavior is unverified
  • —Anyone needing ACH transaction initiation (no evidence this endpoint supports that)

Quick start

curl -X POST https://lowpaymentfee.com/api/v1/ach/162 \
  -H "Content-Type: application/json" \
  -H "X-PAYMENT: <x402-payment-token>" \
  -d '{}'

Endpoint

URLhttps://lowpaymentfee.com/api/v1/ach/162
Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.25/ 1.00

The endpoint is live (402 challenge confirmed) and pricing is clear ($0.02/request in USDC on Base), but there is no documentation, no OpenAPI schema, no request/response examples, and the specific function of /api/v1/ach/162 is unknown. The endpoint is not listed on the provider's own landing page. This is effectively a stub listing.

Warnings

  • —The exact purpose and functionality of /api/v1/ach/162 is undocumented and unknown
  • —No OpenAPI schema, request format, or response format is available
  • —The endpoint does not appear in the provider's own listed API catalog
  • —Docs, pricing, API, and README pages all render only 'Connect wallet' with no content
  • —Cannot verify what data or service this endpoint actually provides

Citations

Provenance

Indexed fromx402_bazaar
Enriched2026-04-19 02:08:56Z · anthropic/claude-opus-4.6 · v2
First seen2026-04-18
Last seen2026-04-27

Agent access

JSONhttps://clawmart.sh/api/listings/U8b5zy
Pay-per-call ACH endpoint on Base via x402 — $0.02/request in USDC, no API keys required. — Clawmart · Clawmart