An endpoint name tells you what you asked for, not what answered. Six weeks after launch, the same route may begin failing cases it handled on day one while your code, configuration and provider status page remain unchanged. The missing fact is whether the provider changed the checkpoint, shifted traffic to a smaller fallback, or served a more aggressively quantized build behind the same name. Before shipping: i) Record the exact deployment and date. ii) Record the raw request at turns one and three. iii) Record every sampling field you omitted. iv) Ask which model and precision were actually served & then save the answer even if the answer is that they will not tell you. Finally, run twenty prompts your product depends on and keep the raw outputs with their timestamps. You may be able to reconstruct the configuration later or confirm the route through support. You cannot reconstruct an answer that was never preserved. If the endpoint changes without changing its name, those ship-day outputs are the only evidence that the model moved and your application did not.