The Robot Registry Foundation issues RRNs — permanent numeric robot identities —
and hosts the five RCAN §22-26 compliance endpoints.
robot-md register handles the signed-POST flow.
An RRN identifies a robot instance. An RMN identifies a robot model. Both are permanent once issued.
rrn:000000000003.
Resolves at robotregistryfoundation.org/r/RRN-000000000003.
One command mints an RRN and writes it back into your ROBOT.md.
Requires a valid ROBOT.md with rcan_version: "3.0".
$ robot-md register ROBOT.md \ --manufacturer "Acme Robotics" \ --contact-email [email protected]
The command signs the registration payload with your robot's key (generated at init time)
and POSTs to https://robotregistryfoundation.org/api/register.
On success, metadata.rrn
and metadata.rrn_uri
are written back to your ROBOT.md.
All five RCAN compliance endpoints are live at robotregistryfoundation.org as of 2026-04-24.
| RCAN § | Endpoint | Packet name | Status |
|---|---|---|---|
| §22 | /api/compliance/fria | FRIA — Fundamental Rights Impact Assessment | ● Live |
| §23 | /api/compliance/safety-benchmark | Safety benchmark (ISO 42001 self-assessment) | ● Live |
| §24 | /api/compliance/ifu | IFU Art. 13(3) — Instructions for Use | ● Live |
| §25 | /api/compliance/incident-report | Incident report Art. 72 | ● Live |
| §26 | /api/compliance/eu-register | EU Register Art. 49 filing | ● Live |
| §27 | /api/compliance/fria-signed | FRIA with post-quantum signature (in flight) | ◌ In flight |
Live endpoint status: robotregistryfoundation.org →
Every compliance packet is signed before posting. Keys are stored locally.
Keys are generated at robot-md register time and bound to the RRN.
The ed25519 algorithm is accepted at RCAN 3.0 L1 only;
L2+ requires pqc-hybrid-v1.
Any system that trusts a robot's key via the M2M_TRUSTED
tier MUST poll for revocation. robot-md handles this automatically.
When a key is revoked (via robot-md revoke-key
or directly at RRF), the RRF broadcasts a revocation event to all registered
M2M_TRUSTED
listeners. Peer runtimes (OpenCastor, robot-md-dispatcher) poll
https://robotregistryfoundation.org/api/revocation/<rrn>
on a configurable interval (default: 60 seconds). Any request signed with a revoked key is
rejected with 403 KEY_REVOKED.