API reference
API changelog
The dated record of every change to the Tase API: additions, behaviour changes, deprecations and sunset dates.
This page is the record of what changed in the API and when. Every deprecation and every sunset date is announced here first, so it is the one page worth reading before a major release of your own.
Entries are newest first and tagged Added, Changed, Deprecated, Removed or Fixed. Additive entries describe changes we may ship without notice under the versioning policy; a Deprecated entry always names the replacement and, once fixed, the sunset date.
Nothing has been deprecated yet
The API is new, so this log is short. That is the honest state of it, not an omission. When the first deprecation happens it will appear here with its sunset date.
2026-07-25
Added: initial availability of the /v1 API.
POST /v1/chat/completions: chat completions, with streaming and tool calling.GET /v1/models: the models available to your key.GET /v1/usage: programmatic usage and spend for the calling account.- Bearer authentication with
tase_sk_keys, issued and revoked in the console.
How to keep track
- Read this page before you upgrade a client library or ship a release that depends on the API.
- Log any response that carries a Deprecation header, so a change reaches you through your own alerting rather than through a page you have to remember to visit.
- Keep the account owner email current in the console. Deprecation notices go to the owners of the keys that actually call the affected surface.
Related pages
- Versioning: which of these entries can land without notice, and which cannot.
- Deprecation policy: how a Deprecated entry turns into a sunset.
- Errors: error types and codes referenced by entries here.
- Rate limits: where limit changes are reflected once announced.
- Legal: where the contractual terms governing API use are published.