The shared language for what agents intend.

Open Intent is the open, vendor-neutral standard for naming what an autonomous action is trying to do. 173 canonical intents across 29 domains — 14 digital and 15 physical — versioned, schema-validated, Apache 2.0. The category only exists if the language is public, so the language is public.

You can't govern what you can't name.

Every agent framework invents its own vocabulary for actions, so policy, audit, and cross-vendor governance never line up. Open Intent is the interlingua: one canonical code for deploy to production — OI-100-class — whether the action came from a coding agent, an RPA bot, or a robot arm.

Classify once, govern everywhere, and prove it in an audit trail any human or auditor can read. The taxonomy is the contract between the agent that decides to act and the systems that must trust it.

Stable codes, two levels deep.

Open Intent is a hierarchy. A domain (OI-100, Software Development) groups related work; each domain holds categories (OI-101, OI-102 …). Codes are stable family identifiers — once assigned, a code never changes meaning, so a policy written against a code keeps working across taxonomy versions. Everything is schema-validated JSON; the current release is v2.0.

All 29 domains. All 173 categories. Searchable.

This is the entire standard — nothing held back. Search any domain, category, or Open Intent code, and filter to the 14 digital or 15 physical domains. Expand a domain to read every category and its definition.

From software actions to physical motion.

Same code structure, same license. An authority decision reads the same whether it gates a git push or a robot's grasp — which is what makes one governance layer work across both.

Use it as your interlingua.

Install the package, map your agent's actions to canonical codes, and govern against them in whatever runtime you already run. It is independent of Intended — fork it, self-host it, build your own enforcement against it. No account required.

Public, versioned, community-governed.

Apache 2.0. Proposals go through a public RFC on GitHub; new domains and categories ship by version with stable codes, so nothing you build against breaks underneath you. The category only exists if the language is public — so we keep it public.