Docs / ai / Agent Catalog

Agent Catalog

guide

There are no pre-built ecosystem agents — agents are per-app; you create them with casino_create_agent via the Casino MCP and target them by name.

There are no pre-built ecosystem agents. Agents are per-app — you create them with casino_create_agent via the Casino MCP, then select them with the persona option on useAgent.

The backend reads the agent definition from your app's config, injects the system prompt, and enforces the declared capabilities — the client cannot escalate to broader tool access.

Note: the SDK's dataScienceTemplate/marketingTemplate/supportTemplate (see Agent Templates & Factory) are client-side config scaffolds for ChatInterface, not registered backend agents — "no pre-built agents" refers to the backend persona catalog.

Examples

Creating an agent (MCP) — category grant
casino_create_agent(
  site_id="<your_site_id>",
  name="support_bot",
  system_prompt="You are a helpful support assistant...",
  capabilities=["data_access"]   // scopes what tools this agent can use
)
Creating an agent (MCP) — per-tool grant
casino_create_agent(
  site_id="<your_site_id>",
  name="readonly_bot",
  system_prompt="You are a read-only support assistant...",
  tools=["query_mongodb", "count_documents"]  // only these 2 tools, no writes
)
Targeting it from your app
const { query, messages } = useAgent(undefined, {
  persona: 'support_bot',
  capabilities: ['data_access'],
});

See also

targeting-custom-agents · tool-categories · tool-access-control · useAgent · useAgents

Source: README.md#agent-catalog · Also available in llms-full.txt and registry.json.