One Typed Registry: agentis.*

No hidden capability

Every feature described in these docs — memory, orchestration, apps, reach, governance — is reachable through one typed registry, agentisToolRegistry.ts. There's no separate internal API a human uses that an agent can't; if the platform can do something, there's a tool for it, and that tool returns the same predictable envelope every time: { ok, result | error, costCents, durationMs }, plus a compass.next hint on settled calls pointing at the next sensible step.

One registry inside; a compact gateway outside

The full typed registry remains the internal source of truth, but MCP clients receive at most six progressive-disclosure operations instead of every schema at once. They orient, search, describe, and call only the capability they need, or use bounded code mode for composition. Policy is still checked by the registry on every inner call, so the smaller prompt surface changes discovery cost, not authority. See The MCP Plane for the exact gateway contract.

Continue