Retired endpoints.

These endpoints are retired. A request to any of them returns 410 Gone with a JSON error body and a link header pointing at the migration guide. A 410 is permanent: don’t retry it — move the call to the endpoint in the right-hand column.

Retired	Returns	Use instead
Agent runs — `/v1/agent-runs` and everything under it, plus `/v1/states` and `/v1/agent-states`	`410`	Run your agent loop in your own client against Chat Completions, Responses or Messages. For long work that should survive a dropped connection, use Responses with `background: true`.
Artifacts — `/v1/artifacts` and everything under it	`410`	Keep large results in your own storage and send the slice you need in the prompt.
Batches — `/v1/messages/batches` and `/v1/batches`	`410`	Send the requests individually (with an Idempotency-Key so retries are safe), or use Responses `background: true` for long-running items.
The Responses WebSocket transport	`410`	`POST /v1/responses` over HTTPS, with `stream: true` for Server-Sent Events.
Legacy text completions — `/v1/completions`	`410`	Chat Completions: put your prompt in a single `user` message.
Tool connectors and catalog — `/v1/tool-connectors`, `/v1/tool-catalog`	`410`	Declare only the tools the model itself executes. See Tool calling.

Example 410 body

{
  "error": {
    "type": "gone",
    "code": "endpoint_retired",
    "message": "/v1/completions is retired in Sideren v2. See https://docs.sideren.io/guides/core-v2-migration",
    "docs_url": "https://docs.sideren.io/guides/core-v2-migration"
  }
}

Everything else on the API overview keeps working, including Embeddings, count_tokens and GET /v1/models. Your keys, model ids and base URL don’t change.

Get started

Plans & pricing

Agents

API reference

Guides

Reference

Retired endpoints.