About · the company
Intent verification infrastructure for autonomous agents.
Intended, Inc. builds the runtime layer that verifies what an agent is about to do matches what was intended — before execution, in the target system, fail-closed. We are a Delaware C Corporation operating from Austin, Texas, with our registered office in San Francisco, building toward a single claim: nothing autonomous moves without consent, and every consent is provable without us.
01 · The thesis
Policies define rules. They do not define intention.
Every control in the stack was designed around a human in the loop. RBAC assumes a person clicked; code review assumes a person read it; the change ticket assumes a person filled it out. An autonomous agent breaks all of those at once — it can open a thousand pull requests or issue a thousand refunds in the time it takes a human to read one alert. The industry’s answer has been to watch harder: more guardrails, more evals, more dashboards. But watching is after the fact. By the time an anomaly surfaces, the git push already happened.
Adjacent systems answer whether an action is permitted, whether the output looks safe, or what happened. None of them answer whether the action matched what was intended, here and now, before it ran. That is the gap autonomous systems cannot close on their own — and the only one we build for.
02 · The shape
An open layer, a runtime, and one invariant.
Open Intent — Apache 2.0
The open language for what an agent action intends. 173 canonical intents across 29 domains, versioned, schema-validated, public RFC process. Fork it, self-host it, contribute back. The category only exists if the language is public.
Open source →Authority runtime
LIM-backed interpretation, composite risk scoring, conformance against your declared process, Ed25519 mint, hash-linked audit chain. Metered by verified decisions. Available today.
Platform →Single-tenant deployments
Isolated control plane, your signing keys, SOC 2 Type II in progress, signed SLAs. On-prem and sovereign options for regulated and air-gapped workloads.
Enterprise →No Token · No Action
The whole product reduces to one invariant: a signed Authority Token is the only thing that authorizes execution, and the connector verifies it itself. Everything else is theater.
Why this matters →03 · What we are not
We do not replace your stack. We answer the question it skips.
We are not a policy engine, a guardrail, or an observability platform — those are necessary, and we sit alongside them. We are not a model provider, and we do not train on your traffic. We are the layer that interprets an agent’s proposed action, anchors it to a canonical intent, scores it against your process and risk thresholds, and decides before execution — then seals that decision into a cryptographically signed, replayable chain; per-tenant public-key (JWKS) verification is live. One question, answered at the only moment it matters.
04 · The company