Skip to main content

Marketplace

Marketplace is how prebuilt work gets into a Runtime. It browses the Beak Hub catalogue and installs agent suites and individual agents into this Runtime, so a tenant starts from something that already works rather than from an empty agent list.

The page subtitle reads "Browse the Beak Hub and install agent suites and agents into this Runtime".

Agent Suites​

The default tab. A suite is a packaged set of agents that belong together — published once in the Hub and installed as a unit, with the agents, skills and configuration they depend on.

Installing a suite creates its agents in this Runtime. They then behave like any other agent here: they appear in Agents, are configured in Configure, and are governed by the same approval policies as anything built locally.

Agents​

The second tab lists individual agents published to the Hub, for when a suite is more than you need. Installation works the same way and produces the same result — an agent in this Runtime.

What installation does not do​

Installing from the Marketplace brings the agent's definition into the Runtime. It does not bring the tenant-specific things that definition depends on:

  • Connections to third-party systems must exist in this tenant — see Connections.
  • Model access comes from this tenant's own configuration, not the publisher's.
  • Knowledge sources must be synced here before the agent can answer from them — see Knowledge.

An installed agent that appears to do nothing useful is usually missing one of these rather than broken.

Access​

The page is available to operators holding the marketplace install permission. Without it the Marketplace is hidden, since browsing a catalogue you cannot install from has no purpose.

Best Practices​

  • Prefer a suite to assembling agents individually — Suites are published as a working set; the agents in them are configured to hand off to each other.
  • Check connections and knowledge before judging an installed agent — Most "it doesn't work" reports after an install are an unconfigured dependency, not the agent.
  • Review approval policies after installing — An installed agent may propose actions your existing rules never anticipated, and rules are matched by action name.
  • Install into a non-production tenant first where one exists — an installed agent is immediately available to the people who can see it.
  • Agent Suites — Working with suites already installed in this Runtime.
  • Beak Hub — The catalogue this page installs from.
  • Agents — Where installed agents appear.
  • Approval Policies — Governing what installed agents may do unattended.
  • Connections — The third-party access an installed agent needs.