MIM
Metering
How MEAL meters MIM operations.
Every call on MIM is metered through MEAL across three dimensions and may be settled across organizations through MADE.
Per-operation profile
| Operation | Tokens | Seconds | Watts |
|---|---|---|---|
message_send | 0 | yes | <0.001 kWh |
message_receive | 0 | yes | <0.001 kWh |
queuing | 0 | yes | <0.001 kWh |
dedup_check | 0 | yes | <0.001 kWh |
Rate card
MIM is a protocol kind — metered primarily on seconds with negligible token/watt cost on the protocol path.
| Dimension | Base rate | Multiplier on MIM |
|---|---|---|
| Tokens | $3.00 / M tokens | 0× (no LLM path) |
| Seconds | $0.018 / second | 1.0× |
| Watts | $0.42 / kWh | 0× (no GPU) |
Runway enforcement
MANA::budget is consulted at Stage 5. If the tenant's runway is below threshold for any required dimension, PolicyDenied { reason: "runway exhausted" } is returned — the call never reaches MIM.
Settlement
Cross-organization calls settle via MADE on the rail declared in the active MOAT treaty. MEAL::reconcile cross-checks metered events against settled payments nightly.