Create keys

Registers an SSH public key so it can authenticate git clone git@<host>:<org>/<repo>.git for the caller's org.

POST /v1/git/keys

Git → · All API references → · Get started →

Address	`https://api.hanzo.ai/v1/git/keys`
Method	`POST`
Operation	`post_git_keys`
Auth	`Authorization: Bearer $HANZO_API_KEY`

Registers an SSH public key so it can authenticate git clone git@<host>:<org>/<repo>.git for the caller's org. The key line is parsed and canonicalized before storage, its SHA256 fingerprint becomes the auth lookup handle, and the full public key round-trips (it is public). Answers 201. Fingerprints are globally unique, so a key already registered — to this org or any other — is a 409: one key belongs to exactly one org.

Request

2 fields, body application/json (required).

Field	In	Type	Required	Description
`publicKey`	body	string	—	PublicKey is one OpenSSH authorized-key line ("ssh-ed25519 AAAA… you@host").
`title`	body	string	—	Title labels the key in the console.

Response

Status	Body	Meaning
`201`	git.keyView	created
`default`	problem-details	refused

201 body — 5 fields.

Field	In	Type	Always	Description
`createdAt`	body	string	—	CreatedAt is RFC 3339 UTC.
`fingerprint`	body	string	—	Fingerprint is the key's SHA256 fingerprint ("SHA256:…"), globally unique and the handle SSH auth resolves a presented key by.
`id`	body	string	—	ID is the key's identifier ("gitkey_…"), the handle to delete it by.
`publicKey`	body	string	—	PublicKey is the canonical OpenSSH authorized-key line as stored.
`title`	body	string	—	Title is the key's label — the caller's, or the comment on the key line.

Failure carries the platform error shape — see Errors.

Examples

CLI

SDK

HTTP

MCP

hanzo git keys create

.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.postGitKeys({ publicKey: "<publicKey>", title: "<title>" });

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_keys(public_key="<publicKey>", title="<title>")

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

resp, _, err := client.GitAPI.PostGitKeys(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_keys(&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).postGitKeys();

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/keys \
  -H "Authorization: Bearer $HANZO_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
       "publicKey": "<publicKey>",
       "title": "<title>"
     }'

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 git upload pack — POST /v1/git/{org}/{repo}/git-upload-pack NextCreate pools