FoundryNet / OEMs / AGILOX

AUTONOMOUS MOBILE ROBOT · CANONICAL DATA MODEL

AGILOX canonical data model: connect your AGILOX equipment to any AI agent

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

Forge turns raw AGILOX 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 AGILOX data and see it normalized in 30 seconds. No POC required.

Read-only. Forge reads your AGILOX data through standard industrial protocols. Read-only. Your equipment is never at risk.


The problem

Why AGILOX 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 AGILOX equipment communicates over ROS 2 (DDS), HTTP / REST, OPC UA. 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 AGILOX AMR

Forge resolves AGILOX 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: "agilox", and spindle speed is spindle_speed_rpm whether it came from a AGILOX controller or anything else on the floor.

ROS 2 (DDS)HTTP / RESTOPC UA
91%Field coverage
10Canonical autonomous mobile robot fields
3,444Corpus mappings

Field coverage

What Forge resolves for AGILOX

Confirmed canonical fields your agent gets from AGILOX 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 inCanonical field outMeaning
battery_pct: 76→amr.battery.charge: 76battery %
pose_x: 5.2→amr.position.x: 5.2pose X
lin_vel: 0.9→amr.velocity.linear: 0.9linear velocity
mode: "MOVING"→amr.operating_mode: "MOVING"operating mode

30-second deployment

Add AGILOX to your agent with one call

No SDK, no per-tag mapping, no historian project. Connect the MCP server and normalize live AGILOX data:

claude mcp add --transport http forge https://mcp.foundrynet.io/mcp --header 'Authorization: Bearer YOUR_API_KEY'
# normalize raw AGILOX telemetry into the universal schema
curl -s https://forge.foundrynet.io/v1/normalize \
  -H 'Content-Type: application/json' \
  -d '{"data": {"battery_pct": 76, "pose_x": 5.2, "lin_vel": 0.9}, "oem": "agilox"}'
{"amr.battery.charge": 76, "amr.position.x": 5.2, "amr.velocity.linear": 0.9, "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 →

Related

Where AGILOX fits

Protocols
ROS 2 (DDS) HTTP / REST OPC UA

Vertical
autonomous mobile robot

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

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

Also searched as agilox


AGILOX 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,027-field canonical schema, 366 resolvable from vendor tags today, 2,461 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.