Agentrig
Registry

Registry overview

How registries and the directory work.

Registry overview

AgentRig separates installable registries from discovery surfaces.

The directory answers what exists. The registry answers what may be installed.

Core pieces

  • Official registry - hosted at https://agentrig.ai/registry.
  • Third-party registries - static signed registries that implement the same contract.
  • Directory - a curated discovery index at https://agentrig.ai/directory/index.json.
  • Submissions - review inputs that can become approved catalog listings and can separately be mirrored for audit when an admin starts that workflow.

Install contract

Public installation is allowed from an approved AgentRig catalog listing or an explicitly configured static signed third-party registry. In both cases the CLI consumes a validated InstallBundle; discovery metadata is never enough.

Canonical install refs use:

<registryAlias>/<namespace.plugin>

The unversioned form resolves to the registry's latest installable version. Append @<version> only when you need an exact reproducibility or rollback pin.

Canonical ids use:

namespace.plugin

Direct URLs, local files, ZIP uploads, author repos, and raw Convex storage bytes are not installable public sources. The official agentrig.ai endpoint may serve an approved listing's SDK-produced InstallBundle; that reviewed contract is distinct from arbitrary Convex-hosted payloads.

Version and integrity records

Registry histories expose latest_version, active_version, and immutable version records. During install, AgentRig resolves the requested latest or pinned version, validates the registry source/lock/review artifacts, and records the concrete version plus snapshot_digest in the local install ledger.

Plugin artifacts are the normal V1 distribution path. Standalone skill artifacts can also be installed directly:

agentrig skill install <provider> <registryAlias>/<namespace.skill>

Standalone MCP and hook installs without --pick are not a public V1 flow; install MCPs and hooks as plugin contents.

Discovery contract

The directory and submission surfaces may:

  • show external projects
  • show listed entries
  • link to upstream repos
  • offer maintainer review workflows

They must not imply install trust.

Use the pages in this section to host your own registry, understand trust tiers, and get listed in the directory.

On this page