x402basequality 0.30

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/12

What it does

lowpaymentfee.com hosts a collection of pay-per-request API endpoints gated by the x402 protocol on the Base network. This specific endpoint (`/api/v1/ach/12`) is listed under "Premium API Access" and accepts POST requests. Payment is settled in USDC (contract `0x8335…2913` on Base) at a maximum cost of 20,000 base units, which equals $0.02 per call (USDC uses 6 decimals). No API keys, rate limits, or upfront commitments are required — callers simply attach an `X-PAYMENT` header with a valid x402 payment proof.

The broader lowpaymentfee.com platform advertises endpoints across several categories: Data & Analytics (metrics, reports, data export, insights), AI & Machine Learning (sentiment analysis, text summarization, classification, embeddings), Finance & Web3 (price feeds, exchange rates, token quotes, gas estimates), and Infrastructure utilities (geocoding, validation, conversion, generation). All endpoints are priced at $0.02 per request.

Documentation is extremely sparse — the docs, pricing, and README pages all render only a "Connect wallet" prompt with no further technical detail. There is no OpenAPI schema, no request/response examples, and no description of what the `/api/v1/ach/12` endpoint actually returns. The endpoint is live (returns a valid 402 challenge), but without documentation it is unclear what data or functionality "ACH" refers to in this context.

Capabilities

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

Use cases

  • —Accessing a premium ACH-related data or processing endpoint with per-call USDC micropayments
  • —Integrating pay-as-you-go API calls into agent workflows without managing API keys
  • —Settling API costs on-chain via Base L2 for transparent, auditable billing

Fit

Best for

  • —Developers wanting keyless, pay-per-request API access settled in USDC on Base
  • —AI agents that can autonomously pay for API calls via x402
  • —Users who prefer on-chain micropayments over subscription billing

Not for

  • —Anyone needing detailed API documentation or request/response schemas before integrating
  • —High-volume use cases where per-call pricing may be less economical than bulk plans
  • —Users who cannot transact in USDC on the Base network

Quick start

curl -X POST https://lowpaymentfee.com/api/v1/ach/12 \
  -H "Content-Type: application/json" \
  -H "X-PAYMENT: <x402-payment-proof>"

Endpoint

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

Quality

0.30/ 1.00

The endpoint is live and returns a valid x402 402 challenge with clear pricing, but there is no documentation, no OpenAPI schema, no request/response examples, and no explanation of what '/api/v1/ach/12' actually does. The docs pages are empty beyond a wallet-connect prompt. This is effectively a stub listing.

Warnings

  • —No documentation available — docs, pricing, and README pages all show only 'Connect wallet' with no content.
  • —No OpenAPI or request/response schema provided; it is unknown what input the endpoint expects or what it returns.
  • —The meaning of 'ACH' and the number '12' in the path is unexplained — unclear whether this relates to ACH bank transfers, a data resource, or something else.
  • —No examples of successful responses exist in the crawl material.

Citations

Provenance

Indexed fromx402_bazaar
Enriched2026-04-19 01:00:25Z · anthropic/claude-opus-4.6 · v2
First seen2026-04-18
Last seen2026-04-27

Agent access

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