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

What it does

This endpoint at `/api/v1/ach/89` is part of the lowpaymentfee.com platform, which offers a broad catalog of pay-per-request APIs spanning data analytics, AI/ML inference, finance/Web3, and infrastructure utilities. All endpoints use the x402 payment protocol, settling in USDC on the Base network. The specific resource at `/api/v1/ach/89` is labeled "Premium API Access" but its exact functionality is unclear — the path suggests it may relate to ACH (Automated Clearing House) payment processing or data, though no documentation beyond the listing title confirms this.

Pricing is $0.02 per request (maxAmountRequired of 20,000 base units of USDC with 6 decimals = $0.02). Payment is made via the x402 exact scheme to address `0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3` using the USDC contract on Base (`0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913`). The endpoint accepts POST requests and returns `application/json`. No API keys, rate limits, or subscriptions are required — each call is independently paid.

Documentation is extremely sparse. The crawled docs, pricing, API, and README pages all returned 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 actually does or what parameters it accepts. The endpoint is confirmed live (402 challenge returned), but without further documentation it is difficult to know what data to send or what response to expect.

Capabilities

x402-paymentusdc-settlementbase-networkpay-per-requestno-api-keyjson-responsepost-method

Use cases

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

Fit

Best for

  • Developers experimenting with x402 payment protocol
  • Agent-based systems needing keyless, pay-per-call API access
  • Low-volume or sporadic API usage where subscriptions are undesirable

Not for

  • Production workloads requiring well-documented, schema-validated APIs
  • High-volume use cases where per-request pricing at $0.02 adds up quickly
  • Users who need detailed documentation or support before integrating

Quick start

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

Endpoint

Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.25/ 1.00

The endpoint is confirmed live via a valid 402 challenge, but documentation is essentially nonexistent — no OpenAPI schema, no request/response examples, and no description of what /api/v1/ach/89 actually does. The listing title 'Premium API Access' is generic and uninformative. Score reflects a live but undocumented stub.

Warnings

  • No documentation available — docs, pricing, API, and README pages all return only a 'Connect wallet' prompt with no content.
  • The exact purpose of /api/v1/ach/89 is unknown; the 'Premium API Access' label is generic.
  • No request or response schema is provided; callers cannot know what parameters to send or what to expect back.
  • No OpenAPI specification or examples found anywhere on the site.
  • This endpoint may involve financial/payment (ACH) functionality which could be subject to regulatory requirements.

Citations

Provenance

Indexed fromx402_bazaar
Enriched2026-04-19 02:05:41Z · anthropic/claude-opus-4.6 · v2
First seen2026-04-18
Last seen2026-04-30

Agent access