APIClaw

Your agent calls real APIs.You sign in once.

Paste one line to your agent. It signs in, finds the API, and makes the call.

Using MCP, CLI or HTTP instead? Choose a path ↓
first run
set up https://apiclaw.cloud/SKILL.md
readapiclaw.cloud/SKILL.mdok
authnpx @nordsym/apiclaw auth loginsigned in
executePOST /v1/execute nasa/apod200

Connect

Choose how to connect.

For any agent that can read a URL.

It reads SKILL.md, signs you in through the browser, and makes its first call. It never asks for a token.

Read SKILL.md

Same sign-in and workspace behind every path.

Discover, execute, observe.

  1. 01

    Discover

    Search by capability. Results say what is callable now.

  2. 02

    Execute

    One call shape for every provider. Keys stay server-side.

  3. 03

    Observe

    Every call logged with provider, cost and latency.

Live today.

26,619
discoverable APIs
1,025
callable now

Pricing

Free APIs are free forever. Paid APIs bill provider cost plus 15% after you add a card.

Need custom limits or an SLA? Talk to us.

Free APIs

$0

forever

Free forever, every zero-cost API, no card

  • Discovery and every zero-cost API
  • Free forever
  • No card, no counter
Start free

Paid APIs

Recommended
Usage

based

Pay per call provider cost plus 15%, after you add a card

  • Everything in Free
  • Provider cost plus 15%
  • Add a card once, pay per call
Start free

Own an API? List it free and agents can find it by capability.

List your API

Questions.

What is APIClaw?
An authenticated discovery and execution layer for AI agents. One workspace covers API discovery, callable execution, missions and observability, reachable through a skill file, local MCP, CLI, HTTP and Remote MCP.
How does my agent connect?
Give it set up https://apiclaw.cloud/SKILL.md. The agent reads the file, runs npx @nordsym/apiclaw auth login, and lands its first POST /v1/execute. Humans can use the same package for local MCP, CLI, HTTP or Remote MCP. One sign-in covers every path. Never paste a token into chat.
Do I have to sign up?
Yes. A free workspace is required for every path, including discovery. Sign-in is the signup: the first login creates the workspace through Clerk with Google or passwordless email and writes ~/.apiclaw.toml.
How are credentials secured?
Provider keys live server-side, encrypted at rest, and never reach the agent. Workspace keys are stored as one-way hashes; the raw value is shown once at creation and never again.
What does it cost?
Free APIs are free forever, no card, including discovery and over 1,000 of the 1,025 callable now. Paid APIs need a card on file and bill provider cost plus 15% per call, billed through Stripe.
What does Remote MCP expose?
Remote MCP surface (14 tools): apiclaw_help, discover_apis, get_api_details, list_categories, list_connected, list_models, call_api, check_balance, check_workspace_status, list_mission_templates, start_mission, discover_missions, mission_status, list_missions.
Can I use my own API key instead of a card?
Yes, if you already have an OpenRouter key you can add it under Workspace, Connections, Your keys and calls routed through it are free. Most workspaces never need this: Free APIs need no key at all.