Shara

Shara is a platform of departmental AI agents governed by a central orchestrator, Amadeus. Each agent covers an area of your company and works with your corporate identity, your tone and your rules, always with full auditing and human control. Instead of twenty loose chatbots, you get one coordinated team that answers to a single person.

Shara is a departmental AI team: a director (Amadeus) receives your requests, decides which specialists resolve them and gives you back a single, consolidated answer. Each specialist masters their area (customer service, sales, marketing, finance, HR, operations, legal, analytics and more) and acts according to the rules you define in your corporate identity.

Unlike a generic assistant, Shara is designed to delegate real operational work without losing control: every action with an effect in the real world (sending an email, issuing an invoice, publishing a post) goes through your human approval before it executes, and every decision is left in a queryable audit log. The promise isn’t “a smarter chatbot”, it’s a team that works, documents what it does and asks your permission for what matters.

• A single point of contact. You talk to Amadeus the way you’d talk to an operations director; it distributes the work internally.
• On-brand by default. Everything Shara produces comes out in your tone, your values and your rules, not in a neutral factory voice.
• With a handbrake. Sensitive actions (money, contracts, external communication) require your sign-off; nothing runs behind your back.
• Traceable end to end. From the request to the result, everything is logged: who asked for what, which agent resolved it, which model was used and what was consumed.

Shara doesn’t replace your team: it takes the repetitive work off their plate and lets people decide. The human is always in the loop for the actions that matter.

For SMEs and professionals without a technical team who want to delegate operational tasks to AI without giving up control. It works especially well in office sectors with a high volume of repetitive work: accounting and tax advisory firms, B2B consultancies, and marketing and communication agencies. If you need work to be logged, reviewable and under your sign-off, Shara is built for you. Below we go into detail on each of these three profiles.

The best way to explain Shara is to follow a request from the moment it leaves your mouth to the moment you get the result. Imagine you write to Amadeus: “Prepare this week’s support ticket close-out and propose a follow-up email to the three clients with the most incidents.” Here’s what happens underneath, step by step:

1. Authenticated entry. Your message enters through the API behind a signed JWT. The tenant middleware fixes your organization as a mandatory filter: from here on, no other client’s data is accessible.
2. Identity loading. Before reasoning, your corporate identity (IDENTITY.md) is injected: tone, values, rules and restrictions. Everything produced from here on comes out on-brand.
3. Orchestration. Amadeus analyzes the request and breaks it down: the ticket summary belongs to Carlzon (customer service), and so does the follow-up email, with support from Carnegie (sales) if there’s a commercial opportunity. It delegates with the necessary context, without leaking data between agents.
4. Model selection. A selector picks the right tier by alias (Prelude, Sonata, Symphony) based on complexity, time of day and available quota. You never choose the model: the platform decides it.
5. Execution with connectors. The agents read from your connected tools (helpdesk, CRM, email) with permissions delegated via OAuth2. Reading is direct; writing requires approval.
6. Action → approval. The follow-up email isn’t sent: it’s generated as a proposal and lands in your approval inbox. You review it, edit it if you want and approve or reject it.
7. Output drafting. Before returning anything, a redactor reviews the response to avoid leaks (for example, the real provider behind an alias) and out-of-context sensitive data.
8. Consolidation. Amadeus merges the agents’ results into a single response with your tone, and delivers it to you along with the actions pending your sign-off.
9. Traceability and consumption. The whole chain is logged in the audit log (who, what, which agent, which model, before/after) and consumption is counted in STU, the single unit of measurement.

What you receive isn’t just the text: it’s the text + the proposed actions + the trail of how it was reached. That traceability is what turns an AI response into something you can audit, defend to a client or an inspection, and improve over time.

If you’d rather see it as data, a request to an agent and its response take this shape (simplified view of the public API):

