FoundryNet / OEMs / Fetch Robotics

AUTONOMOUS MOBILE ROBOT · CANONICAL DATA MODEL

Fetch Robotics canonical data model: connect your Fetch Robotics equipment to any AI agent

Vendor pack coverage·1,031-field schema·12 protocols

Forge turns raw Fetch Robotics tags into one governed schema your AI agent can read, and says plainly which tags it could not map.

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

Paste your Fetch Robotics data and see what Forge returns.

Read-only. Forge reads your Fetch Robotics data through standard industrial protocols. It does not write to the AMR unless you deploy and enable the bridge.


The problem

Why Fetch Robotics data is hard to integrate

Fleet state (battery, pose, velocity, e-stop) is published over ROS 2 topics or a proprietary REST fleet API, and no two vendors agree on the topic names.

Typical Fetch Robotics equipment communicates over ROS 2 (DDS), HTTP / REST. Each firmware revision, model line and integrator names the same physical quantity differently, so every AI or analytics project pays the integration cost again.


Coverage on prod

What Forge supports for Fetch Robotics today

Vendor packs that name Fetch Robotics: Warehouse AMR (Locus, Fetch/Zebra, 6 River, OTTO, Vecna) (125 mapped tags). That pack is shared: it covers Locus, Fetch/Zebra, 6 River, OTTO and Vecna tags, not this vendor alone. Passing oem: "fetch_robotics" routes the request to the AMR vertical, which turns on that vertical's cross-vertical gate. Every mapping says how it was made in match_type; a tag no layer can place comes back abstained instead of forced onto a field.

ROS 2 (DDS)HTTP / REST
Vendor pack coverageProd support tier
125Mapped tags in named packs
AMRRoutes to vertical

Canonical autonomous mobile robot fields in Forge's registry (all present on prod). Which Fetch Robotics tags reach them depends on the tag; Forge does not force a mapping.

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

Source: prod /v1/coverage and /health, read 2026-10-27 (build 238a6b3). Forge does not publish a per-OEM coverage percentage, so this page does not show one.


Try it

Send Fetch Robotics data to Forge

Connect the MCP server, or call the REST API directly:

claude mcp add --transport http forge https://mcp.foundrynet.io/mcp --header 'Authorization: Bearer YOUR_API_KEY'
# normalize raw Fetch Robotics telemetry into the canonical schema
curl -s https://forge.foundrynet.io/v1/normalize \
  -H 'Authorization: Bearer YOUR_API_KEY' \
  -H 'Content-Type: application/json' \
  -d '{"data": {"battery_pct": 76, "pose_x": 5.2, "lin_vel": 0.9}, "oem": "fetch_robotics"}'

The response lists each tag's canonical field, match_type and confidence. Tags Forge cannot place come back abstained, and physically impossible values come back as null with a reason.

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

Related

Where Fetch Robotics fits

Protocols
ROS 2 (DDS) HTTP / REST

Vertical
autonomous mobile robot

Other autonomous mobile robot vendors
MiR (Mobile Industrial Robots) OTTO Motors 6 River Systems AGILOX Geek+ (Geekplus) Locus Robotics

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

Also searched as fetch, fetch robotics, fetch_robotics, freight


Fetch Robotics in the canonical schema

For platforms Want this normalization inside your platform? License the engine and ship cross-vendor support as your own feature. 1,031-field canonical schema, 2,478 mappings, your brand. Platform licensing →
Why does a cross-vendor canonical data model matter? The Machine Agent breaks it down weekly. Read it →
Get the thesis behind this infrastructure: The Machine Agent, weekly.