Overmind Inference

Start with list_projects and choose the intended accessible project. For an account connection, pass its project_id on every project tool and resource URI query; follow returned links. Project API keys retain their narrower access.

Determine whether a model is ready, warm, selected and actually used. These are separate states. Use the chosen MCP project and returned deployment identities; do not invent model IDs or infer a live alias from training success.

Inspect serving

Read overmind://deployments/{deployment} and the relevant capability resource. For metrics, the deployment resource accepts period=1h|24h|7d|30d|all and source=application|all. State the selected filters; all-time/all-traffic is the default. Use application traffic when determining whether the user's application is connected.

Separate deployment readiness, current worker warmth, capability routing and successful application traffic. Worker measurements can be unavailable: null counts are unknown, not zero. Reading metrics does not wake a model. Historical traffic does not prove the worker is currently warm.

Describe failures and latency percentiles with their period and traffic source. Do not let platform evaluations or smoke calls stand in for application usage.

Test or activate

Successful training automatically starts deployment using the model's inference contract. deploy_finetune backfills a completed historical job and reuses its existing deployment; it never changes application routing. Failed or deleted deployments still require retry_deployment.

Use run_inference only for a requested test on a ready deployment, with the user's supplied messages and output budget, or input-only decisions for a decision deployment. Decisions contain state, question, kind and ordered options; they never contain targets or chat generation settings. Their results contain ordered probabilities and the verified artifact identity. Native models use POST /api/deployed-models/{id}/inference/ and poll GET /api/inference-requests/{id}/; they do not support chat completions or chat capability activation. Preserve explicit max_tokens for chat; omission uses the production default. Report finish reason and truncation. An oversized context request needs a deliberate input/budget change, not silent clipping. A test may incur inference spend.

Supply a stable request_key. Contract 4.0 returns an inference_request job, not a synchronous answer. Read it with get_job; a disconnected client can reuse the same key/input to recover the same receipt without resubmission. A different input under that key conflicts. Unknown provider acknowledgement is not a reason to create another request. Result resources support offset/limit content paging when the compact result is clipped.

Follow linked operational receipts with inspect_operation(operation, after, limit). The event timeline distinguishes source/observation time, heartbeat and forward progress, and labels shared-pool observations separately from request-specific adapter/generation work. Missing measurements, dropped provider publications and uncollected event backlog remain explicit. Inspection does not wake workers; it cannot establish application integration or semantic quality.

For an authorized rollout, prefer ship-model when capability, deployment and fine-tuning job are known. Otherwise inspect readiness, then use set_active_model for the approved capability/deployment. Poll the returned model_activation job. The previous alias remains selected until verification succeeds; a requested switch is not a completed switch.

Use retry_deployment only for a failed or deleted deployment. Clearing routing is a separate requested action; omitting deployment from set_active_model clears it and cancels a pending switch. Do not change the benchmark to activate serving.

For a repository rollout, get_model_swap_prompt supplies a local handoff. Apply code changes only within the requested scope and verify final capability and deployment state. Successful application API-key calls establish connection independently of a completed activation.

Report readiness, worker state, selected alias and application evidence separately. Open inference under the project's Console base, preserving projectId, when the user wants the visual serving view.