Hanzo
OpenapiGit

Report your org's git storage footprint over the ZAP transport

Answers every repository in the caller's org with its size in bytes, plus the org's total — what git storage is actually being used, and by which…

POST /v1/git/zap/usage

Addresshttps://api.hanzo.ai/v1/git/zap/usage
MethodPOST
Operationpost_git_zap_usage
AuthAuthorization: Bearer $HANZO_API_KEY

Answers every repository in the caller's org with its size in bytes, plus the org's total — what git storage is actually being used, and by which repository. It reads NO body, and it is scoped to the caller's own org, so it is that org's footprint and never the fleet's.

A ZAP PROCEDURE, not a REST resource. It answers the bridge's {status, msg, data} envelope rather than the raw view the /v1 route returns — which is a wire shape a typed op cannot produce, and the reason this stays a raw handler — and it calls the SAME core function the REST route calls, so the two transports cannot diverge in behaviour. Org and project scope come from the request identity and NEVER from the body: the body cannot widen the caller's scope. Without a validated org the answer is a 403 envelope.

Request

The document declares no body for POST /v1/git/zap/usage. The handler is typed in cloud but its shape is not yet emitted, so the fields are not listed here — ask the MCP door's describe for post_git_zap_usage, which answers from the running route.

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 zap usage

Git API · All Hanzo APIs · Interactive reference

How is this guide?

On this page