finish_reason: "stop" and a short refusal. There is no error code and no refusal category, and the call is billed as normal output. A task that expects JSON gets a plain sentence instead, so the client reports a parsing error such as Unrecognized token.
APIYI has enabled automatic content safety failover for non-streaming requests: when one official route triggers a content filter, the request is retried on another official route. Streaming requests cannot be switched once output has started. The new FAQ shows the refusal response body and how to detect it, and recommends archiving failed cases internally for analysis before retrying that content with another model. See What Does an OpenAI Model Refusal Look Like?.
← Back to Live · 📚 Monthly archive