# Launch a task against the customer service agent
curl -X POST https://api.aiginer.com/v1/agents/carlzon/run \
  -H "Authorization: Bearer $SHARA_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "input": "Summarize the support tickets from this week and propose a follow-up email to the 3 clients with the most incidents.",
    "require_approval": true
  }'

{
  "run_id": "run_8sK2pQ",
  "status": "completed",
  "agent": "carlzon",
  "model_tier": "Sonata",
  "output": {
    "summary": "37 tickets this week (-12% vs. previous). Top reasons: billing (14), access (9), shipping (7).",
    "proposed_actions": [
      {
        "type": "email.draft",
        "approval_id": "apr_4Lm9Zx",
        "status": "pending_approval",
        "to": "client@example.com",
        "subject": "Follow-up on your incidents this week"
      }
    ]
  },
  "usage": { "stu": 142 },
  "audit_log_id": "aud_Qw7Hn1"
}

Notice three fields: model_tier is always an alias (never the real provider), proposed_actions comes in pending_approval (nothing runs without you) and audit_log_id gives you traceability of the whole chain. To resolve the approval, one more request:

# Approve the proposed action (must be done by a human with approvals:write scope)
curl -X POST https://api.aiginer.com/v1/approvals/apr_4Lm9Zx/accept \
  -H "Authorization: Bearer $SHARA_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{ "reason": "Reviewed and approved by the support lead" }'

Approvals can’t be executed by a bot: they require a credential with approvals:write scope tied to a person. The human in the loop is a design guarantee, not an option. Read REST API.

• Amadeus orchestrates. There are no loose agents: there’s a director who coordinates the departmental agents and answers to a single person.
• A living corporate identity. Your IDENTITY.md (tone, values, rules) is injected into every interaction and updated through patches, never through a full replacement. Every patch is logged in the audit trail.
• Public models, no lock-in. You work with four models by alias (Prelude, Sonata, Symphony and Concerto). When a better engine appears, we swap it underneath without your team having to relearn anything. Read No vendor lock-in.
• Predictable cost + automatic saving mode. A single unit of consumption (STU) and automatic spending cuts. Outside your business hours, agents downgrade their model to save.
• Traceability as a first-class citizen. The audit log isn’t an add-on: it’s part of the product. Every action with an effect is logged with its before/after.

Shara is horizontal (it serves any office-based SME), but there are three profiles where the fit is especially direct because their day-to-day is full of repetitive work, with its own tone and a need to leave a trail. For each one: what hurts them and how the agent team covers it.

Tax, labour, accounting and corporate law firms with a high volume of tasks that repeat every month and every quarter, and brutal peaks during campaign season (income tax, closing, quarterly filings). The bottleneck is almost never complexity: it’s volume and the customer service that surrounds it.

What usually hurts them:

• The monthly tax close and quarterly VAT eat up hours of mechanical, repetitive work.
• Customer service gets swamped during campaign season: the same emails (pending documentation, deadlines, reminders) over and over.
• Onboarding new clients is manual: requesting documents, setting up folders, registering them, explaining the process.

How Shara fits: Graham (finance) prepares reconciliations, KPIs and reporting, and leaves the issuing of any invoice or payment for your approval; Carlzon (customer service) absorbs the flood of campaign-season emails with urgency triage and replies in your tone; Maslow (HR) and Carlzon structure repetitive onboarding. Since every document and every email come out on-brand and everything is logged, the firm gains capacity without losing the professional control its clients expect. Recommended plan: Pro.

Business, IT and management consultancies with teams of 10-50 people who sell knowledge and hours. Their product is the proposal, the analysis and the deliverable, and any minute that isn’t billable or strategic is pure cost.

What usually hurts them:

• Building commercial proposals is slow: each one is put together almost from scratch even though 70% could be reused.
• Competitive and strategic analysis is done ad hoc, with no process or living repository.
• Project management lacks visibility: a project running late is spotted too late.

