List images

Lists the org's container repositories, read live from the OCI catalog and filtered server-side to the org's namespace — the page can only ever hold the caller's own images.

GET /v1/registry/images

Addresshttps://api.hanzo.ai/v1/registry/images
MethodGET
Operationget_registry_images
AuthAuthorization: Bearer $HANZO_API_KEY

Lists the org's container repositories, read live from the OCI catalog and filtered server-side to the org's namespace — the page can only ever hold the caller's own images.

Request

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

Response

StatusBodyMeaning
200registry.registryImageListok
defaultproblem-detailsrefused

200 body — 4 fields.

FieldInTypeAlwaysDescription
databodyregistry.registryImage[]—Data is the org's repositories.
data[].namebodystring—Name is the repository name inside the org's namespace (e.g. "cloud").
data[].refbodystring—Ref is the full pullable reference (host + org + name) the docker CLI takes verbatim.
truncatedbodyboolean—Truncated is true when the catalog walk hit its page bound before the registry was exhausted — the list is a prefix, not the whole.

Failure carries the platform error shape — see Errors.

Examples

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

const api = new RegistryApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.getRegistryImages();
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_images()
cfg := hanzoai.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := hanzoai.NewAPIClient(cfg)

resp, _, err := client.RegistryAPI.GetRegistryImages(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_images(&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).getRegistryImages();
curl https://api.hanzo.ai/v1/registry/images \
  -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?