Treat Model-Provider Enforcement as an Ops Event

Create a provider-side profile for each end customer and send it with every request your agents make on that customer’s behalf, including background and scheduled runs. Anthropic’s user profiles exist so that enforcement can land on one end customer rather than the whole organization; that only works if no request goes out untagged. Requests made for your own internal work get their own profile, separate from customers.

Register for the provider’s restriction and ban events (Anthropic’s organization webhooks have one event for a restriction or ban of a user profile and one for when it ends). On a restriction, pause that customer’s agents and queued jobs, keep everyone else running, preserve the logs for that profile, and open a review. On the end event, resume only after the review is closed. Write the runbook before you need it, because the first event will arrive while customers are mid-task.

Providers are being asked about this directly. The European Commission says the AI Office has "sent Requests for Information addressing issues such as security, external evaluation and monitoring how models are used" (EVP Virkkunen, 14 Oct 2026). Those requests go to model providers, and providers push the same expectations down to the platforms between them and end users. Keep a per-customer usage log and your own abuse checks so you can answer a provider’s question with evidence, and catch a problem customer before the provider does.

The UK Financial Conduct Authority says incident reporting "must extend to significant AI failures and near-misses" and that agentic systems "require continuous, conditional assurance" because a system can behave differently as the models beneath it change (speech, Jessica Rusu, 19 Oct 2026; a speech, not a rule change). Record provider warnings, restrictions that were lifted, monitor flags that did not lead to action, and behavior changes after a model update. History of this kind cannot be backfilled when a buyer or regulator first asks for it.

For every product or service you sell, record which models and model families run underneath it, including open-weight models and any reached through a third party. The DHS order covers products from DeepSeek and its affiliates and also "third-party products and services developed using DeepSeek implementations", so it reaches downstream builders, and an open-weight licence does not take a model outside it. If you sell to US federal civilian agencies, check that list before every model swap.