Skip to content

Agent catalog

Shara has 20 departmental agents + Amadeus (the orchestrator) = 21 agents. An agent is an AI assistant for one area of your company (sales, finance, legal and so on). Of the 20 departmental agents, 15 are the ones you choose from and 5 are additional. By default each one carries the name of a historical figure from management, business or science, and you can change names and faces with a name and image pack. It isn’t a collection of loose chatbots: it’s one coordinated team that answers to a single person.

Amadeus is the conductor. It’s available on every plan. Think of it as an operations director: you explain what you need and it decides who does it, with what context and in what order. Its functions:

  • Coordinates: receives the request, identifies which agents resolve it and delegates with just enough context, without leaking data from one agent to another.
  • Synthesises: consolidates the results from several agents into a single response in your corporate tone.
  • Watches: intercepts any deviation from your IDENTITY.md (the file that holds each agent’s tone and rules) before giving anything back to you.
  • Escalates: opens an internal ticket or lets you know if the request falls outside the team’s scope.

Which model Amadeus uses depends on your plan. Models are always named by their alias, never by their real provider:

Plan Amadeus works with
First Prelude (agile and fast)
Pro Sonata (balanced)
Max, Max ×5 and Max ×20 Symphony (the most capable). You can lower it to Sonata in Settings
Concerto Local Concerto, on your own servers. In hybrid mode, Amadeus can use Symphony in the EU cloud

Amadeus doesn’t act outside the app without connectors with delegated permissions, doesn’t reveal the real provider (it always returns the alias) and doesn’t edit your identity without a patch signed in the audit log.

Shara has one simple communication rule: each person talks to the agent that fits their role, and Amadeus coordinates between agents.

  • The owner and the admins talk to Amadeus and have the full picture: they can ask for things that cross several departments at once. Amadeus breaks the task down, delegates to whichever specialists are needed and brings back a single response.
  • Each departmental employee talks to their own agent (the one for their area). A salesperson talks to Patterson; the support lead, to Wanamaker. It’s their direct point of contact for day-to-day work.
  • Coordination between agents always goes through Amadeus. If one department’s agent needs support from another, it escalates internally to Amadeus, which decides and distributes. There are never agents talking to each other behind your back.

A single point of contact per person: management with Amadeus, each employee with the agent for their department. That way the AI team behaves like a real org chart, not like twenty open chat windows. Roles are explained in First steps.

There’s no need to install or configure each agent one by one. Amadeus is on every plan, and you choose which departmental agents you activate according to your plan: 5 on First, 10 on Pro and all 15 on Max. The typical journey is:

  1. You choose a plan when creating the account. That plan determines how many agents you pick (see the table below).
  2. You choose your agents in the app, under Settings → Agents → Your agents. Only the owner and the admins can do it.
  3. You activate the company and define your corporate identity. From that moment, every agent works with your tone and your rules thanks to its IDENTITY.md.
  4. You assign employees to departments from the Team section. Each person is linked to the agent for their area and starts talking to it.
  5. You connect your tools (email, CRM, calendar, accounting) via OAuth. Each agent detects the active integrations and adds them to its capabilities with no extra configuration.
  6. You start delegating. The agents already know who you are, how you talk and what tools they have to work with.

Changing your choice: the 14-day window starts when you save your choice for the first time. During those 14 days you can change it freely. After that, the agents you chose stay and you can only add more by moving up to a bigger plan.

The additional agents (below) are the only explicit purchase: they’re hired one by one, from the Max plan up. A selectable agent you have not chosen, or an additional agent you have not hired, is not available to your company.

The 21 agents, their department, a sense of what each one does and the group each belongs to: the orchestrator, the 15 you can choose, or the 5 additional ones.

The last column is the API slug: the name the API uses. In the API and the SDK you always use the slug, whichever pack you have chosen. It is the agent’s name in the Shara pack, in lowercase.

