model_transfer
ManagementcatalogCopy Model to Another Project
Not in the default tool list
This tool lives in the tool catalog. Discover it with scenario_tools_search (or enumerate everything with scenario_tools_list) and run it via scenario_tool_execute_write. To list every tool directly, connect with ?toolsets=full.
Copy a trained model into another project. The copy gets a new model id in the destination project; the source model stays unchanged, and tags and collections are not carried over. Every member of the destination team receives an email about the new model, and the destination team's model limit applies. To duplicate a model as a draft inside the same project, use model_copy.
Args:
- model_id: required
- target_project_id: a required destination project ID, different from project_id
- team_id, project_id: required for OAuth callers
Returns: the new model record in the destination project.
Example: "Copy this model into my other project" -> model_id="model_xxx", target_project_id="project_yyy"
open-world
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
| model_id | string | ✓ | Model ID. |
| target_project_id | string | ✓ | Destination project ID. |
| team_id | string | — | Team ID. Required with project_id for OAuth callers; an API key is scoped by the key. |
| project_id | string | — | Project ID. Required with team_id for OAuth callers; an API key is scoped by the key. |
| response_format | enum(json | markdown) | json | Output format: 'json' for structured data, 'markdown' for human-readable text. |
Example Request
JSON
{
"model_id": "model_custom_abc",
"target_project_id": "proj_other456",
"team_id": "team_abc123",
"project_id": "proj_xyz789"
}Example Response
JSON
{
"model": {
"id": "model_custom_def",
"name": "My Dragon Style",
"ownerId": "proj_other456"
}
}Common Use Cases
- Copy a trained model into another project; the source model stays where it is