Serve a clone or fetch — POST /v1/git/{org}/{repo}/git-upload-pack
The pack-transfer phase of a clone or fetch: the request and the response are git's binary pack protocol, streamed straight through git itself — request…
POST /v1/git/{org}/{repo}/git-upload-pack
| Address | https://api.hanzo.ai/v1/git/{org}/{repo}/git-upload-pack |
| Method | POST |
| Operation | post_git_by_org_by_repo_git-upload-pack |
| Auth | Authorization: Bearer $HANZO_API_KEY |
The pack-transfer phase of a clone or fetch: the request and the response are git's binary pack protocol, streamed straight through git itself — request body to git's stdin, git's stdout to the response — so a multi-gigabyte clone never lands in this process's memory.
A PUBLIC repository is fetched anonymously; a private one requires its own org, and a wrong or absent org is 404 rather than a hint that the repository exists. A Content-Type other than application/x-git-upload-pack-request is 400. Addressed under the API prefix, so git clone https://<host>/v1/git/<org>/<repo>.git works on any host the binary serves. This is git's own wire protocol, not an API call to make by hand: point a git client at the clone URL and it makes this request itself.
Request
3 fields, body application/octet-stream.
| Field | In | Type | Required | Description |
|---|---|---|---|---|
org | path | string | yes | |
repo | path | string | yes | |
(body) | body | string (binary) | yes |
Response
The document declares no response body for this operation. It answers 200 on success and the platform error shape on failure — see Errors.
Examples
hanzo git org git-upload-pack <org> <repo>import { Configuration, GitApi } from 'hanzoai';
const api = new GitApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.postGitByOrgByRepoGit-upload-pack({ org: 'org', repo: 'repo' });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_by_org_by_repo_git-upload-pack(org='org', repo='repo')cfg := cloud.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := cloud.NewAPIClient(cfg)
resp, _, err := client.GitAPI.PostGitByOrgByRepoGit-upload-pack(context.Background()).Execute()
if err != nil {
return err
}use hanzo_cloud::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_by_org_by_repo_git-upload-pack(&cfg, Default::default()).await?;import ai.hanzo.cloud.ApiClient;
import ai.hanzo.cloud.api.GitApi;
ApiClient client = new ApiClient();
client.setRequestInterceptor(b -> b.header("Authorization", "Bearer " + System.getenv("HANZO_API_KEY")));
var result = new GitApi(client).postGitByOrgByRepoGit-upload-pack();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/<org>/<repo>/git-upload-pack \
-H "Authorization: Bearer $HANZO_API_KEY"Tool git, op post_git_by_org_by_repo_git-upload-pack — POST the JSON-RPC envelope to https://api.hanzo.ai/v1/mcp.
curl -X POST https://api.hanzo.ai/v1/mcp \
-H "Authorization: Bearer $HANZO_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "git",
"arguments": {
"op": "post_git_by_org_by_repo_git-upload-pack",
"input": {
"org": "<org>",
"repo": "<repo>"
}
}
}
}'How is this guide?