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

# Agents

> Buyer agents your organization connects, and the agents that power a storefront: the hosted sales agent and the sales agents behind inventory sources.

An **agent** is a connected piece of software, never a person. What an agent is depends on the
workspace you're in.

## Agents in a buyer organization

In a buyer workspace, **Agents** sits next to Advertisers. A buyer agent is software your organization
connects to Semicola: your own planning agent, an agency tool, a reporting job. Keep these ideas
separate:

* The **agent** is the named software and its purpose.
* Its **principal** is the durable identity Semicola uses for routing and audit.
* A **credential** (an API key or an M2M client) lets the software prove that identity without a
  person's login.
* A **grant** is explicit permission on one advertiser, `READ` or `READ_WRITE`. Credentials and
  principals never imply a grant: a new agent has no advertiser access until an admin grants it.

Spend, payment and Terms authority are never inferred from a grant. Buyer agents call the v3 MCP
endpoint only. See [Buyer-agent credentials](/v2/setup/buyer-agent-credentials) for the console,
credentials and grants.

## Agents that power a storefront

In a seller workspace, **Agents** (in the left navigation) lists the agents behind your storefront.
`GET /api/v2/storefront/agents` returns the same list.

| Agent                    | What it is                                                                                |
| ------------------------ | ----------------------------------------------------------------------------------------- |
| **Sales agent** (hosted) | The storefront agent Semicola runs for you, at `/seller/<storefront>/mcp`. Role `SALES`.  |
| Connected sales agents   | Inventory sources that are themselves agents: your own AdCP sales agent, or a provider's. |

Ad servers and modular feeds aren't agents; they stay under the hosted agent's inventory sources.

### The hosted sales agent

Selecting it opens its sections:

| Section                 | Opens                                                                             |
| ----------------------- | --------------------------------------------------------------------------------- |
| **Overview**            | Identity, status and the next setup step.                                         |
| **Endpoint & protocol** | The Listing, with the agent's MCP endpoint.                                       |
| **Test & certify**      | Test runs against the agent (see [Test a sales agent](/skills/test-sales-agent)). |
| **Inventory sources**   | The sources the agent sells from.                                                 |

Its status reads **Configuring** until setup is done, then **Live**. Health follows the storefront's
liveness: `healthy`, `degraded` (needs attention), `unhealthy` (critical) or `unknown`.

### Connected sales agents

A connected agent shows its protocol, endpoint and a status of **Connected**, **Pending** or
**Disabled**. Its role and sections aren't known to Semicola, so it shows **Overview** only, which
opens the source's diagnostics. Credentials, connection tests and failures belong to the inventory
source, not the agent; see [Inventory sources](/sell/inventory-sources).

**API calls**, under Agents, opens the activity log's recorded API and MCP calls to your storefront
(`list_storefront_activity` with view `calls`; see [Audit logs](/guides/audit-logs)).

## Not available yet

* **Create Agent**, operators, and registering an observed implementation as a production revision.
* Sales-agent certification and a Partner listing.
* Signal, creative and outcome-measurement agents, and agents from a wider marketplace.
* Agent-level and per-account OAuth flows for connected agents.
* Semicola-hosted buyer agents: buyer agents are always your own software.