Versioning
What can change within version 1 of the Direct API, what your client must tolerate, and how models are added and retired.
The version is in the path: /v1. Within v1, changes are additive: new tools, new optional input fields, new response fields, new statuses, new event types and new error codes.
What your client must handle
- Ignore response fields you do not know.
- Treat a generation status you do not know as not final, and keep following it.
- Expect input schemas to stay strict: an unknown input field is refused, so a typo never silently does nothing.
Breaking changes
A breaking change ships as /v2, with at least 6 months of overlap and notice to every organization with an active key.
Models
- Models are added and retired over time; Models always shows the current set.
- A model id is never reused and never stops being accepted. A retired id runs its replacement, and responses name the model that actually ran.
- Morphic may change which engine stands behind a model id only to improve it at the same or a lower price, and announces it in the model catalog.
If you have any trouble or have any questions, feel free to reach out. We're happy to help. Write to us at support@morphic.com.