A runaway agent

Short answer. Meridian shows the jump. It does not turn off the provider key. Stop the credential at the provider or the gateway that holds it, then read the agent on Dashboard and the alert on Meridian Insights.

See the jump

Open Dashboard and find the agent. Open Analytics & Insights. The Meridian Insights tab is findings and monitoring. The hero is Meridian Insights. Spending Alerts is "Stay within budget limits." Anomaly Detection is "Catch unusual patterns early."

A department budget alert, "Alert at 80% of budget" unless the department uses another percent, is a budget warning. It is not the same as one agent running away. Read which department fired, then the agent that spent into it.

Stop the spend

The spend happens where the key is accepted. Revoke or rotate that key in the provider console, or in the gateway that holds it. A Usage ingest key in Meridian only lets a gateway send usage in. Revoking it stops the feed. It does not stop the provider from billing a key that still works.

After the key is stopped, the next sync shows the spend that already happened. It does not erase it.

After it stops

If the month is still open, the new total is an Estimate. When the vendor invoice arrives, confirm the billing period and book it. That invoice is the total for the vendor and the period, and measured usage is scaled to it. See A surprise invoice.

If the agent has no owner, name one before close. See An agent with no owner.