AGENT SKILL

domino-model-serving

Automate Domino endpoints (Model APIs) and registered models over REST. Covers the /api/modelServing/v1 lifecycle (create an endpoint from a file or a registered model, add versions, poll deployment status, list, update replicas or hardware tier, archive, build and instance logs), registered models v1 vs v2 routes, MLflow tracking vs the registry API, management URL vs prediction URL, and sync Basic vs async Bearer prediction auth. Use when scripting deployments from CI, a Job or a notebook, registering a model version by API, or debugging stop, archive and delete behaviour. For UI publishing, the predict function, scaling and health settings use domino-model-endpoints; for drift and quality monitoring use domino-model-monitoring; for exporting a model out of Domino (image to your registry, NVIDIA Fleet Command, Snowflake UDF, SageMaker) or batch scoring Jobs use domino-model-delivery.

License 许可
MIT
最近更新
2026-11-14
Stars
★ 5
Forks
4

01 前言 Front Matter

name
domino-model-serving
description
Automate Domino endpoints (Model APIs) and registered models over REST. Covers the /api/modelServing/v1 lifecycle (create an endpoint from a file or a registered model, add versions, poll deployment status, list, update replicas or hardware tier, archive, build and instance logs), registered models v1 vs v2 routes, MLflow tracking vs the registry API, management URL vs prediction URL, and sync Basic vs async Bearer prediction auth. Use when scripting deployments from CI, a Job or a notebook, registering a model version by API, or debugging stop, archive and delete behaviour. For UI publishing, the predict function, scaling and health settings use domino-model-endpoints; for drift and quality monitoring use domino-model-monitoring; for exporting a model out of Domino (image to your registry, NVIDIA Fleet Command, Snowflake UDF, SageMaker) or batch scoring Jobs use domino-model-delivery.
compatibility
Domino 6.3 and Domino Cloud. Requires DOMINO_API_HOST; in a run use DOMINO_API_PROXY or the localhost:8899 access-token endpoint, outside a run a Personal Access Token or service-account token. The modelServing beta visibility and collaborator routes exist only on Domino Cloud.

02 资源文件 1

03 SKILL.md 正文

Domino model serving (REST)

Applies to Domino 6.3 and Domino Cloud.

Programmatic lifecycle for Domino endpoints (Model APIs in the API) and registered models. UI publishing, the prediction function, scaling and endpoint health are in domino-model-endpoints. Worked requests for every step: LIFECYCLE.md; route catalog: API-MODEL-SERVING.md.

Authentication and base URL

domino-api-intro. Legacy API keys are deprecated; do not use them.

Connectivity check: GET /api/modelServing/v1/modelApis?limit=1 returns 200.

Three surfaces (do not mix them)

Surface Base path Purpose
Model Serving /api/modelServing/v1/modelApis Endpoints: create, versions, list, update, archive, logs
Registered models /api/registeredmodels/v2 (list, register); /api/registeredmodels/v1/{modelName} (get, patch, versions) Registry records; modelName is the name, not an id
MLflow tracking MLFLOW_TRACKING_URI in a run; /api/2.0/mlflow/... on the deployment URL with a bearer token Experiments, runs, artifacts, the MLflow registry client

MLflow logging or registration deploys nothing; deployment is a Model Serving call.

Management URL vs prediction URL

Management calls go to the base above under /api/.... Predictions go to the deployment URL: /models/{modelApiId}/latest/model (sync, Basic auth) or /api/modelApis/async/v1/{modelApiId} (async, Bearer). The ModelApi object has no url field; build the prediction URL from its id and the deployment URL shown on the endpoint's Overview tab.

Lifecycle

  1. Train and, optionally, register (POST /api/registeredmodels/v2, or the MLflow client).
  2. POST /api/modelServing/v1/modelApis with name, description, environmentId, isAsync, strictNodeAntiAffinity, environmentVariables, version{projectId, source, logHttpRequestResponse, monitoringEnabled}; source.type is File (file, function) or Registry (registeredModelName, registeredModelVersion). Optional hardwareTierId, replicas.
  3. Poll the version: GET .../modelApis/{modelApiId}/versions/{modelApiVersionId} until deployment.status is Running and isPending is false (absent deployment means pending), then confirm activeVersion.id on the Model API. Running is not health: fetch .../instanceLogs?maxResults=3000 (no tail), keep model- container lines, expect WSGI app 0 (mountpoint='') ready (no app loaded. GAME OVER is a crash loop), then one test prediction. Sync or commit before step 2 and pin version.commitId; the head lags uploads by seconds.
  4. New code: POST .../modelApis/{modelApiId}/versions (same version fields plus shouldDeploy: true). Poll that version, not the Model API; the old one stays active until the new one runs.
  5. Change replicas, hardware tier, name or environment: PUT .../modelApis/{modelApiId} (name, description, replicas, environmentId required; send current values back, including resourceQuotaId). Scale changes need a restart: UI, or internal stopModelDeployment then startModelDeployment (LIFECYCLE.md).
  6. Retire: stop the running version first (UI Versions > Actions, or POST /v4/models/{modelApiId}/{versionId}/stopModelDeployment with {}; non-public route; may change in a future Domino version), then DELETE .../modelApis/{modelApiId}: 500 while a version runs; after success GET is 404 and the endpoint leaves all lists.
  7. Verify each mutation with a GET; 2xx means accepted, not applied.

Logs: GET .../versions/{modelApiVersionId}/buildLogs, exportLogs, instanceLogs.

/api/modelServing/v1/modelDeployments (with start, stop, credentials, logs, versions) is a separate entity: a registered model deployed onto an admin-defined external deployment target, SageMaker only. It is not a Model API; see domino-model-delivery.

