Create mirror

Imports an external git repository into the caller's repo, provisioning it on first use.

POST /v1/git/repos/{name}/mirror

Git → · All API references → · Get started →

Address	`https://api.hanzo.ai/v1/git/repos/{name}/mirror`
Method	`POST`
Operation	`post_git_repos_by_name_mirror`
Auth	`Authorization: Bearer $HANZO_API_KEY`

Imports an external git repository into the caller's repo, provisioning it on first use. Fetch is FORCED and covers every ref, so a first call clones the source and a repeat call re-syncs it — the endpoint is idempotent by mirror semantics. Mirrored bytes are metered exactly like a push, and a push.landed event is emitted for the default branch so the code index picks the repo up.

Request

4 fields, body application/json (required).

Field	In	Type	Required	Description
`name`	path	string	yes	Name is the local repo to mirror into, from the :name path segment.
`name`	body	string	—	Name is the local repo to mirror into, from the :name path segment.
`project`	body	string	—	Project is the sub-scope to land the repo in; empty uses the caller's own, exactly as a create would.
`source`	body	string	—	Source is the http(s) git URL to fetch from.

Response

Status	Body	Meaning
`200`	git.repoView	ok
`default`	problem-details	refused

200 body — 14 fields.

Field	In	Type	Always	Description
`branches`	body	string[]	—	Branches are the repo's branch names.
`cloneUrl`	body	string	—	CloneURL is the HTTPS smart-HTTP remote `git clone` takes.
`createdAt`	body	string	—	CreatedAt is RFC 3339 UTC.
`defaultBranch`	body	string	—	DefaultBranch is where HEAD points on a fresh repo ("main").
`description`	body	string	—	Description is the caller-supplied blurb (max 4KiB).
`head`	body	string	—	Head is the resolved HEAD commit, empty on an empty repo.
`id`	body	string	—	ID is the repo's stable, prefixed identifier ("repo_" + 128 random bits).
`name`	body	string	—	Name is the org-unique handle, and the last path segment of both URLs below.
`org`	body	string	—	Org owns the repo — the gateway-minted X-Org-Id, and the isolation key.
`project`	body	string	—	Project is the optional sub-scope the repo lives in; absent for the org's default scope.
`public`	body	boolean	—	Public grants ANONYMOUS read (fetch) only; push and the whole control plane stay org-authed.
`sizeBytes`	body	integer (int64)	—	SizeBytes is the repo's measured on-disk size, re-measured on create, after each push, and after a gc.
`sshUrl`	body	string	—	SSHURL is the scp-style SSH remote (git@host:org/repo.git).
`updatedAt`	body	string	—	UpdatedAt is RFC 3339 UTC, empty until the first write.

Failure carries the platform error shape — see Errors.

Examples

CLI

SDK

HTTP

MCP

hanzo git repos mirror <name>

.ts

.py

.go

.rs

.java

import { Configuration, GitApi } from 'hanzoai';

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

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

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

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

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

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

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

let result = git_api::post_git_repos_by_name_mirror(&cfg, Default::default()).await?;

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

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

var result = new GitApi(client).postGitReposByNameMirror();

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 POST https://api.hanzo.ai/v1/git/repos/<name>/mirror \
  -H "Authorization: Bearer $HANZO_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
       "name": "<name>",
       "project": "<project>"
     }'

MCP reaches git through the git tool, which names its 38 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_git_keys"
         }
       }
     }'

Git API · All Hanzo APIs · Interactive reference

Was this page useful?

PreviousCreate gc NextCreate merge