v1.4.0 · 5 §22–26 endpoints live Getting started · one line

The manifest agents read
before they touch your robot.

ROBOT.md is to a robot what CLAUDE.md and AGENTS.md are to a codebase. One file — YAML + markdown — so a planning LLM can safely operate a single robot. Speaks RCAN 3.0+. Built for Anthropic surfaces, flexible for any MCP-aware agent. 

$ pip install robot-md && robot-md init
1 robots registered
7 peer runtimes
5 §22–26 endpoints live
v1.4.0 on PyPI
§ 01 — The closed loop

ROBOT.md → MCP → Claude Code → robot moves.

The full loop — manifest declaration to physical action — in one conversation. No runtime to install. No axis conventions to learn.

~/bob · robot-md · MCP session
$pip install robot-md && robot-md init
✓ ROBOT.md + CLAUDE.md written — preset so-arm101
✓ registered — RRN-000000000003
✓ calibrated — zero pose recorded via IK
$claude
✓ robot-md-mcp connected · 6 resources · 3 tools loaded
You:pick the red lego and place it in the bowl
Claude:Scanning workspace… found red 2×4 lego at (0.31, −0.12, 0.04)
→ IK solved · executing pick …
30-second screencast placeholder
bob arm · pick and place
Step 1
ROBOT.md
YAML frontmatter + prose body declares what the robot is and what it can safely do
Step 2
robot-md-mcp
MCP server exposes 6 resources + 3 tools to any connected agent
Step 3
Claude Code
Reads manifest, reasons over capabilities and safety gates, plans the action
Step 4
Robot moves
Driver executes; E-stop and HiTL gates enforced per §8 AUTHORIZE before servo bus
§ 02 — Surface map

One file. Every surface.

Purpose-built for Anthropic, open to any MCP-aware agent. Install once per surface, then ask in plain English.

● Live
Claude Code
pip install robot-md
robot-md init
claude
Full install guide →
● Live
Gemini CLI
gemini mcp add robot-md \
  npx -- --yes robot-md-mcp \
  ./ROBOT.md
Full install guide →
● Live
OpenAI Codex
codex mcp add robot-md \
  -- npx --yes \
  robot-md-mcp ./ROBOT.md
Full install guide →
○ Pre-release
ChatGPT
npx -y robot-md-http
# OpenAPI bridge for
# Custom GPT Actions
Full install guide →
◌ Pre-release
Amazon Q
# MCP: pending aarch64
# robot-md-http bridge
# available today
Full install guide →
§ 03 — Compliance moat

Filed with regulators. Not just generated.

Five RCAN §22–26 attestation packets, all live endpoints. Run one command per packet — robot-md handles the filing.

§22
FRIA
Fundamental Rights Impact Assessment — automated pre-deployment checklist filed to RRF.
Live
§23
Safety benchmark
ISO 42001 self-assessment linked to the robot's RRN. Signed envelope, audit-trail hash.
Live
§24
IFU Art. 13(3)
Instructions for Use — machine-readable intent and capability declaration per Article 13(3).
Live
§25
Incident report
Structured incident reporting per Article 72, linked to RRN, timestamped and signed.
Live
§26
EU Register Art. 49
Per-model EU AI Act registration packet, routed to the official register endpoint via RRF.
Live

All five endpoints live as of 2026-04-24. Read the full compliance story → RRF registry details →

§ 04 — Founder-authored protocol

robot-md is the reference implementation
of the RCAN protocol.

RCAN (Robot Communication & Addressing Network) is the open wire protocol for signed, authority-aware robot messages. robot-md's team authored the spec. That means every breaking decision — from ML-DSA-65 crypto to the §22-26 EU compliance hooks — was made in-house, not adapted from a third-party interface. When the spec evolves, robot-md ships the reference implementation first.

rcan.dev — read the protocol spec →
§ 05 — Built on · plugs into

Open standards. Zero runtime lock-in.

AI surfaces
Anthropic

Claude, MCP (Model Context Protocol), Managed Agents. robot-md is purpose-built for the Anthropic surface stack — Claude Code, Desktop, and Mobile are the primary targets.

claude.ai →
Infrastructure
Cloudflare

The Robot Registry Foundation runs on Cloudflare Pages + Workers + D1. Edge-served globally, zero downtime at the identifier layer. No seat fees. Self-hosted mode for private fleets.

robotregistryfoundation.org →
Open standards
RCAN + MCP

RCAN 3.0+ (Apache-2.0, community-governed) for the wire protocol. MCP for agent-surface interop. JSON Schema draft 2020-12 for frontmatter validation. No vendor-specific formats in the core.

rcan.dev →
01 — Install

Start in one command.

Install the CLI, run robot-md init, and Claude Code handles registration, calibration, and your first pick — all through the using-robot-md skill.

Install →
02 — Read spec

Understand the format.

The ROBOT.md spec defines every required and optional field, the RCAN 3.0+ conformance rules, and the compliance packet filing requirements. Normative text, schema, and examples.

Read spec →
03 — Talk to us

Compliance-bot waitlist.

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.

Learn more →