# Get started with your AI agent

Your agent can read Attriboo's guides, help install your tracking script, and read reports after you approve a connection. You complete sign-in and provider approvals. Website setup still uses the Attriboo dashboard.

Canonical page: https://www.attriboo.com/agents

Instructions reviewed: 2026-10-30

## Start with one website and one question

1. **Give your agent the setup prompt.** Replace the website placeholder with your address. Tell it which project or website editor it may access.

2. **Sign in and approve the connection.** Start the MCP connection from a compatible app. Attriboo opens sign-in or account creation, then asks you to approve read-only access to a workspace. The exact browser or popup behavior depends on the app.

3. **Add your website and install its script.** If list_sites does not include your website, add it in the dashboard. Copy its script from Setup. Your agent can prepare the website edit if it has access to your project. Publish or deploy that change before checking it.

4. **Check the visit, then connect payments.** Open your published website, then use Setup → Test Connection in Attriboo. Connect a supported payment provider with your own approval. Ask your agent to separate verified steps from anything still waiting.

## What agents can do today

| Task | Available path |
| --- | --- |
| Read setup guides before signing in | Public HTML and Markdown guides; no account required |
| Connect to private reports | Remote MCP with OAuth and your approval, or the authenticated REST API |
| List websites and read reports | Existing MCP tools such as list_sites and get_overview |
| Add a website or get its script | You use the dashboard; current MCP tools cannot perform these tasks |
| Edit your website | Your agent needs separate access to your project or CMS; connecting Attriboo does not grant that access |
| Use an official Attriboo CLI | Planned; no official package or install command is provided yet |

## Connect using the supported authentication flow

MCP server URL: https://www.attriboo.com/api/mcp. Choose OAuth in an app that supports remote MCP sign-in. Start in that app so it can create the authorization request and resume after approval. Opening a bare authorization URL is not a complete connection.

The current permission is analytics:read. It reads the selected workspace's reports; it cannot add websites, change settings or record payments. You can disconnect connected apps in Settings → API & MCP.

Sign-in uses an email link or code and can create a new account. The account holder completes verification and any required acceptance. The documentation does not provide an anonymous account-creation API, a device-code login endpoint or unattended signup.

An agent without OAuth support can use an existing workspace key only when you deliberately configure it in that agent's private environment. A workspace key has broader capabilities than the read-only OAuth connection. Never include it in a public prompt, tracking script or browser code.

- [Connect an AI assistant through MCP](https://www.attriboo.com/docs/mcp)
- [Read the REST API guide](https://www.attriboo.com/docs/api)

## Verify the setup before reporting success

- Check the real website and workspace. Public example reports are not the customer's analytics.
- Check for an existing script, plugin or tag-manager installation to avoid adding another loader.
- Use the platform-specific guide. A code change in a project is not a published installation.
- Confirm a recorded visit on the intended site. A waiting connection or empty report is a pending result, not a successful check.
- Connect visits and payments separately. An imported payment does not reconstruct an earlier unrecorded visit.
- When reading reports, state the website, dates, currency and attribution model. Money in the API is in cents; a crawl is not a citation or a human visit.

- [Choose your platform's installation guide](https://www.attriboo.com/docs/installation)
- [Check your first recorded visit](https://www.attriboo.com/docs/check-first-visit)
- [Connect your payment provider](https://www.attriboo.com/docs/payment-connections)

## You are done when

You know which steps are complete, which are waiting for approval or publication, and whether Attriboo has received a visit from the correct website.

## Related guides

- [Connect your AI assistant with MCP](https://www.attriboo.com/docs/markdown/mcp.md)
- [Read Attriboo reports through the API](https://www.attriboo.com/docs/markdown/api.md)
- [Install Attriboo on your website](https://www.attriboo.com/docs/markdown/installation.md)
- [Check your first website visit](https://www.attriboo.com/docs/markdown/check-first-visit.md)

## Starter prompt

```text
Help me set up Attriboo for [YOUR WEBSITE URL].

Read https://www.attriboo.com/agents/README.md first. Use https://www.attriboo.com/llms.txt to find official guides and https://www.attriboo.com/docs/markdown for their public Markdown versions.

1. Identify my CMS or framework from the project or ask me. Read the matching installation guide. Check for an existing Attriboo script before adding anything.
2. If your app supports remote MCP with OAuth, connect to https://www.attriboo.com/api/mcp. Let me complete sign-in or account creation and approve access in the browser. Do not ask me to paste passwords, email codes or private workspace keys into this conversation.
3. After connection, call list_sites. If my website is missing, guide me to add it in Attriboo. The current MCP tools cannot add websites or retrieve my tracking snippet. Ask me to copy the site-specific script from Setup when needed; never invent a website ID.
4. If you can edit my website project, prepare the correct installation using that script and the platform guide. Keep one tracker installation. Follow my deployment instructions, and tell me if a publish or deployment step is still pending.
5. Help me check the published site and Attriboo's Setup > Test Connection. Use authorized reports when available to check for recorded activity. A script in the source alone does not prove that a visit was received. Report waiting or failed checks honestly.
6. Help me choose a supported payment connection. Let me sign in to the provider and approve its access myself. Do not create charges or promise that historic sales will have matching visits.
7. Finish with a short checklist: website, installation location, published status, tracking verification, payment connection and next action. If there is recorded activity, offer one useful revenue question to ask next.

The official Attriboo CLI and agent tools that change setup are planned. Do not invent CLI commands, create accounts silently, bypass consent or treat example reports as my real results.
```

## Machine-readable resources

- Help index: https://www.attriboo.com/docs/markdown
- Discovery index: https://www.attriboo.com/llms.txt
- Read-only reports: https://www.attriboo.com/openapi.json