Agent Department What it does Group API slug
Amadeus Orchestrator Coordinates the team Orchestrator amadeus
Wanamaker Customer service Tickets, triage and on-brand replies Selectable wanamaker
Patterson Sales Qualifies leads, proposals and follow-ups Selectable patterson
Hopkins Marketing Content, newsletters and editorial calendar Selectable hopkins
Graham Finance Invoicing, reconciliation and KPIs Selectable graham
Maslow HR Onboarding, internal communication and evaluation Selectable maslow
Deming Operations Optimizes processes, cycle time and bottlenecks Selectable deming
Holmes Legal Contract reading and regulatory alerts Selectable holmes
Nightingale Data analytics Dashboards, KPIs and reports with narrative Additional nightingale
Turing IT and systems Monitoring, access and technical documentation Selectable turing
Whitney Quality Output QA, complaints Pareto and ISO 9001 Selectable whitney
Rockefeller Strategy Competitive analysis and positioning Selectable rockefeller
Brunel Engineering Technical specs and architecture Additional brunel
Eastman Product Feedback, prioritization and roadmap Selectable eastman
Bernays Communication Press releases and communication plan Selectable bernays
Kerckhoffs Cybersecurity Virtual CISO: policies, OWASP and runbooks Additional kerckhoffs
Barnum Events Logistics and event communication Additional barnum
Curie R&D Technology watch and experiments Additional curie
Shannon Technical support Helpdesk and knowledge base Selectable shannon
Gantt Projects / PMO Milestones, deadlines and delay detection Selectable gantt
Ohno Procurement Suppliers, budgets and orders Selectable ohno
  • Amadeus (the orchestrator) is on every plan.
  • First: you choose 5 of the 15 selectable agents.
  • Pro: you choose 10 of the 15.
  • Max (and Max ×5 / ×20): all 15 selectable agents.
  • Additional (€99/month and 15M STU each, hireable from Max): Curie, Kerckhoffs, Nightingale, Brunel and Barnum. STU is the unit that measures consumption; see STU and quotas.
  • Concerto Local: all 20 departmental agents (the 15 selectable plus the 5 additional ones) come included by default, at no extra charge for any of them, on your own infrastructure with the Concerto model. It can work with no cloud call at all; the hybrid mode for Amadeus is optional.

The choice can be changed freely during the first 14 days; after that you can only add agents by moving up a plan. A selectable agent you have not chosen, or an additional agent you have not hired, is not available to your company. First and Pro can’t hire additional agents: that upgrade is reserved for Max and above. Check Plans and pricing for the full detail on quotas and cost.

The profiles below are grouped by area to make them easier to read; any of them can be chosen on any plan that lets you choose.

  • Wanamaker · customer service. Answers tickets and emails in your tone and sorts them by urgency, sentiment and category. Starts in draft mode.
  • Patterson · sales. Qualifies and scores leads with your CRM, schedules sales activity, drafts proposals and follow-ups.
  • Hopkins · marketing. Drafts posts, newsletters and landing copy, and keeps the editorial calendar. Anything that goes out waits for your approval.
  • Graham · finance. Invoicing with Holded, bank reconciliation, KPIs (cash flow, margin, runway, DSO/DPO) and reporting. Human approval always required to issue invoices or payments.
  • Maslow · HR. Onboarding, internal communications, document management and 1:1 evaluation. Human approval on salaries, contracts and terminations; strict confidentiality.
  • Bernays · communication. Press releases, communication plan for milestones and crises, media relations. Human approval always required for official external communications.
  • Deming · operations. Maps the operational flow, measures cycle time, spots bottlenecks and proposes PDCA experiments. Optimizes the process.
  • Holmes · legal. Assisted reading of contracts (NDA, SaaS, partnerships, labour), detection of unusual clauses and regulatory alerts (GDPR, NIS2, AI Act). Doesn’t replace a lawyer.
  • Whitney · quality. Audits output correctness (automated QA, complaints Pareto, 5-whys, light ISO 9001 audit). Works in tandem with Deming.
  • Turing · IT and systems. Internal monitoring, maintenance scripts (backups, log rotation), access management (onboarding/offboarding, MFA, reset) and technical documentation.
  • Shannon · technical support. Internal and external helpdesk, up-to-date knowledge base, triage, escalation to a human and reports on recurring tickets.
  • Ohno · procurement. Supplier catalog with SLAs, budget comparison, orders with stock thresholds and spending audits.
  • Rockefeller · strategy. Five forces analysis, competitive mapping, positioning recommendations and market tracking.
  • Eastman · product. Collects feedback, prioritizes (RICE/ICE/MoSCoW), maintains the roadmap and coordinates launches with Hopkins and Bernays.
  • Gantt · projects / PMO. Structures projects into milestones and tasks, assigns owners and deadlines, reminders and early delay detection.

