APIClaw
<div align="center">

# APIClaw 🦞
[](https://apiclaw.cloud/docs)
[](https://x.com/APIClaw)
[](./LICENSE)
[](https://nordsym.com)
[](https://www.npmjs.com/package/@nordsym/apiclaw)
[](https://www.npmjs.com/package/@nordsym/apiclaw)
</div>
---
> Your agent calls real APIs. You sign in once.
## Start
```text
set up https://apiclaw.cloud/SKILL.md
```
Or pick a path directly:
```bash
# Local MCP on a machine the human can see (Claude Desktop, Cursor, Windsurf, OpenClaw)
npm install -g @nordsym/apiclaw && npx @nordsym/apiclaw auth login
# CLI (only after whoami prints an email)
npx @nordsym/apiclaw call nasa/apod --params '{}'
# HTTP gateway
curl https://api.apiclaw.cloud/v1/execute -H "Authorization: Bearer sk-claw-..."
# Remote MCP
https://apiclaw.cloud/mcp
```
On headless, Grok, or cloud: show the first-line `https://apiclaw.cloud/auth/cli?authId=…` URL from unsigned first_run and stop. Do not run `auth login` there — that opens a browser they will never get. After Authorize, whoami and the first call stay in the same chat. Workspace is optional. Terminal.app is not the product.
`auth login` on a machine they can see writes `~/.apiclaw.toml`. The same credential works across every path.
---
## What it is
APIClaw is the authenticated execution and discovery layer for AI agents. An agent reaches it through SKILL.md, local MCP, CLI, HTTP, or Remote MCP, signs in once through the browser, discovers APIs by capability, and executes calls with credentials kept server-side. 26,619 API definitions discoverable, 1,025 callable now.
Route across supported models from OpenAI, Anthropic, [OpenRouter](https://openrouter.ai), xAI, Groq, Mistral, Cohere, DeepInfra, or a configured endpoint. Switch with one parameter, no SDK swap, no lock-in.
---
## Numbers
- 26,619 discoverable API definitions
- 689 exact-name source-verified entries. Source verification is discovery evidence, not proof of execution.
- 22 built-in providers, 22 customer-executable provider rails
- 1,003 workspace-authenticated public/no-key HTTPS origins
- 1,025 total callable now
- Source verification is not execution.
---
## Pricing
| Plan | Price | Access |
|------|-------|--------|
| **Free APIs** | $0, no card | Free forever. Discovery and every zero-cost API, over 1,000 of the 1,025 callable. |
| **Paid APIs** | Provider cost + 15% | Add a card once, then metered per call. Actions without an exact billing adapter remain blocked. |
Pricing canon: underlying provider cost plus a 15% margin. Stripe metered billing live.
---
## Links
- **Site** — [apiclaw.cloud](https://apiclaw.cloud)
- **Docs** — [apiclaw.cloud/docs](https://apiclaw.cloud/docs)
- **Catalog** — [apiclaw.cloud/catalog](https://apiclaw.cloud/catalog)
- **Security** — [apiclaw.cloud/security](https://apiclaw.cloud/security)
- **SKILL.md** — [apiclaw.cloud/SKILL.md](https://apiclaw.cloud/SKILL.md)
- **npm** — [@nordsym/apiclaw](https://www.npmjs.com/package/@nordsym/apiclaw)
- **Remote MCP** — [apiclaw.cloud/mcp](https://apiclaw.cloud/mcp)
- **Claude Desktop Extension** — [apiclaw.cloud/apiclaw.mcpb](https://apiclaw.cloud/apiclaw.mcpb)
- **List your API** — [apiclaw.cloud/docs#list-your-api](https://apiclaw.cloud/docs#list-your-api)
Built by [NordSym](https://nordsym.com). MIT licensed.
TDQS
Scored across 14 tools
Most tools have distinct purposes, but check_balance and check_workspace_status overlap heavily on tier/status/usage information. list_mission_templates and discover_missions also cover similar ground, though descriptions help clarify list-all versus search-by-intent.
The majority of tools follow a clear snake_case verb_noun pattern like discover_apis, get_api_details, and start_mission. Minor deviations like mission_status and apiclaw_help break the pattern, but they remain readable and predictable overall.
Fourteen tools is reasonable for a platform covering API discovery, execution, provider status, and mission orchestration. The count is slightly high because of redundant workspace-status-style tools, but no tool is egregiously out of place.
The core workflows of API discovery, details, calling, balance checks, and mission lifecycle are well represented. Obvious gaps include no cancel-mission operation and no provider connection/disconnection tools, but most user intents can still be handled.