FoundryNet / OEMs / MiR (Mobile Industrial Robots)

AUTONOMOUS MOBILE ROBOT · CANONICAL DATA MODEL

MiR (Mobile Industrial Robots) canonical data model: connect your MiR (Mobile Industrial Robots) equipment to any AI agent

2,461 confirmed mappings·12 protocols·99% field coverage

Forge turns raw MiR (Mobile Industrial Robots) tags into one clean, governed schema your AI agent already understands. One MCP call, no per-AMR integration project.

Try it free: 3 machines, no credit card → See it work →

Paste your MiR (Mobile Industrial Robots) data and see it normalized in 30 seconds. No POC required.

Read-only. Forge reads your MiR (Mobile Industrial Robots) data through standard industrial protocols. Read-only. Your equipment is never at risk.

The problem

Why MiR (Mobile Industrial Robots) data is hard to integrate

MiR fleets expose state through a REST fleet API and ROS 2 topics (/robot_status/battery_percentage, /robot_pose/x) that read differently from every other AMR vendor.

Typical MiR (Mobile Industrial Robots) equipment communicates over ROS 2 (DDS), HTTP / REST, MQTT Sparkplug B. Each firmware revision, model line and integrator names the same physical quantity differently, so every AI or analytics project pays the integration tax again, the tax that cancels 40% of industrial AI deployments before they ship.

The solution

One universal schema for every MiR (Mobile Industrial Robots) AMR

Forge resolves MiR (Mobile Industrial Robots) telemetry into Forge's canonical field set, the same 1,027-field canonical schema (366 resolvable from vendor tags today), used across all 47 vendor packs. Point Forge at the AMR, pass oem: "mir", and spindle speed is spindle_speed_rpm whether it came from a MiR (Mobile Industrial Robots) controller or anything else on the floor.

ROS 2 (DDS)HTTP / RESTMQTT Sparkplug B

99%Field coverage

10Canonical autonomous mobile robot fields

3,444Corpus mappings

Field coverage

What Forge resolves for MiR (Mobile Industrial Robots)

Confirmed canonical fields your agent gets from MiR (Mobile Industrial Robots) AMRs, drawn from Forge's 3,444-mapping corpus:

amr.battery.chargeamr.battery.voltageamr.battery.chargingamr.position.xamr.position.yamr.position.thetaamr.velocity.linearamr.velocity.angularamr.operating_modeamr.safety.estop

Sample normalization

Raw tag in		Canonical field out	Meaning
/robot_status/battery_percentage: 82	→	amr.battery.charge: 82	battery %
/robot_pose/x: 12.4	→	amr.position.x: 12.4	map X (m)
/robot_status/mode_text: "Ready"	→	amr.operating_mode: "Ready"	operating mode
/cmd_vel/linear/x: 1.1	→	amr.velocity.linear: 1.1	linear velocity

30-second deployment

Add MiR (Mobile Industrial Robots) to your agent with one call

No SDK, no per-tag mapping, no historian project. Connect the MCP server and normalize live MiR (Mobile Industrial Robots) data:

claude mcp add --transport http forge https://mcp.foundrynet.io/mcp --header 'Authorization: Bearer YOUR_API_KEY'

# normalize raw MiR (Mobile Industrial Robots) telemetry into the universal schema

curl -s https://forge.foundrynet.io/v1/normalize \

-H 'Content-Type: application/json' \

-d '{"data": {"/robot_status/battery_percentage": 82, "/robot_pose/x": 12.4, "/robot_status/mode_text": "Ready"}, "oem": "mir"}'

{"amr.battery.charge": 82, "amr.position.x": 12.4, "amr.operating_mode": "Ready", "coverage": "100%", "confidence": 0.97}

Unknown tags never get force-mapped. Fields below the confidence floor abstain rather than guess, so your agent never acts on a bad reading.

Start free: Forge API, 3 machines → See the full demo →

Where MiR (Mobile Industrial Robots) fits

Protocols
ROS 2 (DDS) HTTP / REST MQTT Sparkplug B

Vertical
autonomous mobile robot

Other autonomous mobile robot vendors
OTTO Motors 6 River Systems AGILOX Fetch Robotics Geek+ (Geekplus) Locus Robotics

Same protocols, other industries
ABB Robotics KUKA Universal Robots Fanuc Robotics

Also searched as mir, mobile industrial robots, mobile_industrial_robots, mir100, mir250