coordination.fleetmapModule 11Read every agent grant, lease, waiter and quarantine in the workspace in one call, drawn from what the plane has admitted.
coordination.fleetmap is the plane's read-only view of itself. One GET returns the agents that hold grants, the leases in force, the waiters on each resource, who sends heartbeats, who is quarantined and the gateway's mode. It is derived from the policy snapshot, so there is no inventory to keep.
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
agentsleasesid, resource, holder, expiresAtMs, scope, and ./docs/coordination-fleetmapAPI referenceRoutes, bodies and status codes./docs/coordination-fleetmapOpen 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
nonceconditionsgrantswaiterspresencequarantinedmcpModeobserve, advise or enforce.githubgithub.audit events in the ledger.ledgerAgents and leases come from the workspace's policy snapshot, the same replica Intralock evaluates against. An agent appears once it holds a grant.
Waiter counts per resource come from the contention state that coordination.lease keeps. Heartbeat DIDs come from the presence index that civics.presence writes.
mcpMode is read from the policy store and defaults to observe. github counts github.audit events and ledger counts every event in the ledger.
The call writes nothing and is not metered. Each console that shows more, such as trust tier or stops, joins this answer with its own routes.
Runs in a shared demo workspace with a demo key: anyone can see what it holds, so send nothing private. coordination.fleetmap docs
Press Run to send the request on the left to the shared demo workspace.
Runs in a shared demo workspace with a demo key: anyone can see what it holds, so send nothing private.
A request in the shape the API accepts, and an example response in the shape the module returns.
GET /api/v1/acp/coordination/fleetmap Authorization: Bearer av_workspace_•••• → 200 { agents, leases, grants, waiters, presence, quarantined, mcpMode, github, ledger }
{
"agents": [
"did:web:acme.example:agent:billing",
"did:web:acme.example:agent:release"
],
"leases": [
{
"id": "lease_4c1e",
"resource": "lock:deploy/production",
"holder": "did:web:acme.example:agent:release",
"expiresAtMs": 1793545800000,
"scope": {
"urn_prefix": "lock:deploy/production",
"verbs": [
"*"
]
},
"nonce": "did:web:acme.example:agent:release:lock:deploy/production:1793545770000",
"conditions": {}
}
],
"grants": 12,
"waiters": {
"lock:deploy/production":
},
: [
],
: [],
: ,
: ,
:
}An on-call engineer reads leases to see which agent holds lock:deploy/production, and when its expiresAtMs says the lease lapses.
Compare agents with presence. An agent that holds grants but sends no heartbeat is one to look at before it next acts.
waiters shows the resource with the longest line, which is usually where two agents want the same thing.
quarantined lists the DIDs the plane is refusing right now, so an incident lead can check that a stop is in force.
trust.get for the score and tier.mcp.shadow.identity.enroll has its own list route.A module is a strong claim about a narrow thing. Rely on it for exactly what it is.
Each workspace reads only its own replica. A warm Worker that serves several workspaces never mixes their leases or grants.
The dashboard Fleet Map joins this answer with the identity list, compiled mandates, stops and each agent's trust tier. Those come from their own routes, not from this one.
mcpMode is observe until a workspace sets it. At observe the MCP gateway records calls and lets them through; only enforce can refuse.
coordination/admit counts as a coordinated action.grants is a count. The grants themselves are read with POST /api/v1/acp/coordination/grants.Authenticate with a workspace API key as a Bearer token. The base URL is https://api.intramedial.com.
/api/v1/acp/coordination/fleetmapRead the workspace's agents, leases and presence.coordination.fleetmap.getRead the same map as an MCP action.coordination.lease02Resource leases and queuesHold 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.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.identity.enroll12Agent identity registryGive each agent its own identity before it acts, so every admitted action traces back to one agent and never to a shared account.mcp.shadow13Shadow agent discoveryList the tool calls the MCP gateway has seen, with the agent behind each, so callers nobody enrolled show up beside the ones that are.worldmodel.graph16World model graphSee every agent, repo, lease and named resource your workspace knows, and how they connect, without drawing the map first.cartographer.map17