Track the current API contract

The documented contract includes user owned API keys, optional workspace ceilings, role aware database access, scheduled jobs, durable runs, integration catalogs, and supervised workspace summaries.

No public deprecation is listed on this page. When a future change requires migration, the entry will name the affected route, replacement, and removal date.

Treat unknown response fields as additive and ignore them unless your application uses them. Validate required fields at your boundary and keep endpoint paths in one client module so migrations stay contained.