Agents

What is an agent

An agent is the canonical AI persona unit in Ambrose. One agent = one identity + one voice + one memory + one set of capabilities.

What an agent owns

The nine exec heads are agents, fixed roster, always in the War Room.
Your custom agents are agents you create for specific jobs (a RenewalsBot, a Closebot persona, a VAPI voice agent).
A team is a separate row that bundles a prompt + tool access + GHL webhook. An agent can play a team for a specific task.

Every agent auto-publishes seven URL shapes, see 7 URL shapes per node.

## What is an agent

An agent is the canonical AI persona unit in Ambrose. One agent = one identity + one voice + one memory + one set of capabilities.

### What an agent owns

- A slug (kebab-case) that becomes the URL: /api/agent//run.

- A name and a role.

- Markdown files for identity / personality / memory / notes, see Agent files.

- A provider + model: Anthropic Claude or AWS Bedrock.

- An allowed_spokes list, which capabilities it can reach.

- (Optional) attached_teams: sub-agents it can delegate to.

- (Optional) attached_mcps: external MCP servers it can call.

- (Optional) consumer tokens: for shared API access.

### Agent vs Team vs Exec head

- The nine exec heads are agents, fixed roster, always in the War Room.

- Your custom agents are agents you create for specific jobs (a RenewalsBot, a Closebot persona, a VAPI voice agent).

- A team is a separate row that bundles a prompt + tool access + GHL webhook. An agent can play a team for a specific task.

### Endpoints every agent gets for free

Every agent auto-publishes seven URL shapes, see 7 URL shapes per node (/docs/connect-shapes).