Use 2ot from the harness the engineer already trusts
2ot is an industrial automation execution and tooling layer. Automation scripts, CI systems and LLM agents can invoke it from an engineer-selected harness; the engineer remains in control of the workflow, permissions and review boundary.
When an agent should reach for 2ot
Use 2ot when a harness needs structured industrial-automation operations rather than prose-only guidance: workspace-aware routing, IEC 61131-3 compilation and transpilation, fast diagnostics, supported vendor operations, testing or language-server intelligence.
Inspect installed routed commands with 2ot --list --json.
Obtain the normalized tool contract with 2ot --mcp-dump-schema.
Run 2ot mcp when the engineer-selected harness speaks MCP.
Use 2ot check --fast for low-latency compiler diagnostics and LLM-oriented enrichment.
The website is discovery, not the control plane
This public site exposes read-only discovery surfaces for documentation and capability lookup. Project-changing or device-facing operations stay on the local 2ot CLI/MCP surface inside the harness and permission boundary chosen by the engineer.
Canonical public origin: https://2ot.ai (apex, no www).
Machine-readable entry points
Pure Markdown representation of this machine-oriented entry point.
Compact machine-readable product and documentation index.
Expanded machine-readable product context.
Agentic Resource Discovery catalog for public 2ot resources.
Manifest-driven public route inventory, including blog posts.
Markdown explanation of the local operational MCP surface.
Source of truth for the installed surface
The website explains the 2ot model and capabilities, but it is not the authoritative inventory of commands on a particular installation. Treat the local command surface as the source of truth:
2ot --list --jsonis the authoritative list of installed routed commands.2ot --mcp-dump-schemais the authoritative normalized MCP tool contract.- Website documentation describes the model; the local surface describes what is actually installed and callable.
What 2ot is not
2ot is not a public autonomous agent and not a cloud or remote PLC control plane. The public site only exposes discovery and documentation surfaces. Operational commands run locally inside the engineer-selected environment.
Distribution and version guidance
This site does not currently advertise a public installable distribution artifact. Agents must not infer a download URL or version from the website. When a public installer or package exists, its canonical distribution URI and version metadata should be advertised from the machine-discovery surfaces (ARD, MCP registry and docs).
Operational trust and authorization
Operational MCP and CLI run locally inside the engineer-selected environment and inherit that environment's authentication, authorization, permissions and approval or review policy. Discovery metadata on this site does not grant permission to mutate projects, source or devices.
Markdown on every core page
Core public pages expose a clean .md representation. HTML responses also advertise their Markdown alternate and llms.txt through discovery link headers, so a capable client does not have to guess that the machine-readable versions exist.
ARD for initial discovery
The ARD catalog advertises public documentation and the local MCP model without pretending that 2ot is a remotely callable autonomous agent. Operational MCP remains local to the engineer-selected environment.
Workspace-aware vendor routing
A correctly configured workspace usually lets 2ot choose the vendor runtime for common operations. Explicit Siemens TIA Portal, Beckhoff TwinCAT and CODESYS routes remain available when the harness needs vendor-specific behavior.
Licensed knowledge stays local
Siemens-derived API metadata, documentation, graph snapshots and version data remain on the licensed developer workstation. Agents may use the local mechanism inside that environment; the public website does not publish the vendor-derived corpus.
WebMCP after navigation
In WebMCP-capable browsers, this site registers read-only tools for documentation search, capability discovery, vendor-integration lookup, agent setup guidance and site navigation. ARD, search, sitemaps and Markdown discovery help an agent find 2ot first; WebMCP becomes useful once the agent is on the site.