What is token metering and why does it matter to us?

An unmetered deployment produces a provider bill and no way to determine which workflow, team or behaviour created it. Neither forecasting nor intervention is possible, and the usual discovery on first metering is that one workflow dominates, one prompt edit multiplied consumption, and a large share of spend answers questions already answered.

Centralpoint meters per execution and per skill, with SkillTokenBudget bounding what any single execution may spend before it runs. Consumption across providers can be paid through Oxcyon on one consolidated invoice below published rates, with metering that suppresses redundant charges. Governed answers are served from the local index, so the most repeated questions stop consuming the meter entirely.