Current version
Use the v1 route prefix for every released REST operation. The visible Latest tag identifies the current documentation set.Read version fields
Route, OpenAPI, and payload versions answer different compatibility questions. Keep all three with stored research responses.Major-version boundary
The current documentation has no earlier public major-version snapshot, so the navigation shows the current version without an empty selector.- The September 9 consolidation keeps /v1, retires overlapping routes and tools, and adds belief_id and source search filters to the remaining resources. Update saved requests and refresh tool discovery using the changelog.
- Future major payload contracts use a new route prefix. The version selector lists only documentation backed by a separate, published snapshot.
- A historical option never aliases current documentation or implies support that does not exist.
Endpoint lifecycle
A deprecated operation publishes its announcement, optional removal date, replacement, and migration steps on the endpoint page.Preview and Deprecated labels describe one operation’s lifecycle. They do not create a new major API version.