# 2ot for agents

2ot is tooling invoked by the harness the engineer chooses. It is not a public autonomous agent and the website is not a remote PLC control plane.

Canonical public origin: `https://2ot.ai` (apex, no `www`).

## When to use 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.

## Discover the local execution surface

- `2ot --list --json` lists installed routed commands.
- `2ot --mcp-dump-schema` emits the normalized machine-readable tool surface.
- `2ot mcp` exposes compatible operations to an MCP-capable harness.
- `2ot check --fast` provides low-latency compiler diagnostics when vendor software is not required.

## 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 --json` is the authoritative list of installed routed commands.
- `2ot --mcp-dump-schema` is 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.

## Public website discovery

The public website exposes read-only documentation and capability discovery. Project-changing and device-facing operations remain on the local 2ot CLI/MCP surface inside the engineer-selected permissions boundary.

Machine-readable entry points:

- [/llms.txt](/llms.txt)
- [/llms-full.txt](/llms-full.txt)
- [ARD catalog](/.well-known/ai-catalog.json)
- [/sitemap.xml](/sitemap.xml)

## Siemens knowledge boundary

Siemens-derived API metadata, documentation, graph snapshots and version data remain on the licensed developer workstation. The public website explains the local mechanism but does not publish the vendor-derived corpus.