Registry
The catalog of resources Orca Agent Engine exposes to agents and operators.
The registry is the catalog of resources available inside a Workspace. Its core API carries agent definitions, sessions, environments, files, vaults, skills, memory stores, Git credentials, and triggers, and every deployment serves it. StreamNative Cloud adds providers and streaming integration resources through the cloud.sn.io/v1 extension group.
What lives in the Registry
The registry organizes resources into groups, each documented in its own section of these docs.
Agent resources
The registry's primary group. Documented under Agents.
| Resource | Purpose |
|---|---|
| Agents | Reusable, versioned configurations: model, system prompt, tools, MCP servers, skills. |
| Sessions | Running agent instances within an environment. |
| Environments | Container templates that define packages and network policy. |
| Events & streaming | The events your application sends to and receives from sessions. |
| Files | Uploaded assets that agents can read in a session. |
| Vaults | Per-user credential storage, used for MCP server authentication at runtime. |
| Skills | Reusable, filesystem-based domain expertise that agents load on demand. |
| Triggers | Automation that creates sessions on a cron schedule in every deployment. StreamNative Cloud extends it with messaging sources. |
StreamNative Cloud integrations
These resources are available when the deployment advertises cloud.sn.io:
| Resource | Purpose |
|---|---|
| Connections | Reusable Pulsar, Kafka, and generic endpoints. |
| Packages | Versioned function, source, and sink artifacts. |
| Functions | Lightweight stream processing between Pulsar or Kafka topics. |
| Sources | Ingest external data into Pulsar. |
| Sinks | Deliver Pulsar records to external systems. |
| Kafka Connect | Kafka-native connector plugins, tasks, lifecycle, and offsets. |
MCP servers
The Model Context Protocol (MCP) servers that publish tools and resources to agents. An MCP server is not a registry resource of its own - there is no endpoint that creates or lists one. Each agent carries its own mcp_servers array, versioned with the agent, so the set of servers an agent reaches is part of that agent's definition. See MCP servers. The StreamNative Remote MCP Server separately publishes Workspace resources as MCP tools.
Providers
LLM endpoint configurations, on StreamNative Cloud only, served by the Cloud extensions group. For selecting a model on an agent, see Model access.
How the Registry is accessed
Every interaction with the registry happens through a registry endpoint. On StreamNative Cloud, each Workspace has its own: the endpoint URL is published in Workspace.status.serviceEndpoints[]. On a self-hosted deployment, it is the URL of the registry's public listener, and the credential selects the Workspace. Clients call:
https://<registry-host>/v1/...On a self-hosted deployment, see Connect to the registry for the endpoint and credentials.
You can interact with the registry through:
- The
orkCLI - the primary way for developers and operators to manage registry resources, including guardrails when the registry exposespolicy.runorca.ai. - The REST API - full operation set, fully documented under Registry API reference.
- The StreamNative Cloud Console - guided UI for browsing and managing resources.