Five tested integrations into MCP-aware agent surfaces — free. One managed offering — Compliance-bot — that files EU AI Act packets in one day.
ROBOT.md works with any MCP-aware agent. Five surfaces are tested and shipped.
| Claude Code | claude mcp add robot-md |
Primary → |
| Gemini CLI | gemini --mcp robot-md |
Docs → |
| Codex | codex tools add robot-md |
Docs → |
| ChatGPT Custom GPT | Web Browsing + Knowledge file | via web |
| Amazon Q | q mcp add robot-md |
Docs → |
Give Compliance-bot your robot repo. Get back a signed FRIA, IFU, safety-benchmark, and EU-register filing — all five RCAN §22–26 packets — without reading a single EU AI Act article yourself.
The RCAN §22–26 compliance stack is already live. Compliance-bot is the hosted agent that automates it.
ROBOT.md
with an issued RRN. Nothing else required.
The compliance tooling is open-source. The hosted agent is the convenience layer — no infrastructure to run, no SDK to integrate.
The reference enforcement gateway: receives signed action requests, verifies, and dispatches to drivers. Self-host on your robot or your own cloud.
robot-md-mcp surface — 4 resources + 2 tools (frontmatter, capabilities, safety, body · validate, render)/enable-dispatch from Claude CodeThe hosted Managed Agent. Give it a repo, get back a full compliance bundle — no infrastructure, no CLI, no reading of RCAN section numbers.
ROBOT.md file uploadCompliance-bot is the first robot-md product built on Anthropic's just-announced Managed Agents platform — composable cloud-hosted agents with a public API.
Anthropic's Managed Agents platform provides the infrastructure for cloud-hosted, composable agent workflows. Compliance-bot is the robot-md flagship built on this surface: it receives a robot repo, orchestrates a multi-step compliance filing workflow, and returns signed attestation packets — all without the operator running any local infrastructure.
The open-source
robot-md-gateway
is the reference enforcement gateway — self-hosted for developers
who want full control. Compliance-bot is the managed convenience
layer for operators who want the outcome without the infrastructure.
Compliance-bot is in private preview. Leave your email and we'll contact you when it's ready — or when we need a test case. No spam. No sales cadence. One email when the beta opens.
Your email is only used to contact you about Compliance-bot. No third-party sharing. Unsubscribe in one reply.
Install robot-md,
author a ROBOT.md,
register with RRF, run a skill, and walk away with a signed
audit bundle. About ten minutes, end to end.
The ROBOT.md spec defines every required and optional field, the RCAN protocol conformance rules, and the compliance packet filing requirements. Normative text, schema, and examples.
Read the spec →Give your robot repo to Compliance-bot and get back a signed FRIA + IFU + safety-benchmark + EU-register filing in one day. Powered by Anthropic Managed Agents.
Join the waitlist →Where safety is actually enforced.
Physical safety is enforced at Layer 3 (robot-md-gateway) or Layer 4 (a runtime that embeds it, e.g., OpenCastor). Declaration alone (Layer 1) does not enforce safety. Agent host alone (Layer 2) is not the safety boundary. If a deployment lacks Layer 3, no safety claim attaches to it.