API changelog: where Sume lists changes, and how to read it

Sume's changelog is a page in its docs: short notes for product releases, newest first, each with a version, a date, a one-line headline and bullets. The page calls itself the reader-facing source of truth for what shipped. It does not label entries as breaking, so read the bullets, and check the retiring routes separately.

This comes from the Changelog, the API overview and the Models overview, read 2026-09-29.

What does a changelog entry look like?

Each entry is a heading with the release version and date, a headline line, and a bullet list. On the read date the newest entry on the page is v0.2.59, dated August 1, 2026. Its headline is "Next 16, Agent Completions, Scheduled, team wallet".

Does the changelog cover every API change?

It covers product releases only. The page says its source is the GitHub release tags v0.2.*, with the separate skill-lab-v* tags excluded. It mixes UI notes with API notes, so scan for endpoint paths, field names and new scopes.

The changelog is not a per-endpoint history. For the exact current shape of a route, use the OpenAPI schema, which the docs point to as the live source for schemas; see the OpenAPI post.

How do I find out what is being retired?

Look at the Models overview, which lists deprecated and retiring compatibility aliases that are still supported. Today it says Video 1.0 (POST /v1/video-1.0/generate) is deprecated and maps to sume/auto, and that Music 1.0 is retiring and resolves through Music Router. It also lists two Avatar image-to-video routes as deprecated aliases of the VEED Fabric route.

Those aliases keep working for now. For the Video 1.0 and Image 1.0 move, see the migration post. The pages checked give no sunset dates for them, so treat the retiring label as your cue to move.

Is there an API version I can pin?

Paths carry a /v1 prefix; the overview gives the base URL https://api.sume.com/v1. The docs pages checked describe no version header, dated API versions or written deprecation-notice policy. If a contract needs a notice period, ask Sume for it in writing rather than inferring one from the changelog.

What is a practical way to stay current?

Skim the changelog on your own release cadence, and keep the retiring list on your code review checklist. Watch for new scopes: scopes are fixed when a key is created and cannot be added later, so a feature that needs a new scope needs a new key.