Arch Tools
- Name: Arch Tools
- URL: https://archtools.dev/
- Category: hosted tool shelf / x402 seller wrapper / directory packaging
- Tags: ethereum-ecosystem
- Summary: Arch Tools is a hosted x402 tool shelf with a small directory bolted on. Most of the tools are generic. The note matters because one operator controls hosting, pricing, distribution, and a bit of discovery across the bundle.
- What it does:
- Sells a bundled API surface for common agent utilities such as web search, scraping, OCR, extraction, transcription, and crypto data
- Supports both account-based credits and x402 pay-per-call flows for some requests
- Publishes MCP, OpenAPI, SDK, and CLI distribution paths so the same hosted tool set can be consumed from multiple agent clients
- Runs an x402 service directory with machine-readable discovery endpoints and provider submissions
- Key claims:
- This is operator packaging around a pile of ordinary utilities, not a category-defining service layer
- The docs describe both
x-api-keyaccess and x402 request flows where a client receives402 Payment Required, pays, and retries with a payment header - Hosted MCP access, OpenAPI import support, and SDK or CLI distribution matter more than any single tool in the shelf
- The directory layer is the interesting extra because Arch Tools wants a little discovery leverage over third-party x402 services too
- Whitepaper: No canonical standalone Arch Tools whitepaper or litepaper surfaced in this pass. The clearest current sources of truth were the official homepage, docs portal, SDK/CLI page, and x402 service directory page; see
../whitepapers/arch-tools-primary-sources-2026-05-03.md. - Sources:
Internal linkages
Control surface
-
The leverage sits in which utilities Arch hosts, which ones get x402 versus account-key access, how MCP and OpenAPI distribution are packaged, and what the directory admits or ranks.
-
Useful seller-and-directory packaging. Still not a payment rail or discovery standard.
-
Last reviewed: 2026-06-18 UTC