Replace projects

Renames a project. It rewrites `partOf` on every declaration that names the project, in one commit to `hanzoai/universe`.

PUT /v1/platform/projects/{project}

Platform → · All API references → · Get started →


Address	`https://api.hanzo.ai/v1/platform/projects/{project}`
Method	`PUT`
Operation	`put_platform_projects_by_project`
Auth	`Authorization: Bearer $HANZO_API_KEY`

Renames a project.

It rewrites partOf on every declaration that names the project, in one commit to hanzoai/universe. 409 when the new name is already a project: fold into it with DELETE /v1/platform/projects/{project}?into=. mode as for create.

Request

5 fields, body application/json (required).

Field	In	Type	Required	Description
`project`	path	string	yes	Project is the project to rename, from the path.
`mode`	body	string	—	Mode is `branch` (the default) or `commit`.
`name`	body	string	—	Name is its new name, which no app may already name.
`org`	body	string	—	Org names the project's owner, defaulting to the caller's own scope.
`project`	body	string	—	Project is the project to rename, from the path.

Response

Status	Body	Meaning
`200`	platform.projectWrite	ok
`default`	problem-details	refused

200 body — 11 fields.

Field	In	Type	Always	Description
`commit`	body	string	—	Commit is the sha the change created, "" when nothing had to move.
`live`	body	boolean	—	Live says whether the generator will see it: true only on main.
`mode`	body	string	—	Mode is branch (a review; nothing deploys) or commit (main).
`moved`	body	platform.relabel[]	—	Moved are the declarations whose partOf moved, and from what.
`moved[].from`	body	string	—
`moved[].name`	body	string	—
`moved[].org`	body	string	—
`moved[].to`	body	string	—
`project`	body	string	—	Project is the project the change leaves the moved apps in.
`ref`	body	string	—	Ref is the branch the change was pushed to, main for a commit.
`review`	body	string	—	Review is where to open the pull request for a branch.

Failure carries the platform error shape — see Errors.

Examples

hanzo has no subcommand for this operation — the CLI serves only what cloud's live route table confirms. Use HTTP or an SDK.

import { Configuration, PlatformApi } from 'hanzoai';

const api = new PlatformApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.putPlatformProjectsByProject({ project: 'project', mode: "<mode>", name: "<name>" });

from hanzoai.cloud import ApiClient, Configuration
from hanzoai.cloud.api import PlatformApi

client = ApiClient(Configuration(access_token=os.environ["HANZO_API_KEY"]))
result = PlatformApi(client).put_platform_projects_by_project(project='project', mode="<mode>", name="<name>")

cfg := hanzoai.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := hanzoai.NewAPIClient(cfg)

resp, _, err := client.PlatformAPI.PutPlatformProjectsByProject(context.Background()).Execute()
if err != nil {
	return err
}

use hanzo_client::apis::{configuration::Configuration, platform_api};

let mut cfg = Configuration::new();
cfg.bearer_access_token = std::env::var("HANZO_API_KEY").ok();

let result = platform_api::put_platform_projects_by_project(&cfg, Default::default()).await?;

import ai.hanzo.cloud.ApiClient;
import ai.hanzo.cloud.api.PlatformApi;

ApiClient client = new ApiClient();
client.setBearerToken(System.getenv("HANZO_API_KEY"));

var result = new PlatformApi(client).putPlatformProjectsByProject();

The method above is the one at the current release of the document. [email protected] (npm) and [email protected] (PyPI) were generated from an earlier release, where this operation carried a different id, so it spells the method differently — regenerating the clients is what makes the two agree. SDKs →

curl -X PUT https://api.hanzo.ai/v1/platform/projects/<project> \
  -H "Authorization: Bearer $HANZO_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
       "mode": "<mode>",
       "name": "<name>"
     }'

MCP reaches platform through the platform tool, which names its 39 operations with its own verbs — this one among them, under a name only MCP declares. describe explains any of them:

curl -X POST https://api.hanzo.ai/v1/mcp \
  -H "Content-Type: application/json" \
  -d '{
       "jsonrpc": "2.0",
       "id": 1,
       "method": "tools/call",
       "params": {
         "name": "describe",
         "arguments": {
           "op": "list_builds"
         }
       }
     }'

Platform API · All Hanzo APIs · Interactive reference

Request

Response

Examples

On this page