coordination.haltModule 06Stop one agent, one mandate or one resource at once, with a reason on record, and lift the stop when it is safe.
coordination.halt sets a stop on the admission hot path at one of three scopes – agent, mandate or resource. The next admission answers with a refusal. Only a signed-in administrator can set or lift a stop; the whole-workspace stop is the separate switch.
Put admission in front of your MCP servers, repositories, SaaS tools and cloud accounts. Every agent gets a lease or a reason – and you keep the lever to stop any of them.
© 2026 Intramedial. All rights reserved. Intramedial is a product by Trustvice. Secured and supercharged by Avonao Labs.
Report abuse
Plane module
killThe coordination.stops.halt schema lists why, but the route reads reason and refuses a stop without one. unhalt takes the stop id, not scope and target. Agents and tokens are refused either way.
scopeagent, mandate or resource. Anything else is a 400 that points to the kill switch.targetreason/docs/coordination-haltAPI referenceRoutes, bodies and status codes./docs/coordination-haltOpen the consoleSee the module at work in the dashboard, on a seeded fleet or your own./dashboard-preview/emergencyStart freeCreate a workspace and admit your first intent./auth/signup
haltid (prefixed hlt_), scope, target, reason, by and at.createdfalse when the same scope and target were already stopped; the existing stop is returned.ledgeredcoordination.halt event reached the ledger. The stop stands either way.idunhalt. The stop to lift. A bare quarantined agent appears in switches as q:<did>.scope: agent, target a DID. The agent joins the quarantine set, so every admission for it answers quarantine.
scope: mandate, target a mandate name. Admission answers mandate_halted for any action whose grant comes from that mandate.
scope: resource, target a resource. It covers what is under it, so repo:acme also stops repo:acme/x. Admission answers resource_halted.
halt takes scope, target and reason. All three are required, and a resource stop cannot target * or /.
The stop is held in memory and written to the policy store. The next admission sees it, before any grant or lease is read.
switches lists the workspace kill switch, every halt in force with who set it and why, and whether you may change them.
world stands in for your workspace; nothing leaves this page. coordination.halt docs
Press Run (or ⌘/Ctrl + Enter) to decide the request on the left.
It runs in this browser: the plane’s own kernel, with no key, no account and no network call. Change an agent, a lease or a rule on the left and run it again to see the verdict move.
A request in the shape the API accepts, and an example response in the shape the module returns.
POST /api/v1/acp/coordination/halt Authorization: Bearer av_workspace_•••• Content-Type: application/json { "scope": "agent", "target": "did:web:acme.example:agent:billing", "reason": "runaway writes" } → 200 { ok, halt, created, ledgered }
{
"ok": true,
"halt": {
"id": "hlt_5d2c81",
"scope": "agent",
"target": "did:web:acme.example:agent:billing",
"reason": "runaway writes",
"by": "did:web:acme.example:person:ines",
"at": "2026-11-01T09:20:00.000Z"
},
"created": true,
"ledgered": true
}Stop the agent with a reason. Its next write is refused at admission with quarantine, with no change to its grants.
Halt the mandate by name. Its grants stop admitting at once, while grants from other mandates keep working.
Stop repo:payments. Anything under it is refused with resource_halted until the stop is lifted.
Use kill. It trips the workspace's coordination switch, and admission answers kill_switch for every agent until resume.
coordination.quarantine, which needs dual control or an adjudicated case.coordination.approve; a stop is a blanket refusal.watchdog.check flags anomalies; a halt is what you do once you know.A module is a strong claim about a narrow thing. Rely on it for exactly what it is.
coordination.halt event to the ledger.coordination.unhalt with the administrator, the scope and the target.KILL_SWITCH_KV bound; without it kill and resume answer 503.halt, unhalt, kill and resume are for a signed-in person who administers the workspace. An agent or API token is refused with 403.
Quarantine and resource stops are checked first, then confirmation, grants and finally a mandate stop. A kill switch refuses before any of them.
kill takes an optional reason and ledgers coordination.kill. resume clears it; a switch the operator set is the operator's to lift and returns 409.
switches also shows quarantined agents that have no halt row, such as one quarantined by a ruling, as q:<did> with an empty reason.
agent, mandate and resource. Stopping the whole workspace is the kill switch.reason or no target returns 400, as does a resource stop on * or /.halt and unhalt; reading switches needs no role.Authenticate with a workspace API key as a Bearer token. The base URL is https://api.intramedial.com.
/api/v1/acp/coordination/haltStop an agent, a mandate or a resource./api/v1/acp/coordination/unhaltLift a stop by its id./api/v1/acp/coordination/switchesRead the kill switch and every halt in force./api/v1/acp/coordination/killThrow the workspace's coordination kill switch./api/v1/acp/coordination/resumeTurn the workspace's coordination back on.coordination.stops.haltSet a stop from an action call; refused unless the caller is an administrator.coordination.stops.unhaltLift a stop from an action call.coordination.stops.switchesRead the stop switches from an agent.coordination.killThrow the kill switch from an action call.coordination.quarantine32Agent quarantineCut one agent off at admission, but only with the second person's approval or a ruling that names that exact agent.coordination.admit01Intralock admissionDecide every action before it happens: an agent declares its intent, and Intralock admits it or names the reason it may not.watchdog.check36Issuance watchdogCatch a plane that is issuing leases or credentials too fast, or has gone quiet, by reading the ledger instead of asking the plane.mcp.enforce04MCP gateway enforcementPut a front on an MCP server so each tool call is admitted like any other intent, and a refused call never reaches the server.github.enforce29GitHub write gateMake a commit's check go red unless the agent behind it holds the grant and, for a write, a human has confirmed.saas.admit30SaaS connector admissionAsk whether an agent may touch a SaaS source, and let it write through one only after the same check that gates everything else.unhalt takes the stop's id and an optional why. The lift is ledgered as coordination.unhalt; an unknown id returns 404.
iam.assume31