Scale or redeploy a model
Changes a model’s deployment incrementally. instances merges into the current plan: a
listed region takes the new count, an omitted region is untouched, and count: 0 scales
a region down.
release is optional. Omit it to change capacity only and keep the deployed release.
Supply it to roll every region to that release, not only the regions in the plan. The
body must set release, instances, or both.
strategy and immediate behave as on PUT. Without a release, REPLACE_ALL is
treated as ROLLING, and immediate is refused.
Callable by an account_admin or developer of the owning account when model serving is
enabled for the account. The CLI equivalent is reactor model deploy.
Authorizations
A Reactor API key (rk_...), sent as Authorization: Bearer rk_.... Keep it on a server.
Path Parameters
The model's ID (not its project ID). Find it with GET /models?name=your-org/your-model.
Body
The release to deploy. Required on PUT; optional on PATCH.
"v1.2.3-gabcdef0"
The instance plan per region. On PUT it replaces the plan; on PATCH it merges. Omit to leave capacity unchanged.
How the old release stops serving. Matched exactly.
ROLLING, REPLACE_ALL Close the model's live sessions once the deploy is sent. Requires a release and REPLACE_ALL.
Response
The change was accepted. A capacity-only change omits the weights fields.
The release now deployed.
Whether this deploy closes live sessions.
The release whose weights were reused because this release has none.
true when the release deployed with no weights available. Omitted when false.
The production revision this deploy created. Omitted when nothing changed.