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

# Set up: Brand Book to first change

> One route from your website to your plan: the Brand Book the agents drafted, the few questions only you can answer, what the assistants say today question by question, and where changes go, all before you pay.

Setup at `/setup` takes you from your website to your plan in five steps. Each step shows work the agents have already done for your business. Nothing is charged before the last step, and nothing is published to your site before your plan starts.

`/setup` reads and writes the same set-up record as [the steps on /start](https://docs.attensira.com/start/first-fifteen-minutes.md). A workspace set up on either route is the same workspace.

When you arrive from a [free audit](https://docs.attensira.com/start/free-audit.md), setup does not ask again for what the audit already answered. See [Arriving from the free audit](#arriving-from-the-free-audit).

**1. Your Brand Book**

The agents read your site and draft your Brand Book. It holds the facts the site states, your competitors, voice rules and the phrases a draft must never use. Every fact shows the page it came from, or says you wrote it. A fact with neither is never shown.

Facts appear as each page is read, and you can continue while the draft is still going. If your homepage cannot be read, the step asks you to paste its text, and the Brand Book is drafted from that. If the draft stops for a reason on our side, it says so and offers **Retry now**. A draft that stopped this way is not tried again by itself, and you can continue to the next step meanwhile.

Suggested never-say phrases stop nothing until you keep them. Phrases on your own rules stop any draft that contains them.

**2. A few questions only you can answer**

You get at most three questions. They are chosen from the essential facts your site did not state, and each says why it is asked. One you already answered somewhere else, in a chat or in the Inbox, is not asked again; the next gap takes its place. An answer is saved to your Brand Book as yours, not as a draft. Leave a field blank to answer it later. If the agents need something only you know later on, they ask in **Needs you**.

**3. What the assistants say today**

The agents ask the assistants about fifty questions your buyers ask, and show each question on the [Scoreboard](https://docs.attensira.com/tracking/scoreboard.md)'s scale:

| Colour | Label | Means |
| - | - | - |
| green | Recommended with a link | named, and your site linked |
| amber | Mentioned | named, with no link to your site |
| red | Not mentioned | not named |
| none | Not checked yet | no assistant has answered yet |

On screen, each question shows its label and a symbol, so colour is never the only signal.

The preview colours each question exactly as the Scoreboard does. On each assistant, the question takes the colour of its latest answers: green when you are named in at least half of them and your site is cited in at least half, amber when you are named in at least half, and red otherwise. The question's own colour follows the [prompt state](https://docs.attensira.com/measure/prompt-state.md) rule across the assistants that answered, as on the Scoreboard. So the number of green questions you see here is the number the Scoreboard shows for the same answers.

A question no assistant has answered yet has no colour and is never counted as red. While questions are still out, the step says how many have been checked, and it keeps updating after you continue. If the first scan finishes with no question to ask, the step shows **0 questions checked**, and your questions are checked once your plan starts.

**4. Where changes go**

Choose where your changes are published, from the destinations listed. The list comes from the server, so it shows only destinations offered today: GitHub, Webflow, WordPress, Shopify, Notion and hosted answer pages. Choosing a site opens its sign-in in a new tab. The step checks every few seconds whether you finished, and **Check again** asks right away.

**Hosted answer pages** are for a workspace with no repository or CMS to connect. There is nothing to sign in to: choosing it gives your workspace its own site on a subdomain we host, named after your brand, and the step is done at once. Choosing it again keeps the same site. When the agents write you a new page and it is approved, it goes live on that site, unless the repository or CMS it was written for is connected and working. Changes to the pages of your own site never go there. Copy and paste is not a destination: anything nothing can publish for you is already handed to you to paste.

If the sign-in fails, is left unfinished, or the connection does not work, the step says why and offers **Connect again** for a fresh link. Nothing is published through the connection until your first payment, even if our billing provider is briefly unreachable: a change approved before then stays approved and goes out on the first check after your plan is confirmed. Once you have paid, publishing carries on through a billing outage.

Connecting is not required to continue. **Connect later** goes on to the plan. A change that needs your site connected asks you to connect it when it is ready to publish. Your first change does not wait on a connection: today it is a passage you paste onto the page yourself (see below).

A connection made before you pay is kept for 14 days. If no plan has been paid 14 days after you connected, we revoke the connection, delete it, and send you one email saying so. The step then shows that the site was disconnected, with **Connect again**. Connect it again when you are ready to pay. This only applies to accounts that have never paid.

**5. Your plan**

Choose a plan and a monthly budget, then pay in checkout. This is the same plan step as on `/start`. When the plan is active, the agents start the first work and checkout returns you to the handover. On the Starter trial the first work is drafted during the trial, from its 3,000 credits, and nothing ships without your yes ([The trial](https://docs.attensira.com/account/plans.md#the-trial)). If your plan is already active, `/setup` sends you to [Today](https://docs.attensira.com/agent/today.md).

## Arriving from the free audit

A link from a free audit carries the audit: either its domain and its questions, or a short reference to it, from which setup reads back the audit's domain, its questions and the competitors it named. A reference works on another device, or after a mail app opened the link. A link from a head-to-head also carries the second domain. If the audit a reference names cannot be read, setup uses whatever else the link carries, and with nothing usable it asks for your website as usual.

From such a link, `/setup` (and `/start`) skip what the audit answered:

* **Your website.** The workspace is created for the audit's domain without asking.
* **Your questions.** The audit's questions join your starter set word for word.
* **Your competitors.** The competitors the audit named, with a head-to-head's second domain first, are tracked on the new workspace, as if you had kept them yourself. Your own domain and its subdomains are never among them. If they cannot be tracked (for example, one is part of your brand family), none are, and competitors are proposed as usual.

On `/setup`, when the link carried the audit's questions, the **Where changes go** step is skipped on the way to the plan, as **Connect later** would, so setup takes four steps: your Brand Book, your questions, what the assistants say today, and your plan. The preview, with your first change, is never skipped. A change that needs your site connected asks you to connect it when it is ready to publish.

Only the workspace for the audit's own domain gets any of this. A workspace for a domain you typed yourself starts with nothing from the audit.

## Your first change

Once the scan has answered a question you are not named in, the agents draft your first change before you pay. They pick the question the most assistants answered without you, then rewrite one passage on your own site to answer it. The passage is checked against the page as it is published today, and the draft is checked against your rules like any other. We pay for this draft: each workspace gets at most two tries, and if both come back with nothing usable, your first change is drafted after payment with the rest of your first work.

We draft one first change before payment per site, not per account. A site here means the registrable domain, so `www.example.com`, `blog.example.com` and `example.com` count as one. If another workspace already had the first change for your site, nothing is drafted before you pay, and your first change is drafted after payment with the rest of your first work.

The draft is a proposal in your Inbox. Nothing is published before your plan starts. You can:

* **Accept it before paying.** Your yes is kept for the version you saw, and that version is approved the moment your plan starts, in your name. When your assistant accepts it for you, it is approved as your assistant once you pay, and held to every rule an assistant's approval is. If the draft changed after the yes, or a rule holds it for a person, it goes to the veto window instead.
* **Leave it.** When your plan starts, it waits in your Inbox for your yes, like every change at the default [level](https://docs.attensira.com/agent/approval.md#autonomy-levels). Nothing ships without your yes, unless you raised your own site to **Ship after 48 hours unless stopped** before paying.
* **Decline it.** It stays declined after you pay.

When your plan starts, the lanes you have not set stay at **Draft and wait for a yes**, your own site included. Paying never raises a lane; a lane you set is left as you set it.

A day after payment we check that your first change is live. A change still in its veto window is checked again a day after the window ends. A passage rewrite cannot yet be published to your site for us, so today your first change ends with one row in **Needs you**: paste the new words onto the page and mark it live. This is the same when you chose hosted answer pages: the first change rewrites a passage on your own site, and only new pages go live on your hosted site. For a change we can publish, we publish it again first. If it is still not live, **Needs you** gets one row with the one step only you can take: reconnect your site when its connection stopped working, or look at the change again when your page changed since the draft. An updated change is never approved for you.

## Over MCP and the API

Your assistant can run the same setup with `start_workspace` and `confirm_setup`, and choose a destination with `configure` (`kind: "destination"`, `op: "update"`, `change: {"workspace_id": …, "destination": "hosted"}`) or `PUT /v1/onboarding/workspace/{id}/destination`. Choosing works before payment on both. For hosted answer pages the answer has `state: "done"` and the site's `host`; for a site it has the sign-in link (`connect_url`, which `configure` returns as `confirm_url`). `get` on `attensira://{workspace}/destination` reads the choice back. `start_workspace` returns the first change as `first_change`, and `act` with `approve` on its `uri` before payment accepts it: the answer is `pre_approved: true`, and nothing is approved until the plan is paid. See [the MCP tools](https://docs.attensira.com/mcp/tools.md). `start_workspace` lists the offered destinations as `connect_options`. The dashboard's own destination read, `GET /v1/projects/{id}/onboarding/destination`, returns the same list as `options`.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.