How Shara fits: Carnegie (sales) speeds up proposals by reusing what already worked and adapting it to the client; Porter (strategy) systematizes competitive analysis (five forces, mapping, positioning) and keeps it alive instead of starting from scratch every time; Rosling (analytics) turns scattered data into reports with narrative; and Tracy (PMO, additional agent) structures projects into milestones with early delay detection. The consultant spends their time thinking and selling, not formatting documents. Recommended plan: Max.

Creative, performance, social media and PR agencies running several clients at once, each with its own brand, tone and calendar. The challenge isn’t a lack of ideas: it’s producing at scale while keeping each brand distinct and reporting without eating into the margin.

What usually hurts them:

• Generating on-brand content at scale for several clients without everything “sounding the same”.
• Monthly client reporting is repetitive and eats up non-billable hours.
• Coordinating the multi-client editorial calendar without overlaps or missed posts.

How Shara fits: this is where the living corporate identity shines. Each of the agency’s clients can have its own identity, so Kotler (marketing) and Bernays (communication) produce posts, newsletters and press releases that sound like that brand and not a generic voice; Rosling (analytics) automates monthly reporting with narrative; and Tracy (PMO) coordinates the multi-client editorial calendar. Human approval guarantees that nothing gets published without the account manager’s sign-off. Recommended plan: Pro (or Max if the agency wants Bernays for communication).

Shara is aimed at office sectors with repetitive work. It isn’t designed for high regulatory-risk environments like pharma. Read the agent catalog to see all 21 available.

1. Create your account at the Shara panel and choose a plan. You’ll receive your company key by email in the format SHARA-XXXX-XXXX-XXXX-XXXX.
2. Activate the company: trade name, sector, team size and business hours (outside of them, saving mode applies). Verify the admin email, set your timezone (Europe/Madrid by default) and accept the DPA.
3. Invite your first employee from Team, with their role and departments. Only the CEO or whoever has permission talks to Amadeus; each employee talks to their own agent.
4. Connect your tools (email, calendar, CRM, ERP) via standard OAuth2. Read Connectors.
5. Talk to Amadeus. For example: “Give me an executive summary of the last month: closed sales, open pipeline, pending tickets and financial alerts.” Amadeus delegates and consolidates the response.

Once inside, day-to-day work happens in two modes: the desktop app (recommended, with native notifications and the approval inbox at hand) and the REST API to integrate Shara into your own flows. A minimal example in Python to check this month’s usage:

import os, requests

BASE = "https://api.aiginer.com/v1"
headers = {"Authorization": f"Bearer {os.environ['SHARA_TOKEN']}"}

# STU consumption for the current month
usage = requests.get(f"{BASE}/usage/current", headers=headers).json()
print(f"STU consumed this month: {usage['stu_used']} / {usage['stu_quota']}")

# Approvals awaiting your sign-off
pending = requests.get(f"{BASE}/approvals", headers=headers).json()
print(f"Actions awaiting approval: {len(pending['items'])}")

Self-serve on First and Pro; guided onboarding on Max and Concerto Local. Questions while getting started? Write to support@aiginer.com.

This page is the map. From here, depending on what you want to understand:

• First steps: activate your account, invite your team and leave your first task in five steps.
• Agent catalog: Amadeus + the 20 specialists, what each one does and on which plan.
• Plans and pricing: First, Pro, Max and Concerto Local, with their STU quota and agents.
• Connectors: which tools you can plug in (email, chat, calendar, CRM, ERP) and how.
• STU and quotas: how consumption is measured, what an STU is and how spending cuts work.
• No vendor lock-in: why you work with model aliases and never end up tied to a provider.
• REST API: authentication, endpoints, signed webhooks and SDKs to integrate Shara.
• Concerto Local: Shara 100% on-premise on your own infrastructure with the Concerto engine (€999/month, no cloud component).
• Glossary: Shara’s terms (tenant, STU, identity, tier, orchestrator) on one page.