metering.snapshotModule 21See what the plane has counted for your workspace, meter by meter, and which billing meter each count feeds.
metering.snapshot returns the workspace's counters: coordinated actions, active agents, arenas, lookups, doors and the rest. The plane increments each one as the work happens, and no request can report usage. The snapshot also names the billing meter each count maps to.
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
metersbillingMeterIds{ name, billingMeterId }: the billing meter each count maps to.identity.active_agents/docs/metering-snapshotAPI referenceRoutes, bodies and status codes./docs/metering-snapshotOpen the consoleSee the module at work in the dashboard, on a seeded fleet or your own./dashboard-preview/commonsStart freeCreate a workspace and admit your first intent./auth/signup
coordination.admissionscoordination/admit, whatever its outcome.parley.arenasparley.local.anchor, parley.arena_hours and parley.participant_agents beside it.gatehouse.lookupsgatehouse.doors and gatehouse.matters beside it.arbitration.casesyards.instancesnegotiate.sessions beside it.Admissions, enrollments, arena opens, directory lookups and similar events call the metering bridge from inside the plane, as they happen.
Each count is stored in the workspace's own policy store. One workspace never adds to another's totals.
GET /api/v1/acp/metering/snapshot returns every meter's current count, and the billing meter id each one feeds.
A request to metering/emit is refused. A meter counts what the plane did, and nothing a caller sends changes it.
Runs in a shared demo workspace with a demo key: anyone can see what it holds, so send nothing private. metering.snapshot 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/metering/snapshot Authorization: Bearer av_workspace_•••• → 200 { meters, billingMeterIds }
{
"meters": {
"identity.active_agents": 12,
"coordination.admissions": 4180,
"parley.arenas": 3,
"gatehouse.lookups": 57,
"arbitration.cases": 1
},
"billingMeterIds": [
{
"name": "identity.active_agents",
"billingMeterId": "identity_active_agents"
},
{
"name": "coordination.admissions",
"billingMeterId": "coordination_admissions"
}
]
}A finance lead reads coordination.admissions and identity.active_agents against the plan, and sees the count before the invoice does.
An engineer sees gatehouse.lookups far ahead of every other meter and traces it to a loop in one agent.
billingMeterIds lists the billing meter each count feeds, so a usage line can be traced back to the counter behind it.
Read the snapshot, turn on a new agent fleet, read it again. The difference is what the rollout cost in counted work.
coordination.lease for the queue and coordination.fleetmap for the leases.mandates.compile.ledger.blame for the record of what happened.A module is a strong claim about a narrow thing. Rely on it for exactly what it is.
metering/emit is refused for any request.identity.active_agents, coordination.admissions, parley.arenas, parley.local.anchor, parley.arena_hours, parley.participant_agents, gatehouse.lookups, gatehouse.doors, gatehouse.matters, arbitration.cases, yards.instances and negotiate.sessions.
A billing meter id is the meter name with each . swapped for _, so coordination.admissions feeds coordination_admissions.
The dashboard's Commons page also shows waiters and budget buckets. Those come from coordination/wait and treasury/envelopes, not from this snapshot.
coordination/admit, identity/enroll and identity/scim, parley/open, directory/lookup and arbitration/open, among others. Reads and most other routes do not.metering/emit is refused for requests, so usage cannot be added by hand.Authenticate with a workspace API key as a Bearer token. The base URL is https://api.intramedial.com.
/api/v1/acp/metering/snapshotRead every meter's count and its billing meter id.coordination.metering.snapshotRead the metering snapshot 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.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.coordination.fleetmap11Fleet MapRead every agent grant, lease, waiter and quarantine in the workspace in one call, drawn from what the plane has admitted.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.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.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