Skip to main content

Agent Suites

The Agent Suites catalog sits under the Hub · Catalog eyebrow and is described as "Curated bundles of agents, skills, datasources, and MCP servers — installable as a unit." A suite packages everything a team needs for a complete enterprise workflow: the agents, the skills they rely on, the datasources they query, and the MCP servers they call — all pinned to specific versions and published as a cohesive artifact. Suites are versioned independently so the catalog always shows a stable history of what was published and when.

Catalog Statistics​

Three stat tiles above the card grid summarise the current catalog state:

  • Published suites — Total count of suite entries in the catalog.
  • Bundled agents — Sum of all agents across all published suites.
  • Total installs — Cumulative number of times suites have been installed across all tenants.

A single search bar sits above the card grid. Typing filters cards in real time by suite name, description, or slug. There is no category filter on the Suites catalog; all suites are surfaced in a single grid.

Catalog Card Grid​

Each suite is represented by a card in a responsive grid (one column on mobile, two on tablet, three on wide screens). The card surface shows:

  • Visibility eyebrow — Either public (visible to all tenants) or tenant list (visible only to the owning tenant and explicitly listed tenants).
  • Latest version — The most recently published version tag.
  • Suite name — The primary identifier for the suite.
  • Description — A brief summary of what the suite delivers.
  • Owner tenant — The tenant ID that published the suite, displayed as Owner tenant #N.
  • Agent count and install count — Displayed at the bottom of the card in the form N agents · N installs.
  • View link — Opens the suite detail page.

Suite Detail Page​

Clicking any card navigates to the suite detail page. The header shows the suite name, visibility eyebrow (public suite or tenant list), description, the latest version tag, agent count, install count, and the owning tenant ID. A Back to suites link returns to the catalog grid.

Tenants that own the suite see an Open in Studio action in the header, which opens the suite in Beak AI Studio for editing.

Versions Timeline​

The Versions section below the header lists every published version of the suite as a row of version buttons. Each button shows the version tag and its release date. Clicking a version button selects it and updates the Agents preview below to reflect the contents of that version. The latest version is selected by default.

Agents Preview​

The Agents section shows the agents bundled in the selected version as a card list. Each agent card displays:

  • Agent name — The agent's display name.
  • Slug — The agent's unique identifier in monospace.
  • Description — A brief summary of what the agent does.
  • Agent type — The agent's type designation, optionally followed by the industry tag.

An Open version detail link at the right of the section header navigates to the full version manifest page for the selected version.

Suite Version Page​

The version manifest page provides a complete read-only view of every component declared in a specific suite version. The page header shows the suite slug, the version tag as an eyebrow (Suite manifest · vX.Y), and a summary line of the form N agents · N skills · N datasources · N MCP servers.

Agent Sidebar​

A collapsible sidebar on the left lists every agent in the version. Each item shows the agent name, slug, and agent type. Clicking an agent row loads its manifest detail in the main panel on the right. The first agent is selected by default.

Agent Manifest Detail​

The main panel renders the selected agent's full manifest. The sections are:

Agent Header​

Shows the agent name, slug, agent type and industry eyebrow, and description.

Attribute Pills​

A row of inline pills summarises the agent's runtime configuration:

  • Model — The LLM model name.
  • Provider — The LLM provider.
  • Context — Context window size in tokens.
  • Memory — on or off.
  • Citations — on or off.
  • File upload — on or off.

System Prompt​

The agent's system prompt rendered in a scrollable monospace block. The block is capped at 360 px height with overflow scrolling.

Skills​

Lists all skills attached to this agent, resolved from the manifest's top-level skills catalog. Each skill entry is rendered by the SkillView component showing the skill's full detail.

Datasources​

Lists all datasources attached to this agent, resolved from the manifest's top-level datasources catalog. Each datasource entry is rendered by the DatasourceView component showing the datasource's full detail.

MCP Servers​

Lists all MCP servers referenced by this agent, resolved from the manifest's top-level MCP servers catalog. Each MCP server entry is rendered by the McpServerView component.

Sub-agents​

When an agent orchestrates other agents, the sub-agent slugs are listed as monospace pills.

Generative UI Actions​

When the agent declares generative UI actions, they are displayed in a scrollable JSON block.

Visibility​

Suites carry one of two visibility values that control who can discover them in the Hub catalog:

  • public — The suite is listed for all tenants browsing the Hub.
  • tenant list — The suite is listed only for the owning tenant and any tenants explicitly granted access.

Best Practices​

  • Pin to a specific version when integrating a suite into a production workflow — this protects against unintended changes when a new version is published.
  • Use the Versions timeline to compare what changed between releases before upgrading a deployed suite.
  • Review the MCP Servers and Datasources sections of each agent's manifest before installing a suite — these components may require separate credentials to be configured in the Runtime after deployment.
  • The Open in Studio action is available only to the tenant that owns the suite; if you need to customise a public suite, clone it in Beak AI Studio and publish the copy under your own tenant.
  • Use the Agent Manifest Detail to verify model selection and context window sizes meet your organization's LLM governance policies before installing.
  • Overview — Beak Hub landing page and catalog summary.
  • Agents — Individual pre-built agents available outside of suites.
  • MCP Servers — MCP servers referenced inside suite manifests.
  • Tenants & API Keys — Register tenants and manage the API keys their services authenticate with.