Docs

Documentation

Everything you need to choose a door, set up the right runtime, and connect APIClaw to your agent stack.

Install

Local MCP setup for Claude Desktop, Cursor, and other local clients. The full OS-specific install flow lives on the install page.

Auto-install to Claude Desktop

Or run the MCP server directly

Bare npx @nordsym/apiclaw (no subcommand) does the same thing.

OS-specific commands for macOS, Windows, and Linux live in the install guide. Use this page as the hub, not the full manual.

Auth

One command, every door. Opens your browser, one-tap sign-in via Clerk (Google or passwordless email), writes ~/.apiclaw.toml with mode 0600. The same file is read by the local MCP server, CLI, and HTTP gateway. Remote MCP uses its own OAuth 2.1 + DCR flow.

Canonical flow

If you are already signed into Clerk in your browser there is no inbox round-trip, no key copy-paste, no dashboard visit.

Switch accounts

Show current identity

Headless server or SSH

On a machine with a browser: npx @nordsym/apiclaw auth login writes ~/.apiclaw.toml with your api_key. On a machine with no browser at all, skip the CLI entirely: create a key in Workspace, Connections and set APICLAW_API_KEY in the environment instead.

For MCP clients: agent_auth_required action

When the APIClaw MCP server has no local session, every tool returns a JSON payload with action: "agent_auth_required" and the exact CLI command to run. Agents that recognize this contract can resolve auth without human intervention.

CLI

Terminal-native use for Codex, scripts, and CI/CD. Codex is one example, not the whole category. Run apiclaw auth login first (see Auth above), then use the direct commands below.

Buzz and other ACP (Agent Client Protocol) clients spawn npx @nordsym/apiclaw acp over stdio instead.

Direct tool parity

apiclaw discover "currency conversion"
apiclaw details apilayer/fixer-latest
apiclaw call apilayer/fixer-latest --params '{"base":"USD","symbols":"EUR"}'
apiclaw balance

Install APIClaw into Codex / Cursor / Windsurf

Check status

Shows CLI path, auth status, connection health, and all client configurations.

HTTP

Server-side agents and custom runtimes. Use it from OpenClaw or any backend that sends requests with a workspace API key.

Endpoint
https://api.apiclaw.cloud/v1
Default model
apiclaw/openai/gpt-5.4-20260305
API key
sk-claw-...

On a machine with a browser: run apiclaw auth login and the key is written to ~/.apiclaw.toml. On a headless machine: create a key in Workspace, Connections and set APICLAW_API_KEY in the environment.

Environment config

OPENAI_BASE_URL=https://api.apiclaw.cloud/v1
OPENAI_API_KEY=sk-claw-<your-workspace-key>

Override route or model per request

Response includes _apiclaw metadata: provider used, route reason, model resolved.

Remote MCP

Connected clients go through your workspace. Sign in first, then open Integrations to add or edit a connector. Grok, ChatGPT, Cursor, and other OAuth-capable clients fit here.

  1. Step 1

    Free email signup

    Required for every door.

  2. Step 2

    Workspace

    Same auth, same logs, same gateway.

  3. Step 3

    Integrations

    Generate a connector for your client.

Bring your own key

You do not need your own keys. APIClaw's point is one sign-in, no key collecting. If your workspace already has its own OpenRouter key, you can add it in Workspace, Connections, Your keys, and route calls through it for free: no card, no markup, OpenRouter bills your workspace directly instead of going through the built-in rail. Today this covers an OpenRouter key for POST /v1/chat/completions, not every provider.

An APIClaw key (sk-claw-...) authenticates a client into the gateway. A provider key is different: it is the workspace's own credential for an upstream provider, kept encrypted server-side and never returned decrypted.

Examples

NASA Astronomy Picture of the Day

// First call: POST /v1/execute
call_api({
  provider: "nasa",
  action: "apod",
  params: {}
})

Search the web

call_api({
  provider: "brave_search",
  endpoint: "search",
  params: { query: "best MCP servers 2026" }
})

Latest EUR exchange rates

call_api({
  provider: "apilayer",
  action: "fixer_latest",
  params: { base: "EUR" }
})

Tools Reference

apiclaw_help

Get help and see all available commands. Start here if you're new.

apiclaw_help()

discover_apis

Search 26,619 discoverable APIs using natural language.

discover_apis({
  query: "send alerts to Sweden",
  max_results: 5
})

Parameters

  • query: Natural language description
  • category: Filter: communication, search, ai
  • max_results: Number of results (default: 5)
  • region: Filter by region (e.g., "sweden")

get_api_details

Get detailed information about a specific API.

get_api_details({
  api_id: "nasa"
})

get_connected_providers

List all built-in providers (no API key needed).

get_connected_providers()

Currently available

  • openrouter: 800+ LLMs
  • brave_search: Web search
  • github: Read-only GitHub
  • nasa: Astronomy Picture of the Day
  • apilayer: Fixer latest (EUR base) and other contracted HTTPS rails

call_api

Execute an API call through a built-in provider.

call_api({
  provider: "brave_search",
  endpoint: "search",
  params: { query: "AI agents 2026" }
})

list_categories

Browse all API categories (30 main categories).

list_categories()

Catalog numbers

Source verification is not execution: a source-verified entry passed a reachability check, not a customer call.

  • 26,619 API definitionsDiscoverable by agents via the catalog.
  • 1,025 callable nowWhat a workspace can execute today, of which 22 are built-in providers. Keyless public origins are Free; built-in providers are Free when the upstream API is free and Paid otherwise.
  • 689 source-verifiedPassed a live reachability check against the source. Not a claim of execution.

Support

Need help? Reach out.

List your API on APIClaw

APIClaw indexes 26,619 APIs and 689 have source-verified definitions. Callable readiness is shown separately. Adding yours takes one OpenAPI spec and a free email signup.

  1. 01

    Use the same workspace

    Sign in at apiclaw.cloud/workspace. The same workspace covers your discoverable listing and any agent calls you make.

  2. 02

    Submit your spec

    Open Workspace, My APIs, Add API. Paste an OpenAPI 3 / Swagger URL, or describe the endpoint manually. APIClaw normalises auth, parameters, and pricing.

  3. 03

    Approve the listing

    Review the auto-generated capability tags (the keywords agents will match on), the pricing model, and a working example. Edit any field before going live.

  4. 04

    Live and discoverable

    Your API is searchable by discover_apis immediately. Per-call analytics show in your dashboard from the first agent that calls you.

  5. 05

    Optional: partner upgrade

    Hand APIClaw the credential. We hold custody and agents call without keys. Commercial terms (flat fee, share, or hybrid) are agreed per partner.

Always free

Listing your API is free. Always. The partner upgrade is opt-in.

List your API