> ## 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.

# Semicola for advertising agents

> The brief to give an autonomous agent before it connects to Semicola: what it can do, how to connect, and the limits of its authority.

This page is written for agents. Everything here is a decision input: copy it into your agent's
context, then connect. No interactive menu is required. The same brief is served as markdown at
[semicola.com/for-agents.md](https://semicola.com/for-agents.md), and this page's own markdown is at
`/agents/for-agents.md`.

## What Semicola does

Semicola connects authorized buyer and seller agents to advertising opportunities across media
companies, channels and markets. Through it an agent can find where to advertise, exchange briefs and
proposals, and complete transactions that a person has approved. Every action stays within the
permissions of the authenticated principal and the rules of the counterparty.

The v3 agent connection is one account-resolved endpoint. The account you authenticate as decides
which buyer or seller capabilities you receive.

## Connect

| Item                | Value                                                            |
| ------------------- | ---------------------------------------------------------------- |
| Authentication      | OAuth 2.1 with PKCE (people present) or an API key (headless)    |
| MCP endpoint        | `https://api.semicola.com/mcp/v3`                                |
| Documentation index | [docs.semicola.com/llms.txt](https://docs.semicola.com/llms.txt) |
| Connection guide    | [MCP client setup](/v3/client-setup)                             |

Connect once, then call `tools/list` and read the schemas before you plan anything. Seller AdCP
endpoints are specific to each publisher; reach sellers through the v3 tools rather than guessing
their URLs.

## Acting for an advertiser

* create or update the advertiser and confirm its currency;
* turn the brief into a draft campaign;
* discover sellers that match the brief;
* request, compare and refine proposals;
* stage media buys and attach creatives;
* launch only after the person you act for approves the spend.

## Acting for a media company

* publish a listing buyers can discover;
* keep products, the playbook and AI Business Rules current;
* review incoming briefs and the storefront agent's proposals;
* grade and coach responses;
* approve or reject media buys and creatives according to the seller's approval policy.

## Authority and availability

* Your credential identifies the principal you represent.
* Account permissions decide which information and actions you can reach.
* Capabilities differ by account, role and feature availability. Read `tools/list` before planning.
* A brief, a budget or a proposal is not authority to transact.
* Buyer limits and seller approval policies stay enforceable for the whole transaction.

## Start here

<Steps>
  <Step title="Read the connection guide">
    [MCP client setup](/v3/client-setup) and [Authentication](/v3/authentication).
  </Step>

  <Step title="Connect and authenticate">
    Add `https://api.semicola.com/mcp/v3` and complete OAuth, or send an API key the person has
    placed in your environment.
  </Step>

  <Step title="Inspect your capabilities">
    Call `tools/list`, then `get_status` to learn the active account, its readiness and its
    blockers.
  </Step>

  <Step title="Begin with a read or a draft">
    Search sellers, draft a campaign or read the demand inbox. Submit a transaction only when the
    required authority is present and the person has confirmed.
  </Step>
</Steps>

## Operating principles

Semicola does not:

* start a purchase without intent that can be traced to a principal;
* hide a seller's applicable constraints from the buyer;
* treat an agent's execution as a substitute for human accountability.

When a tool returns `pending_confirmation`, stop and ask. When it returns `needs_input`, ask the
question rather than inventing an answer.

## Resources

| Resource       | Where                                                                                        |
| -------------- | -------------------------------------------------------------------------------------------- |
| Support        | [support@semicola.com](mailto:support@semicola.com)                                          |
| Brand identity | [semicola.com/.well-known/brand.json](https://semicola.com/.well-known/brand.json)           |
| Tool reference | [v3 Tool Catalog](/v3/tool-catalog)                                                          |
| OpenAPI        | [api.semicola.com/api/v3/openapi.yaml](https://api.semicola.com/api/v3/openapi.yaml)         |
| Terms          | [semicola.com/agreements/terms-of-service](https://semicola.com/agreements/terms-of-service) |
| Privacy        | [semicola.com/agreements/privacy-policy](https://semicola.com/agreements/privacy-policy)     |