coordination.leaseModule 02Hold a resource for one agent at a time, with a lease that lapses on its own and a queue for the agents that have to wait.
coordination.lease grants one agent an exclusive lease on a resource. A second agent that asks is refused with the holder's name and told how long to back off. Every resource has its own lease authority, so a lease cannot be granted twice, and a lease that is never released expires.
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 abuseThe REST route and the lease authority take resource and actorDid only. The MCP schema accepts ttlMs, but it is dropped before the lease is made, so every lease runs 30,000 ms. Release early or acquire again to extend.
Plane module
resourceactorDidleaseid, resource, holder, , , and ./docs/coordination-leaseAPI referenceRoutes, bodies and status codes./docs/coordination-leaseOpen the consoleSee the module at work in the dashboard, on a seeded fleet or your own./dashboard-preview/fleet-mapStart freeCreate a workspace and admit your first intent./auth/signup
expiresAtMsscopenonceconditionsreasonlease_held, or deadlock when the request would close a wait cycle.holderstampedelease_held: admitted, the waiters let through, and waitMs, how long to back off.waitingOndeadlock: the resource the holder is itself waiting on.leaseIdrelease: the lease to release. A stale id is refused.Post resource and actorDid. An authenticated agent can only ask as itself. The request goes to the lease authority for that one resource.
A free resource returns { ok: true, lease }. A held one returns lease_held with the holder and a back-off. A request that would close a wait cycle returns deadlock.
release frees the lease and adds 0.5 to the holder's trust score. A lease left to expire is taken back by an alarm and costs 5 points.
A refusal carries stampede.waitMs, which grows with the number of waiters. GET /api/v1/acp/coordination/wait returns the queue.
world stands in for your workspace; nothing leaves this page. coordination.lease 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/lease Authorization: Bearer av_workspace_•••• Content-Type: application/json { "resource": "lock:deploy/production", "actorDid": "did:web:acme.example:agent:release" } → 200 { ok, lease } or { ok: false, reason, holder }
{
"ok": false,
"reason": "lease_held",
"holder": "did:web:acme.example:agent:release",
"stampede": {
"admitted": false,
"waitMs": 50
}
}Two release agents ask for lock:deploy/production. One gets the lease, and the other is told who holds it and when to retry.
An agent takes a lease and dies. The lease lapses, the alarm takes it back and the next agent in line can ask again.
Agent A holds one resource and waits for B's, while B waits for A's. The second request is refused as deadlock with waitingOn named.
Fifty agents want the same file. Each refusal returns a waitMs that grows with the queue, so retries spread out instead of hammering.
coordination.admit says whether the action is allowed.civics.presence to report status and civics.claims to state what you intend.negotiate.propose for longer agreements.A module is a strong claim about a narrow thing. Rely on it for exactly what it is.
deadlock instead of queueing forever.ttlMs a caller sends.The resource's semantics class decides what conflicts. Two reads of a resource that is safe to read concurrently do not exclude each other, and a write or delete excludes everything.
A release raises the holder's trust score by 0.5 and an expiry without a release lowers it by 5. Those two signals are the ones the lease authority emits.
A grant writes a coordination.lease event to the ledger. The write is best effort, so a ledger outage does not stop the lease.
ttlMs.release takes resource and actorDid, plus an optional leaseId. The MCP schema has no leaseId.coordination/admit counts as a coordinated action.Authenticate with a workspace API key as a Bearer token. The base URL is https://api.intramedial.com.
/api/v1/acp/coordination/leaseAsk for an exclusive lease on a resource./api/v1/acp/coordination/releaseRelease a lease the caller holds./api/v1/acp/coordination/waitRead the queue of waiting agents and deadlock pairs.coordination.lease.acquireAsk for a lease as an MCP action.coordination.lease.releaseRelease a lease as an MCP action.coordination.waitRead the wait queue as an MCP action.coordination.admit01Intralock admissionDecide every action before it happens: an agent declares its intent, and Intralock admits it or names the reason it may not.civics.presence14Agent presenceLet agents see which peers are online and what each holds, so a quiet agent is not mistaken for a hostile one.trust.get15Trust scores and autonomyRead an agent's trust score and the autonomy tier it has earned, so autonomy follows conduct the plane has actually seen.civics.claims20Resource claims officeLet an agent state what it is about to work on before it takes a lease, and open a case when two claims collide.metering.snapshot21Metered usage by workspaceSee what the plane has counted for your workspace, meter by meter, and which billing meter each count feeds.coordination.approve05Human approval queueHold a risky write or delete until a signed-in person approves it, with the agent, resource and verb in front of them.dual-control.scopes22