Model registration makes a self-hosted or fine-tuned model a first-class model-service resource instead of a special application-side integration. Applications discover it, request it by name, and receive the same interface used for commercial models. section 3.1.4 section 3.1
A registration request supplies the information the platform needs to route, constrain, authenticate, and monitor the deployment:
- Name the model with a stable identifier used by discovery and workflow requests. section 3.1.4
- Specify the internal endpoint and credential reference so the service can reach the deployment without embedding credentials in application code. section 3.1.4
- Declare capabilities such as context-window size, vision support, and tool support so callers can select compatible models. section 3.1.4
- Provide a health-check path and receive a provisioning status with a registration timestamp. section 3.1.4
Using a registered model
A workflow requests the registered model by name rather than calling its internal endpoint directly. The Model Service routes the request, records usage and interaction data, monitors health, and can fall back to another model or support an A/B test through configuration. section 3.1.4
Listing 3.4 Custom model registration request and response
Request:
name: "healthfirst-medical-v1"
endpoint: "http://ml-inference.
➥internal:8000/v1" #A
capabilities: { #B
context_window: 8192,
supports_vision: false,
supports_tools: true
}
health_check: "/health" #C
credential_ref: "ml-inference-prod" #D
Response:
name: "healthfirst-medical-v1"
status: "provisioning"
registered_at: "2024-03-01T14:00:00Z"
Inspect the concrete registration request and response, including endpoint, capabilities, health check, credential reference, and provisioning status. section 3.1.4

