# Ambrose OS

> Agentic AI operating system for insurance agencies — a back-office of named AI department heads (CMO, CRO, COO, CFO, CTO, Compliance, Research, Client-Success) that already know your book of business, carriers, campaigns, and GoHighLevel setup.

This is the documentation index for AI assistants and crawlers. Every link below is a public, fully server-rendered page (no JavaScript needed to read it). For the entire documentation as a single plain-text file, fetch https://app.hiambrose.com/llms-full.txt.

## Getting started
- [What is Ambrose?](https://app.hiambrose.com/docs/what-is-ambrose): Ambrose OS is an agentic AI operating system built for insurance agencies. Think of it as a back-office of named AI department heads — a CMO, CRO, COO, CFO, CTO, Compliance, Research, Client-Success —…
- [Quick tour](https://app.hiambrose.com/docs/quick-tour): A 5-minute walkthrough of every tab in the Ambrose top nav, in the order you will probably use them.
- [Sign up & first login](https://app.hiambrose.com/docs/signup-first-login): Create an Ambrose account, sign in, and finish the onboarding wizard in about 5 minutes.
- [GoHighLevel AI Context Snapshot](https://app.hiambrose.com/docs/ghl-snapshot): A ready-made GoHighLevel snapshot that keeps Ambrose's AI context in sync with every call, message, reply, note and CRM change — and ships proven ACA follow-up sequences you can turn on in minutes.
- [Core concepts](https://app.hiambrose.com/docs/core-concepts): Five terms you need to keep straight. Mixing them up is the most common source of confusion.
- [Glossary](https://app.hiambrose.com/docs/glossary): Quick definitions of every term you will see in the UI and the docs.

## Dashboard
- [Dashboard overview](https://app.hiambrose.com/docs/dashboard): The Dashboard is your home screen. It surfaces the numbers, the people, and the alerts you should look at first thing.
- [Widgets & quick stats](https://app.hiambrose.com/docs/dashboard-widgets): Every card on the dashboard is a widget. Some show numbers, some show lists, some are little forms.
- [Floating chat widget](https://app.hiambrose.com/docs/floating-chat): The little chat bubble in the bottom-right corner of every page. It is the same exec team as the War Room, just always-on-hand.

## War Room
- [What is the War Room](https://app.hiambrose.com/docs/war-room): The War Room is the chat surface for the executive team. Type a question; Ambrose decides which head answers, or convenes a small group, and synthesizes the response.
- [How to use the War Room](https://app.hiambrose.com/docs/war-room-howto): Tips for getting the most out of every chat.
- [Example: VAPI call summary](https://app.hiambrose.com/docs/war-room-vapi): Use Alex (COO) or Taylor (CCO) to pull yesterday's voice calls from VAPI, tag the missed ones, and propose follow-ups.
- [Example: GHL messages today + follow-up](https://app.hiambrose.com/docs/war-room-ghl): Pull every conversation that received an inbound message today, summarize, and queue follow-ups — all via the ghl spoke.
- [Example: Add context + move a contact through a GHL pipeline](https://app.hiambrose.com/docs/war-room-ghl-pipeline): Summarize a contact, tag them, and move their opportunity into the right pipeline and stage — notes, tags, and a stage change in one chat turn, all via the ghl spoke.
- [Example: Search ACA marketplace plans](https://app.hiambrose.com/docs/war-room-marketplace): Use the marketplace-finder spoke to get live ACA plans + APTC subsidy estimates from healthcare.gov in a single chat turn.
- [Example: Plan info by plan ID](https://app.hiambrose.com/docs/war-room-plan-id): When you already have a specific plan ID (HIOS), get the full benefit grid in one call.
- [Example: Ask the vault](https://app.hiambrose.com/docs/war-room-vault): Plain-English Q&A over your private book of business — CSVs, PDFs, XLSX files you uploaded.
- [Example: ICHRA savings & Medicare quotes](https://app.hiambrose.com/docs/war-room-quote): plan-quoter is the spoke for "what would this client save / pay" questions.

## Executive team
- [The nine heads (overview)](https://app.hiambrose.com/docs/exec-team): Ambrose ships with nine named executive heads. Each is a Claude Agent SDK session with a fixed personality, a curated set of spokes, and the authority to dispatch its own sub-specialists.
- [Ambrose — Chief of Staff](https://app.hiambrose.com/docs/head-ambrose): Orchestrator. Sits at the top of the war room and routes every question to the right head.
- [Morgan Chase — Chief Marketing Officer](https://app.hiambrose.com/docs/head-morgan): Owns content, campaigns, brand voice, and outbound channels.
- [Jordan Knox — Chief Revenue Officer](https://app.hiambrose.com/docs/head-jordan): Owns the sales pipeline, objection handling, close strategy, and quote generation.
- [Alex Rivera — Chief Operating Officer](https://app.hiambrose.com/docs/head-alex): Owns the operational layer — pipeline hygiene, automations, infrastructure between systems.
- [Taylor Brooks — Chief Client Officer](https://app.hiambrose.com/docs/head-taylor): Owns client success, churn risk, renewals, and post-sale relationships.
- [Dr. Elena Reyes — Compliance](https://app.hiambrose.com/docs/head-elena): Owns CMS marketing rules, HIPAA, BAA enforcement, and the veto gate on outbound content.
- [Sam Okafor — Research](https://app.hiambrose.com/docs/head-sam): Primary user of The Brain. Calls every federal/healthcare data MCP.
- [Casey Park — Chief Financial Officer](https://app.hiambrose.com/docs/head-casey): Owns revenue, commissions, reconciliation, and AI spend.
- [Riley Hart — Chief Technology Officer](https://app.hiambrose.com/docs/head-riley): Owns integrations, system health, automations, and the admin-ops surface.

## Agents
- [What is an agent](https://app.hiambrose.com/docs/agents): An agent is the canonical AI persona unit in Ambrose. One agent = one identity + one voice + one memory + one set of capabilities.
- [Create an agent](https://app.hiambrose.com/docs/agent-create): New agents take less than a minute. You can create them in the UI, via the floating chat widget, or by dropping a folder on disk (self-hosted).
- [Agent files](https://app.hiambrose.com/docs/agent-files): Each agent is a folder of markdown files. Edit any file and the next chat turn picks up the change.
- [Provider & model](https://app.hiambrose.com/docs/agent-model): Per-agent model selection. Pick the right model for the job and the budget.
- [Allowed spokes](https://app.hiambrose.com/docs/agent-spokes): Per-agent spoke allowlist. The agent can only call spokes that are explicitly on its list.
- [Attached teams](https://app.hiambrose.com/docs/agent-teams): Sub-agents the agent can delegate to via the Task tool.
- [Attached MCPs](https://app.hiambrose.com/docs/agent-mcps): External MCP servers (Slack, Linear, GitHub, Notion, …) mounted as tools on this agent.
- [Routines in an agent](https://app.hiambrose.com/docs/agent-routines): Schedule prompts to run automatically against this agent. Cron schedule + prompt body + (optional) target audience.
- [Consumer tokens](https://app.hiambrose.com/docs/agent-tokens): Per-agent, per-consumer bearer tokens. Surgical sharing.
- [Share an agent](https://app.hiambrose.com/docs/agent-share): One agent = many URL shapes. Pick the one your platform needs and paste.

## Teams
- [What is a team](https://app.hiambrose.com/docs/teams): A team is a role config. It bundles a prompt + tool access + routines + an immutable GHL webhook URL. Teams are the canonical surface for GHL workflow webhooks.
- [Create a team](https://app.hiambrose.com/docs/team-create): Teams take less than a minute. The webhook_id is assigned automatically — copy it once, paste into GHL.
- [Team prompts & files](https://app.hiambrose.com/docs/team-prompts): Teams have a primary prompt and any number of supporting markdown files.
- [Routines in a team](https://app.hiambrose.com/docs/team-routines): Same shape as agent routines. Cron + prompt + sink. Open the team detail → Routines tab.
- [Routine run logs](https://app.hiambrose.com/docs/team-logs): Every team run — routine-fired, webhook-fired, or manual — is logged with full input + output + tool calls.
- [GHL workflow webhook (deep dive)](https://app.hiambrose.com/docs/team-ghl-webhook): Every team auto-publishes one GHL workflow webhook URL. Point a GHL Workflow → Webhook action at it, and the team runs against the inbound contact on every trigger.
- [Team MCP endpoint (deep dive)](https://app.hiambrose.com/docs/team-mcp): Every team also publishes a Streamable HTTP MCP server. Mount the team URL in any MCP-aware client (Claude Desktop, Cursor, VAPI, Retell, your own SDK) and the team becomes a single tool with the righ…
- [Integration URLs](https://app.hiambrose.com/docs/team-integrations): Every team auto-publishes eight URL shapes for external systems.

## Routines
- [What routines do](https://app.hiambrose.com/docs/routines): A routine is a scheduled prompt attached to an agent or a team. It is the easiest way to make Ambrose run on its own — nightly book checks, weekly newsletters, daily KPI digests.
- [Cron syntax](https://app.hiambrose.com/docs/routines-cron): Five-field cron. UTC by default; toggle to your local zone in account settings.
- [History & logs](https://app.hiambrose.com/docs/routines-history): Every fire is logged with input, output, tool calls, tokens, latency, cost, and any errors.

## Claude Routines
- [What is a Claude Routine](https://app.hiambrose.com/docs/claude-routines): A Claude Routine is a saved Claude Code session on claude.ai that runs unattended when called.

## Spokes
- [What are spokes](https://app.hiambrose.com/docs/spokes): A spoke is a capability — one MCP server with a set of tools. Spokes are the things Ambrose can do; agents reach them through allowed_spokes.
- [agent-vault safe](https://app.hiambrose.com/docs/spoke-agent-vault): The agency's private book of business. CSV/PDF indexer, policy parsers, file watcher. Files never leave the account.
- [client-vault safe](https://app.hiambrose.com/docs/spoke-client-vault): Client-facing enrollment, policy, and document store. Sits next to agent-vault but indexed per client.
- [lead-memory safe](https://app.hiambrose.com/docs/spoke-lead-memory): Per-lead dossier store. Historical context across campaigns and conversations.
- [lead-hunter free](https://app.hiambrose.com/docs/spoke-lead-hunter): Prospect discovery and enrichment — Google Maps scraping, email guessing, verification.
- [demo-forge free](https://app.hiambrose.com/docs/spoke-demo-forge): Generates branded demo websites + JSON-LD schema for prospect outreach.
- [search-audit free](https://app.hiambrose.com/docs/spoke-search-audit): AEO/SEO website visibility audits. Scores sites on schema, content, technical, and AI-citation surface.
- [campaign-metrics scrub](https://app.hiambrose.com/docs/spoke-campaign-metrics): Campaign analytics across email, SMS, social — opens, clicks, replies, booked-call rates.
- [channel-bridge scrub](https://app.hiambrose.com/docs/spoke-channel-bridge): Outbound dispatcher for email, SMS, and Telegram. The single place messages actually leave your account.
- [plan-quoter scrub](https://app.hiambrose.com/docs/spoke-plan-quoter): ICHRA savings calculator + Medicare quoting + ACA marketplace quotes.
- [reply-bot scrub](https://app.hiambrose.com/docs/spoke-reply-bot): AI-drafted replies + appointment booking across email, SMS, and chat channels.
- [marketplace-finder free](https://app.hiambrose.com/docs/spoke-marketplace): Live ACA marketplace plan search + APTC subsidy estimator backed by healthcare.gov.
- [aca-watchdog free](https://app.hiambrose.com/docs/spoke-aca-watchdog): Scheduled ACA marketplace intelligence — cost hikes, carrier exits, benefit cuts, plan-year transitions.
- [medicare-watchdog free](https://app.hiambrose.com/docs/spoke-medicare-watchdog): Scheduled MAPD / PDP / Med Supp intelligence — cost hikes, plan discontinuations, network changes, Star Ratings, rate filings.
- [ghl scrub](https://app.hiambrose.com/docs/spoke-ghl): Full GoHighLevel v2 surface. Contacts, conversations, calls, pipelines, workflows, calendars, social, Voice AI, tasks, notes, custom fields.
- [agencybloc scrub](https://app.hiambrose.com/docs/spoke-agencybloc): Bi-directional AgencyBloc AMS+ connector. Pulls Individuals / Groups / Policies / Activities / Notes / Commissions into the vault; pushes Ambrose-generated notes / activities / fields back.
- [phi-gateway safe](https://app.hiambrose.com/docs/spoke-phi-gateway): PHI scrubber + re-hydrator. The safety rail every scrubbed-posture spoke calls before egress.
- [llm-analytics safe](https://app.hiambrose.com/docs/spoke-llm-analytics): Token usage + cost breakdown + provider performance analytics across every LLM call.
- [admin-ops safe](https://app.hiambrose.com/docs/spoke-admin-ops): Tenant-scoped read + create + update of Ambrose resources (agents, teams, skills, MCPs, routines). Used by the floating chat widget to let you build the OS with natural language.

## Skills
- [What are skills](https://app.hiambrose.com/docs/skills): A skill is a SKILL.md brief that teaches the AI how to use a specific spoke or workflow well. The Claude Agent SDK auto-discovers them and attaches them to every exec head.
- [Insurance content pack (9 skills)](https://app.hiambrose.com/docs/skills-insurance-pack): A ready-made set of 9 skills for producing compliant, data-backed insurance content and websites — available to every agency, selectable on any agent or team, and previewable on the Tools page.
- [Auto-attach to exec heads](https://app.hiambrose.com/docs/skills-auto-attach): Every project skill is automatically discovered and attached to every exec head. Drop a SKILL.md, the next chat turn picks it up.
- [Create a skill](https://app.hiambrose.com/docs/skills-create): Two minutes. Pick a name. Write a SKILL.md that explains the trigger, the tools, and the safety rails.

## MCP
- [What is MCP](https://app.hiambrose.com/docs/mcp): Model Context Protocol — the open standard for plugging external tools into an AI. Ambrose speaks MCP both ways: every spoke is an MCP server, and you can mount any external MCP server as tools.
- [Add an MCP server](https://app.hiambrose.com/docs/mcp-add): Settings → MCP → Add MCP server. Pick stdio or HTTP. Enter the connection details. Save.
- [Per-tool permissions](https://app.hiambrose.com/docs/mcp-permissions): Allowed_spokes gates a spoke. Per-tool permissions further restrict which actions inside a spoke / MCP an agent or team may call.
- [stdio vs HTTP](https://app.hiambrose.com/docs/mcp-stdio-vs-http): Two transports. Pick HTTP when the server lives across the network; pick stdio when it lives on the same box.

## Integrations
- [Integrations overview](https://app.hiambrose.com/docs/integrations): External systems that plug into Ambrose. Configure each one in Settings → Integrations.
- [GoHighLevel (GHL)](https://app.hiambrose.com/docs/int-ghl): The CRM most agencies use. Once connected, every spoke and every head that touches CRM works.
- [GoHighLevel AI Context Snapshot](https://app.hiambrose.com/docs/ghl-snapshot): A ready-made GoHighLevel snapshot that keeps Ambrose's AI context in sync with every call, message, reply, note and CRM change — and ships proven ACA follow-up sequences you can turn on in minutes.
- [HealthSherpa](https://app.hiambrose.com/docs/int-healthsherpa): ACA quoting + enrollment platform. Add your HealthSherpa API key for direct quote + enroll flows.
- [Twilio (SMS)](https://app.hiambrose.com/docs/int-twilio): Direct SMS sending when you do not want to route through a GHL conversation.
- [Slack](https://app.hiambrose.com/docs/int-slack): The fastest path is one-click "Add Ambrose to Slack" (and "Sign in with Slack") when your plan has it enabled — no app to build.
- [Discord](https://app.hiambrose.com/docs/int-discord): Webhook or bot. Webhook is easiest — no app creation, no permissions.
- [VAPI (voice)](https://app.hiambrose.com/docs/int-vapi): VAPI plugs into Ambrose three ways. Pick the one that fits.
- [Retell (voice)](https://app.hiambrose.com/docs/int-retell): Same idea as VAPI. Custom LLM (full takeover) or function call (during Retell's own conversation).
- [Closebot](https://app.hiambrose.com/docs/int-closebot): GHL chatbot with custom-tool webhook. Lets Closebot ask Ambrose anything mid-conversation.
- [Stripe](https://app.hiambrose.com/docs/int-stripe): For agencies that bill their own clients through Ambrose. Webhook-based event flow.
- [Linear](https://app.hiambrose.com/docs/int-linear): Mount the official Linear MCP server in 30 seconds — issues, projects, comments become tools for Riley and your engineering team.
- [Make / Zapier / generic webhook](https://app.hiambrose.com/docs/int-make-zapier): Anything that can POST JSON can hit Ambrose. Anything that needs a JSON response from Ambrose can call the run endpoint.
- [Claude Desktop / Cursor](https://app.hiambrose.com/docs/int-claude-cursor): Mount any Ambrose agent or team in Claude Desktop or Cursor via MCP.
- [Connect GitHub (push generated code)](https://app.hiambrose.com/docs/connect-github): Save a GitHub Personal Access Token so Ambrose agents can push the code and projects they generate straight to your own GitHub repositories. Your token, your repos, isolated to your agency.

## Files
- [File Library — folders, uploads, downloads](https://app.hiambrose.com/docs/file-library): The Files page is your agency file space: upload anything, organise into folders, and download.
- [Generate documents and files with agents](https://app.hiambrose.com/docs/generating-files): Ambrose agents can create real Excel, Word, PDF, and CSV documents, plus HTML pages and multi-file code projects, and they always land in your isolated file space.

## Settings
- [Settings overview](https://app.hiambrose.com/docs/settings): Seven tabs in Settings. API keys, PHI mode, integrations, MCPs, vault encryption, billing, privacy.
- [API keys (Anthropic / Bedrock)](https://app.hiambrose.com/docs/settings-api-keys): Two providers. Pick one (or both). Paste the key. Save.
- [PHI mode (Fast / Private / BAA)](https://app.hiambrose.com/docs/settings-phi): The HIPAA toggle. Sets the default mode for every chat unless overridden per-call.
- [Brand voice](https://app.hiambrose.com/docs/settings-brand): A short paragraph that defines how Ambrose talks for your agency. Set in Brand. Every outbound message is anchored against it.
- [Vault encryption](https://app.hiambrose.com/docs/settings-vault): The vault is encrypted at rest using a per-agency key. You can rotate the key or export everything at any time.
- [Billing & usage](https://app.hiambrose.com/docs/settings-billing): Add a card, top up credits, turn on auto top-up, review charges, and manage your subscription — everything on Settings → Billing.
- [Privacy](https://app.hiambrose.com/docs/settings-privacy): What Ambrose stores, what it sends out, and how to inspect every PHI scrub.

## Models
- [Supported models](https://app.hiambrose.com/docs/models): Anthropic Claude (direct or via AWS Bedrock) — Opus, Sonnet, Haiku. All have prompt-caching and tool use.
- [Anthropic Claude (direct)](https://app.hiambrose.com/docs/models-anthropic): Paste your sk-ant-… key in Settings → AI. Billing flows through Anthropic.
- [AWS Bedrock](https://app.hiambrose.com/docs/models-bedrock): Same Claude models, billed through your AWS account. Required for some compliance regimes.
- [System Bedrock fallback](https://app.hiambrose.com/docs/models-fallback): When you have not pasted any key, your agency falls back to SAA-managed Bedrock. Pay-per-use via credits.

## Connectors
- [Connect any system](https://app.hiambrose.com/docs/connect): Every agent and every team auto-publishes 7+ URL shapes. Pick the one your platform needs and paste.
- [7 URL shapes per node](https://app.hiambrose.com/docs/connect-shapes): Drop a folder, get 7 URLs. Same backend, 7 different shapes for different consumers.
- [OpenAI-compatible endpoint](https://app.hiambrose.com/docs/connect-openai): Drop in to any tool that supports the OpenAI Chat Completions API. Set base_url + model.
- [Streamable HTTP MCP](https://app.hiambrose.com/docs/connect-mcp-url): The modern MCP transport. One URL → mount in Claude Desktop, Cursor, VAPI, or your own SDK.
- [Bearer tokens](https://app.hiambrose.com/docs/connect-bearer): Three different tokens. Do not mix them up.

## Architecture
- [System architecture](https://app.hiambrose.com/docs/architecture): Ambrose is a multi-process stack with strict service responsibilities. This is the 30-second tour.
- [Services & ports](https://app.hiambrose.com/docs/arch-services): Full topology.
- [PHI Rail](https://app.hiambrose.com/docs/arch-phi-rail): Ambrose's redact-then-rehydrate pipeline. The compliance IP.
- [Data flow](https://app.hiambrose.com/docs/arch-data-flow): A typical "ask the war room" request, traced end to end.

## API Reference
- [Public endpoints](https://app.hiambrose.com/docs/api-public): Service discovery + node listings.
- [Per-node endpoints](https://app.hiambrose.com/docs/api-node): Every agent and every team gets these. {kind} = agent or team.
- [Management API (Teams & Agents)](https://app.hiambrose.com/docs/api-teams-agents): Programmatically manage agents, teams, their markdown files, sequences, skills, MCPs, Claude routines, and read logs — all with your Agency API key.
- [Token management](https://app.hiambrose.com/docs/api-tokens): Per-agent / per-team consumer tokens.
- [Vault API](https://app.hiambrose.com/docs/api-vault): Upload, reindex, query.