Versioning & changelog
/v1 only changes additively. Here's what that promises, and what changed.
The policy
The API is versioned in the path: /api/v1.
/v1only changes additively. New endpoints, new optional request fields, new response fields, new error codes, and new enum values for things that are clearly open-ended can appear at any time.- Breaking changes mean
/v2. Removing or renaming a field, changing a type or its meaning, or making an optional request field required would all go into a new version, and/v1would keep working alongside it.
What that means for your client
- Ignore fields you don't recognize. Don't fail on unknown properties in responses.
- Handle unknown error codes by their HTTP status (see Errors).
- Don't depend on field order or on the exact wording of
message. - Treat cursors and IDs as opaque strings.
Changelog
Newest first.
2026-09
- Public API launch. Personal access tokens with fine-grained scopes, per-token rate limits
(with
X-RateLimit-*headers), CORS for the API playground, and the public spec at/openapi.jsonand/openapi.yaml. - These docs: guides, a generated reference with a playground, and Markdown /
llms.txtversions of every page.