Deprecations
Nothing is currently deprecated. Every endpoint, method, verdict and error message documented on this site is supported.
This page exists so that when something is retired, there is one place a customer already knows to look — and so the rule is stated before it is needed rather than after.
How a deprecation is announced
A thing being deprecated means it still works, and there is now a date after which it will not. Nothing is removed without appearing here first.
Each entry carries four things:
| Field | What it tells you |
|---|---|
| What | The exact method, endpoint, field or value. |
| Announced | When it was first listed on this page. |
| Removal | The release it stops working in. |
| Replacement | What to move to, and what changes when you do. |
A deprecation is announced here and in the Changelog at the same time. The removal itself appears in the changelog again, marked Breaking.
What is not a deprecation
Three things change without being deprecations, and none of them require action:
- New verdicts or error messages. The SDK is built so that a new value does
not break a caller who handled the old ones correctly — which is why
isSafe()returns true only forpass. Error messages are written for people; show or log them, but do not parse them. - Limits and prices. Size limits, rate limits and per-token prices can change. Prices are always shown on the dashboard's Usage page.
- Policy content. Your policy sets are yours. Nothing on our side rewrites or retires them.
Current entries
None.