Build without the UI

Everything the chat flow does — create hosted agents, message them, read activity, manage lifecycle — is a plain REST API, an MCP server, and a drop-in Claude skill.

1 · Get an API key

Checking sign-in…

Keys act as your account (they can create agents, which spends credits). Shown once — store it as CLAWMETRY_API_KEY. Revoke any time.

2a · MCP — one command

claude mcp add --transport http clawmetry https://build.clawmetry.com/mcp \
  --header "Authorization: Bearer $CLAWMETRY_API_KEY"

Tools: list_runtimes, create_agent, send_message, get_activity, configure_agent, pause_agent / resume_agent / destroy_agent. Works with any MCP client that speaks Streamable HTTP.

2b · Claude skill — one file

mkdir -p ~/.claude/skills/clawmetry-agent-builder
curl -s https://build.clawmetry.com/skill.md \
  -o ~/.claude/skills/clawmetry-agent-builder/SKILL.md

Claude Code then knows the whole API — say “deploy a claude_code agent that watches my repo” and it does the rest. The same file is the API reference: skill.md.

2c · Raw REST

# what can be hosted (no auth)
curl -s https://build.clawmetry.com/api/runtimes

# create an agent (debits the monthly plan price; 402 if credits are short)
curl -s -X POST https://build.clawmetry.com/api/provision \
  -H "Authorization: Bearer $CLAWMETRY_API_KEY" -H "Content-Type: application/json" \
  -d '{"runtime":"claude_code","brief":"Triage my GitHub issues. Be concise."}'

# talk to it (synchronous — allow up to 910s)
curl -s -X POST https://build.clawmetry.com/api/instances/<id>/messages \
  -H "Authorization: Bearer $CLAWMETRY_API_KEY" -H "Content-Type: application/json" \
  --max-time 910 -d '{"text":"What can you do?"}'

Full endpoint list with status-code semantics lives in skill.md. Need something the API doesn't do? Ask in the app — the team custom-builds extensions.