Read model route status

A model route describes an exact model release at your API endpoint. In Provider workspace, read its review status, customer exposure and Next action together. An approved route may still be unavailable to customers. A status is not evidence that a model answered a request.

Review status

Label	What it means and what happens next
Staged or Validated	The metadata passed validation. Millwork must still test and review this exact revision.
Nonconformant	Correct the feed findings before submitting another draft.
Live checked or tested	Testing has progressed; follow the next action for the remaining review.
Awaiting decision	The tested revision is waiting for Millwork to decide whether to approve it.
Approved	Millwork approved the revision. Preparing it for serving and enabling customer access remain separate.
Not listed	The approved revision is not yet in the loaded serving configuration.
In manifest	The revision is in the loaded serving configuration. Read its customer exposure below.
Quarantined	The route is held. Follow the stated reason and next actor.
Deprecated or withdrawn	The route is no longer offered in its previous active state. Read current state before attempting a replacement.

Customer exposure

Label	What you can conclude
In manifest	Loaded configuration alone does not show current catalog exposure or execution admission.
Catalog visible	The route has catalog exposure; execution admission is a separate fact.
Canary only	Catalog exposure is limited to one granted customer organization, for the exact deployed model, within a time window, attempt limit and spending limit. It does not mean general customer availability.
Admission open	Execution admission is open in the observed state. Catalog visibility and customer eligibility still apply.
Exposure unobserved	Current exposure could not be established; shown as a warning when the observation is incomplete or inconsistent. Missing observations do not mean the route is open or closed.

Hold and expiry tags

A route can show these tags alongside its review status:

Label	What to do next
Suspended or out of serving	The route is held out of serving. Read the reason and next actor; a new feed does not lift a Millwork suspension.
Expired	The current claim has expired. Submit a new revision with current details and follow the stated next action.
not ready	Your feed marks the route as not ready. Correct the feed when the route is ready for review.
left out of feed	Your current feed omits the route. Restore its details if you intend to offer it again.

Follow a hold or a changed revision

Read who needs to act beside Next action. Restore a route omitted from your feed or marked not ready by correcting the feed. Submit a new revision when its claim or test evidence expires. Complete domain proof when domain control expires. A Millwork suspension needs Millwork review; a new feed does not lift it. Keep the observed feed revision token with each draft. After a conflict, read current state and compare your intended change before submitting again. The CLI and SDK make one attempt and do not refresh and resubmit a stale draft.

Get started

Provide models

Build

Build safely

SDK and MCP

Read model route status

Review status

Customer exposure

Hold and expiry tags

Follow a hold or a changed revision

​Review status

​Customer exposure

​Hold and expiry tags

​Follow a hold or a changed revision

Review status

Customer exposure

Hold and expiry tags

Follow a hold or a changed revision