Hired at €99/month + 15M STU each, on any plan from Max up. They expand the team with more specialized areas:

  • Curie · R&D. Technology watch (papers, patents), A/B experiment design, technical summaries and support for grant applications (CDTI, ENISA, NEOTEC).
  • Kerckhoffs · cybersecurity. A virtual CISO (chief information security officer), and it is an AI agent, not a human service: password policies, OWASP Top 10, STRIDE threat modelling, incident runbooks and CVE searches against your stack. Doesn’t replace a pentester or generate exploits.
  • Nightingale · data analytics. Dashboards, KPIs by department, reports with narrative and anomaly detection.
  • Brunel · engineering. Drafts of technical specs (RFCs, ADRs), effort estimates and architecture review (C4).
  • Barnum · events. Action plan, communications to attendees, logistics (venues, catering, AV, speakers) and post-event follow-up.

Each company chooses how its agents are named and what they look like. The agent’s slug, its tools and its way of working do not change: the API and the SDK keep using the slug, so agentSlug: "patterson" works with any pack.

You pick the pack in the app, under Settings → Agents → Name pack.

Imagine you write to Amadeus: “Prepare this month’s sales summary and notify clients with proposals pending signature.” Here’s what happens underneath:

  1. Amadeus breaks down the request: there’s a pipeline analysis part (sales) and a client communication part (sales + customer service).
  2. It delegates the summary to Patterson (sales), who reads your CRM and reports the status of the proposals.
  3. It hands the notifications to Patterson and Wanamaker (customer service), who draft the emails in your corporate tone.
  4. The emails aren’t sent: they land as proposals in your approval inbox for your sign-off.
  5. Amadeus consolidates everything into a single response and delivers it to you along with the actions pending approval. The whole chain is logged in the audit log.

You gave one order; Amadeus moved three agents, respected your tone and left the sensitive actions waiting for your approval. That’s Shara’s work pattern for any request.

Everything that touches the real world goes through approval

Section titled “Everything that touches the real world goes through approval”

Agents read your tools with total freedom, but any action with a real effect (sending an email, issuing an invoice, placing an order) is generated as a proposal and waits for your approval. It’s a design guarantee: no agent executes sensitive actions on its own, and whoever approves is always a person, never a bot. Read Approvals for the full detail.

  • Turing vs. Holmes vs. Kerckhoffs: Turing is the sysadmin (access, backups, systems), Holmes covers the legal-contractual side (contracts, clauses, regulation) and Kerckhoffs covers technical security (policies, OWASP, incidents).
  • Deming vs. Whitney: Deming optimizes the process (cycle time, lean, flow); Whitney audits output correctness (QA, ISO 9001, complaints Pareto). They work in tandem.
  • Hopkins vs. Bernays: Hopkins is marketing (content, campaigns, acquisition); Bernays is communication (press, reputation, crisis).
  • Patterson vs. Eastman: Patterson sells (leads, proposals, closing); Eastman does product (feedback, roadmap, prioritization).
  • Can I talk to a specific agent without going through Amadeus? If you’re an employee in a department, yes: you talk to the agent for your area. Coordination between agents is still handled by Amadeus.
  • Do the agents talk to each other on their own? No. All coordination goes through Amadeus, with just enough context and without leaking data from one area to another.
  • Can I deactivate an agent I don’t use? No need: you only consume STU when you use it. An inactive agent generates no cost.
  • Can I change the agents I chose? Yes, freely during the first 14 days. After that you can only add agents by moving up a plan.
  • Can I change an agent’s name or tone? The name and the image come from your name and image pack, and how the agent works and its tone are fully adjustable through its IDENTITY.md. Read Agent identity.
  • Which model does each agent use? It depends on your plan. On First and Pro the departmental agents work with Prelude; on Max they work with Sonata (or Prelude), and on Max ×5 and Max ×20 they can go up to Symphony. On Concerto Local they use Concerto. In the app, Shara decides the model for each step according to your plan, the time of day and your quota, and the real provider stays hidden. Through the API you choose the alias yourself, up to the ceiling of your plan: if you ask for a higher one, it answers 422 alias_plan_mismatch.

Key catalog distinction: Turing is the sysadmin, Holmes covers the legal-contractual side and Kerckhoffs covers technical security. Continue with Agent identity to see how each one learns to sound like your company.