- In short
- Structured refusal handling means reacting to the API's refusal signal - the stop_reason and its optional stop_details object - rather than parsing the model's text. The detail object can carry a policy category and readable explanation, but both can be null and some models or responses omit the object entirely, so handlers must tolerate its absence and fall back to generic handling. After a refusal, the triggering turn should be removed or rephrased, or the history cleared, before sending the next request, because re-sending on the same refused context typically produces further refusals.
Full concept guide coming soon
We are building the in-depth, exam-aligned guide for this knowledge point. In the meantime, explore the prerequisites and related concepts below, watch the official Anthropic Academy lessons, and start an adaptive study session to master it with Archie.
Watch and learn
Official Anthropic Academy lessons first, then hand-picked walkthroughs. Videos load only when you press play.
No videos curated for this concept yet
We are still curating the best official and community videos for this topic.
References & primary sources
Adaptive study
Master this concept with Archie
Practice it inside an adaptive study session. Archie, your Socratic AI tutor, tracks your mastery with Bayesian Knowledge Tracing and schedules the perfect next review.