> ## Documentation Index
> Fetch the complete documentation index at: https://docs.exterview.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Roadmap to 100 Agents

> How the Smaya Agent Library grows from 26 today to 100 across the platform, and the principles that decide what becomes an agent and what does not.

## Purpose

The [Agent Library](/smaya/capabilities) is the platform's compounding asset. Every agent added is available to every application above it, under one governance model — so the cost of the hundredth agent is a fraction of the cost of the first.

This page states direction and sequence, not dates.

## Where the library stands

| Stage     |   Agents | Application                                       | Status                                   |
| --------- | -------: | ------------------------------------------------- | ---------------------------------------- |
| **Today** |   **26** | Exterview — talent                                | **Available** or **Upcoming**, per agent |
| **Next**  |  **+10** | Gradientflo — HR                                  | **Upcoming**                             |
| **Then**  | **→100** | IT service · customer service · sales · marketing | **Upcoming**                             |

```mermaid theme={null}
%%{init: {'theme':'base','themeVariables':{'primaryColor':'#EEF2FF','primaryBorderColor':'#4B6CFE','primaryTextColor':'#0F172A','lineColor':'#64748B','clusterBkg':'#F8FAFC','clusterBorder':'#E2E8F0'}}}%%
flowchart LR
  A([26 · Exterview]) -.-> B([36 · + Gradientflo · Upcoming])
  B -.-> C([100 · platform library · Upcoming])
```

*Exterview's 26 agents are the library today, each labelled Available or Upcoming. Dotted lines are Upcoming growth.*

## The seven business functions

An agent's address on the platform is its **business function**, its **stage** within that function, and the **industry** its expertise is tuned for. The function is the horizontal axis, and it is what makes 100 reachable without a second platform.

| Business function    | Status                                                               |
| -------------------- | -------------------------------------------------------------------- |
| **Recruiting**       | Available                                                            |
| **HR**               | Upcoming — 10 agents in Gradientflo                                  |
| **IT service**       | Upcoming — no agent registered yet                                   |
| **Customer service** | Upcoming — no agent registered yet                                   |
| **Sales**            | Upcoming — no agent registered yet                                   |
| **Marketing**        | Upcoming — no agent registered yet                                   |
| **Platform**         | Upcoming — cross-cutting roles, such as the Quality & Fairness Agent |

A function with no agent registered yet is a real, empty slot: the platform recognizes it, filters for it, and shows it as pending registration. No agent is invented to fill it and no code is assigned locally — registration goes through the same catalog every existing agent passed.

## What growth actually costs

The first application carried the platform: identity, permissions, approvals, evidence, integration, evaluation and the regulatory posture. That work is done and it is shared.

<CardGroup cols={3}>
  <Card title="Governance — reused" icon="shield-check">
    A new agent inherits the authority model, the approval gates, the record and the fairness measurement. None of it is rebuilt.
  </Card>

  <Card title="Integration — reused" icon="plug">
    Identity, calendar, meetings, mail and system-of-record connections are
    platform services.
  </Card>

  <Card title="Expertise — new each time" icon="brain">
    What is genuinely new per agent is the domain judgment: what counts as evidence, and what good looks like. That is the part worth paying for.
  </Card>
</CardGroup>

## What becomes an agent

Not every capability deserves one. The test we apply:

<CardGroup cols={2}>
  <Card title="It is accountable for one job" icon="target">
    If you cannot write its mandate in one sentence, it is either a feature of an existing agent or two agents wearing one name.
  </Card>

  <Card title="It produces a judgment backed by evidence" icon="file-check">
    If the output is a record rather than a judgment, it belongs in a system of
    record, not in an agent.
  </Card>

  <Card title="It can be governed" icon="lock">
    If we cannot state its authority, its approval points and what it may never
    do, it is not ready to be built.
  </Card>

  <Card title="A customer has asked for it" icon="users">
    Customer demand is the primary input to the sequence. Speculative agents are how a library becomes shelfware.
  </Card>
</CardGroup>

## How the sequence is decided

<Steps>
  <Step title="Demand">
    What customers are asking for, weighted by how many are asking and how much of their day it consumes.
  </Step>

  <Step title="Evidence readiness">
    Whether the platform already holds the evidence the agent would need. An agent
    without evidence is a guess with a job title.
  </Step>

  <Step title="Governability">
    Whether the authority, approvals and prohibitions can be stated clearly enough
    to be enforced.
  </Step>

  <Step title="Reuse">
    Whether it extends the shared library or only serves one workload. Shared capability wins.
  </Step>
</Steps>

## What we are not building

The library is a curated set of governed, pre-built agents. It is deliberately **not** an open marketplace, a plugin ecosystem, or a hosting service for third-party agents.

An agent that makes judgments about people carries obligations that cannot be delegated to an unknown publisher. Every agent in the library is one we built, tested and stand behind. Organizations needing something bespoke get it as a services engagement, built to the same standard.

## Related

<div className="kb-links">
  *   <span className="kb-ico">
        <Icon icon="boxes" />
      </span>
    [Agent Library](/smaya/capabilities). What is in it today.
  *   <span className="kb-ico">
        <img src="https://mintcdn.com/exterviewinc/2F3WHDYe4q7V4uTB/images/smaya/smaya-icon.webp?fit=max&auto=format&n=2F3WHDYe4q7V4uTB&q=85&s=e757bc266abe66ce35ab7128b7008cf8" alt="" className="smaya-ico" width="96" height="96" data-path="images/smaya/smaya-icon.webp" />
      </span>
    [Applications on Smaya](/smaya/applications). Where the next workloads come
    from.
</div>