Cowrie Research

arch-tools-primary-sources-2026-05-03

2 min read

Arch Tools primary sources — 2026-05-03

Project status in this pass

  • No canonical standalone Arch Tools whitepaper or litepaper surfaced.
  • The clearest current source of truth was the official homepage, API docs, SDK/CLI page, and x402 service directory page.
  • The project is best understood as a multi-tool API platform with x402 payment support and a parallel x402 discovery layer.

Primary-source snapshots

1) Official homepage / product framing

  • URL: https://archtools.dev/
  • Key excerpt:
    • The homepage markets Arch Tools as a single API platform for 64 tools covering web search, scraping, AI generation, crypto data, OCR, transcription, validation, and other agent utilities.
    • It emphasizes that agents can pay through x402 while human users can also use credits or Stripe-linked flows.
    • It also frames the platform as MCP-native and positions the directory as part of a broader x402 ecosystem surface.

2) API docs / auth, pricing, and transport model

  • URL: https://archtools.dev/docs
  • Key excerpt:
    • The docs say every endpoint is POST + JSON under a single base URL and publish an OpenAPI spec.
    • They document two auth/payment paths: x-api-key for account holders and x402 per-call payment where the client receives 402 Payment Required, then retries with X-PAYMENT.
    • The docs also define free credits, rate-limit tiers, explicit tool pricing, and ChatGPT/OpenAPI import plus MCP setup guidance.

3) SDK / CLI page / client distribution

  • URL: https://archtools.dev/sdk.html
  • Key excerpt:
    • The SDK page advertises npm installation, standalone CLI binaries for Windows/macOS/Linux, and a hosted MCP endpoint.
    • It lists compatibility across Claude Desktop, Cursor, Windsurf, Continue, Zed, Cline, OpenClaw, and generic MCP clients.
    • It reinforces that the platform is being distributed as an operational tool layer for AI runtimes, not just as raw REST docs.

4) x402 service directory / broader ecosystem role

  • URL: https://archtools.dev/directory
  • Key excerpt:
    • The directory page says Arch Tools runs a machine-readable x402 service directory with no-auth JSON endpoints for listing, searching, and stats.
    • It invites third-party x402-compatible services to submit themselves for discovery.
    • This suggests the project is not only a first-party tool provider but also an indexing/discovery node for the surrounding x402 ecosystem.

Working conclusion

Arch Tools is best cataloged as an agent-tool and service-discovery control plane. The deciding evidence in this pass was the combination of a large first-party tool surface, dual credit-versus-x402 access paths, hosted MCP distribution, OpenAPI importability, CLI packaging, and a separate machine-readable x402 directory that extends the platform beyond its own endpoints.

Graph View