Agent Registry

agent-registry is a self-hosted OCI container registry with a folder-backed store (no database) and per-owner permission scopes — every credential can be limited to pull-only and to a glob of image paths. The same single binary is both the server and the admin CLI, so the command you install can stand up a registry and manage its owners from your laptop against a remote one.

Two ways to run it

• Server: agent-registry serve (or no args) starts the registry, serving the OCI /v2/ API on REGISTRY_ADDR with state under USER_DATA_DIR.
• Admin CLI: any non-serve subcommand manages owners, repos, and tags. Point it at a remote registry with REGISTRY_REMOTE + REGISTRY_ADMIN_TOKEN to administer a deployed instance (e.g. registry.agentics.dk) without SSH.

Quick start

curl -fsSL https://agentics.dk/install/agent-registry.sh | bash
agent-registry version

# Manage a remote registry's owners from anywhere:
export REGISTRY_REMOTE=https://registry.agentics.dk
export REGISTRY_ADMIN_TOKEN=<token>
agent-registry owner list

See Quickstart for install options and a first owner, Owners & permissions for the scoped-credential model, and Reference for every command and environment variable.

Why it exists

• Customer-safe credentials. Issue pull-only owners scoped to a single image, so a customer can docker pull your product but can't push or read anything else.
• No database. All state is plain files under USER_DATA_DIR; tar czf is a complete backup.
• Standards-compliant. Works with docker, buildx, and multi-arch images (including OCI 1.1 attestation/referrers), so the normal Docker workflow just works.