List projects

Lists the namespaces the caller can see with what each holds: the org's slug, its repository count on the OCI catalog, and its package count on the npm registry.

GET /v1/registry/projects

Addresshttps://api.hanzo.ai/v1/registry/projects
MethodGET
Operationget_registry_projects
AuthAuthorization: Bearer $HANZO_API_KEY

Lists the namespaces the caller can see with what each holds: the org's slug, its repository count on the OCI catalog, and its package count on the npm registry. Today that is exactly one row — the caller's org.

Request

GET /v1/registry/projects takes no parameters and no body — the credential is the whole request.

Response

StatusBodyMeaning
200registry.registryProjectListok
defaultproblem-detailsrefused

200 body — 4 fields.

FieldInTypeAlwaysDescription
databodyregistry.registryProject[]—Data is the namespaces visible to the caller.
data[].imagesbodyinteger (int64)—Images is how many of the org's repositories the OCI catalog holds.
data[].packagesbodyinteger (int64)—Packages is how many of the org's packages the npm registry reports.
data[].projectbodystring—Project is the namespace: the org's slug, which prefixes its image names and scopes its npm packages.

Failure carries the platform error shape — see Errors.

Examples

hanzo registry projects
import { Configuration, RegistryApi } from 'hanzoai';

const api = new RegistryApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.getRegistryProjects();
from hanzoai.cloud import ApiClient, Configuration
from hanzoai.cloud.api import RegistryApi

client = ApiClient(Configuration(access_token=os.environ["HANZO_API_KEY"]))
result = RegistryApi(client).get_registry_projects()
cfg := hanzoai.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := hanzoai.NewAPIClient(cfg)

resp, _, err := client.RegistryAPI.GetRegistryProjects(context.Background()).Execute()
if err != nil {
	return err
}
use hanzo_client::apis::{configuration::Configuration, registry_api};

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

let result = registry_api::get_registry_projects(&cfg, Default::default()).await?;
import ai.hanzo.cloud.ApiClient;
import ai.hanzo.cloud.api.RegistryApi;

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

var result = new RegistryApi(client).getRegistryProjects();
curl https://api.hanzo.ai/v1/registry/projects \
  -H "Authorization: Bearer $HANZO_API_KEY"

MCP reaches registry through the registry tool, which names its 5 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_registry_images"
         }
       }
     }'

Registry API · All Hanzo APIs · Interactive reference

Was this page useful?