Technical Platform
Built to integrate with what you already run
Stateful Robotics sits between your WMS and your AMR fleet. REST API inbound, WebSocket state feed outbound, persistent task graph in the middle tracking every run.
Architecture
Five layers, one task graph
Inbound ops requests arrive at the API layer and are compiled into a directed task graph. The graph executes against the live fleet state. When conditions change, the replanning layer patches the running graph without halting execution.
Each layer communicates state changes forward only. The fleet coordinator issues assignments once the graph is resolved. Robots operate on discrete task instructions, not a continuously-replanned map.
- Persistent run history per task graph
- Dependency-aware partial re-execution
- WMS integration via standard REST endpoints
- Robot type constraint resolution at compile time
API Layer
One endpoint to submit an ops request
POST your operations request to /v1/ops-requests. The response carries a graph ID and the initial task set. Subscribe to the WebSocket feed on that graph ID to receive live state updates as tasks execute.
The API accepts plain JSON. No SDK required for integration. Robot vendor adapters are included for common AMR fleets; custom adapters can be added during onboarding.
{
"graph_id": "grph_b4e9c1a2",
"status": "compiled",
"task_count": 6,
"assigned_robots": [
"R-04",
"R-07"
],
"ws_feed": "wss://feed.statefulroboticshq.com/grph_b4e9c1a2",
"conflicts_detected": 0,
"estimated_completion_s": 184
}What it connects to
Warehouse management systems
Stateful Robotics accepts ops requests from any WMS that can issue a POST. Built-in formatting guides cover Manhattan Associates WM, Blue Yonder, and Oracle WMS. Custom field mapping is handled at the API adapter layer during onboarding.
AMR robot vendors
Fleet adapters are included for Locus Robotics, Geek+ and 6 River Systems. If your fleet uses a different vendor, the adapter interface is documented and can be implemented in a standard onboarding engagement.
Deployment
Stateful Robotics runs on-premise inside your network or in a single-tenant cloud environment. All task state and run history remains within your deployment boundary. No fleet data is shared outside your instance.
Integration Support
Integration is part of the pilot
We walk through the WMS connection and robot adapter configuration with every pilot team. No self-serve setup required.