Registered models

  • List: GET /api/registeredmodels/v2?projectId=&searchPattern=&maxResults= (token-paginated with pageToken). Register: POST /api/registeredmodels/v2 (modelName, modelSource{sourceType, mlflowSource|huggingFaceSource}, create). POST /api/registeredmodels/v1/{modelName}/versions is deprecated.
  • Get and patch: GET|PATCH /api/registeredmodels/v1/{modelName} (PATCH takes description and discoverable; GET returns neither discoverable nor aliases); versions at /api/registeredmodels/v1/{modelName}/versions/{version}; endpoints serving a version at .../versions/{version}/modelapis.
  • Aliases and tags are MLflow features: the MLflow client on MLFLOW_TRACKING_URI, or /api/2.0/mlflow/registered-models/... on the deployment URL; see domino-experiment-tracking.

Prediction auth

Restricted sync endpoints require HTTP Basic with the endpoint access token as username and password. Async endpoints require Authorization: Bearer <token>. Unrestricted endpoints need neither. Tokens: the user's, or create one (domino-model-endpoints DEPLOY-ENDPOINT.md); never print it. Source: https://docs.domino.ai/cloud/platform-capabilities/features/model-deployment/domino-endpoint-authorization.

Which path applies

curl -s "$DOMINO_API_HOST/version"   # "version": "6.3.x" self-managed; "6.4.x" or later on Domino Cloud

Domino Cloud adds /api/modelServing/beta/modelApis/{modelApiId}/visibility (Public, Discoverable, Private), .../access and .../collaborators (roles Owner, Editor, Operator, Viewer); not on 6.3, where you set them in the UI (Settings > Access and Sharing).

Related

04 同仓库更多 Skills

dominodatalab
dominodatalab/domino-ai-plugin

tags-and-properties

Manage Domino tags and properties via the Tags (Taxonomy) API at /api/taxonomy/v1. Covers namespaces and tags (create, list, update, deprecate, delete; tag entities such as projects, models, datasets, apps, project templates, NetApp volumes, environments; query by tag; autocomplete; merge; CSV import/export) and properties (typed metadata fields - text, number, date, boolean, url, user, organization, select, multi_select - with per-entity values, groups and versioned entities like model_version/app_version). Use when organizing entities with tags, building hierarchical namespaces, defining typed metadata fields, setting property values, finding entities by tag, bulk-tagging during onboarding, or migrating a taxonomy across environments.

★ 5
dominodatalab
dominodatalab/domino-ai-plugin

netapp-volumes

Work with Domino Volumes for NetApp ONTAP (NetApp Volumes) - shared, multi-terabyte storage with near-instant snapshots. Covers creating volumes, attaching them to projects, mount paths (/mnt/netapp-volumes/ or /domino/netapp-volumes/), snapshots and tags, roles, deletion, mounting volumes in jobs, and the NetApp Volumes REST API (/remotefs/v1). Use when managing large-scale shared data, taking fast no-copy snapshots, or integrating NetApp ONTAP storage with Domino.

★ 5
dominodatalab
dominodatalab/domino-ai-plugin

domino-workspaces

Work with Domino Workspaces - interactive sessions running Jupyter, JupyterLab, VS Code or RStudio on a hardware tier with a compute environment. Covers launching and configuring a Workspace, what persists across stop and resume, file paths and syncing for DFS and Git-based Projects, package and home-directory persistence, SSH access from a local IDE, the Workspace API routes, and troubleshooting. Use when setting up or debugging an interactive development session in Domino.

★ 5
dominodatalab
dominodatalab/domino-ai-plugin

domino-ui-bootstrap

Bootstrap or retrofit a Vite + React 18 + TypeScript project so it uses the Domino design system (`@dominodatalab/extensions-tools`). Scoped to a **fully standalone SPA frontend for a Domino application or extension**, not snippets, library additions, or work inside an existing Domino monorepo package. Use whenever the user wants to create, scaffold, refactor, retrofit, or set up such an SPA (a React app, web app, frontend, UI, or extension) that should "look like Domino", use Domino components, follow the Domino design system, or integrate with the Domino platform, including when they mention DominoThemeProviderDecorator, extensions-tools, or base-components without saying "Domino". Also use to make an existing standalone React/Vite project "Domino-styled" or add Domino theming. Handles React 18 / react-router 5 pinning, Storybook MCP registration, theme provider wiring, and build verification.

★ 5
dominodatalab
dominodatalab/domino-ai-plugin

domino-trace-setup

Set up GenAI tracing for an LLM or agent application in Domino by checking the Domino SDK and MLflow requirements (the DSE needs nothing installed), then adding a tracing_setup.py helper, span evaluators, a config.yaml, and @add_tracing / DominoAgentContext wiring. Use when the user asks to add tracing, observability, or evaluation to an agent or LLM app running on Domino.

★ 5
dominodatalab
dominodatalab/domino-ai-plugin

domino-rust-apps

Build a Rust web app (axum) in Domino and ship it as a Domino App that starts from a prebuilt binary. Covers installing a pinned Rust toolchain into a Compute Environment with rustup, Cargo project defaults (edition 2024, rust-toolchain.toml, Cargo.lock, Clippy pedantic, rustfmt, cargo-nextest, cargo-deny), rust-analyzer for the IDE and coding agents, check hooks, calling Domino as the viewer with extended identity propagation, dev and release build profiles, keeping target/ out of Git and Domino storage, and an app.sh that runs the binary in App Preview and deployments without compiling. Use when the user wants a Rust app, API, dashboard or Proa site on Domino, a performance-sensitive or correctness-critical App, or asks to set up Rust, cargo, Clippy, nextest or rust-analyzer in a Domino Workspace or environment.

★ 5