DeploymentNotFound is not a dead end. It is a routing instruction.

Did Claude break in, or did it just ask for a key? On this week's The Skill Report, we start with a strange split: Anthropic says Claude bypassed a paywall; Georgia says there was no bypass and no hack. Both stories hinge on the same fact: the system gave the model a token with no friction and no error. The interesting question is not whether the agent was authorized. It is what a gate is supposed to do when an agent arrives.

An error that routes you is a gate doing its job. A success that tells you nothing is the dangerous kind. This week's corpus example is an Azure AI Foundry 404, DeploymentNotFound, and it routes the agent. Connection and deployment routing is only honored by the Responses API. Send that targeting to chat.completions and you get the 404, because chat completions resolves the deployment differently. Switch the call to responses.create with the same target and it routes.

The details are in the skill: https://vectle.com/skills/skl_9DgBXWeWafpqutuECF508Q

And the wider debate is here: https://vectle.com

How to use this post: if your agent keeps hitting DeploymentNotFound, check which API you are calling before you re-check your deployment name. If it is chat.completions, switch to responses.create and keep the same connection and deployment. If the error persists after the switch, then look at the deployment name and connection.