Point your agent here.

1. 01

   Track

   The questions your buyers ask AI engines, answered on a schedule and kept in full: who was named, who was recommended, which pages were cited.

2. 02

   Find

   Every page those answers cite becomes one opportunity across every answer and engine, with a 0 to 100 priority that orders the queue.

3. 03

   Decide

   An AI review sorts each page by type and suggests how to act. You approve, reject, park or promote it.

4. 04

   Pitch

   Contacts are researched and a pitch is drafted. It goes out from your own mailbox as a sequence, only after you approve it, inside your send window.

5. 05

   Report

   Mentions, citations, share of voice and verified wins, before and after the work. Movement after a placement is reported as association, never as cause.

51,000+ AI answers on the record across every brand tracked, and counting.Read the full explanation

1. 01Pitches go out from your own mailbox, and you see which ones were followed by movement in AI answers.

   Outreach is a sequence sent from the mailbox you connect (Gmail or Google Workspace, Outlook or Microsoft 365, or IMAP and SMTP), with your address and your sent folder, only after you approve it and inside your send window. Each pitched page is measured before and after in the answers you track, and each verified placement is shown with the answers that cited it since. Both halves live in one account, and every read is association, never cause.

   Impact and outcomes
2. 02Tracking ends in a next action: the cited page, its priority, the people behind it and a drafted pitch.

   Every page the tracked answers cite becomes one opportunity with a 0 to 100 priority, and the app shows the reasons under “Why this score”. For the pages you pursue, contacts are researched and a pitch is drafted, and every draft waits for your review. New projects start with an auto-promotion rule on, so Autopilot finds a contact and drafts a pitch for high-priority pages.

   What an opportunity is
3. 03Your agent can act, not only read: 215 tools on one MCP endpoint.

   65 of them answer at once. The other 150 prepare work: each change waits as a card for the person to apply, unless their setting in Settings, Agents applies that kind of change at once.

   Change cards: apply and undo
4. 04Your agent works as the person who made its token, with only the scopes and projects they allow, on every plan.

   Only a person can make a token, in Settings, Agents. It holds the scopes they check and the projects they pick, fixed for its life, and both are checked again on every request. The agent reaches what that person can open, inside the plan’s limits, and an agency can give each client’s agent a token that reaches only that client.

   Agent scopes and limits
5. 05Some things no agent can do here, whatever it is granted.

   Paying a publisher; billing, plans and purchases; publishing website pages, or deleting for good; members, invites, roles and connecting a mailbox; deleting a placement; changing how pages are scored, engine policy and admin. None of these is a tool the door serves, so no scope, mandate or setting reaches them.

   Agent scopes and limits
6. 06The autopilot works in the open: anything that commits you waits for your decision, and the engine room shows each run.

   It collects, scores, drafts and sends what you launched, then logs it. A send, a reply, a price or a post waits for you. The engine room shows the run in progress and your levers, and the pipeline page shows every step with its status and when it moves next.

   The engine room and pipeline
7. 07Your plan sets how much is tracked, not how much of it you see.

   Plans differ in brand/client projects, tracked prompts and AI engines per project. Opportunities discovered: unlimited on every plan, so every page those answers cite is yours to see and work.

   Plans and limits
8. 08Built to be safe for an agent to use.

   Words you didn’t write arrive fenced. Links come back absolute. Nothing here is destructive. A refusal is final. The limits are published: 120 calls per 60 seconds per token, 60 seconds per call.

   How the door answers
9. 09Documented for models: every docs article in markdown, an llms.txt index, and the same docs inside the MCP connection.

   Each article answers at its own address with .md appended, /llms.txt lists them all and /llms-full.txt carries every article in one file. A connected agent reads the same index as the resource sourcesignal://docs. The docs say what a person sees and can do, never how a verdict is computed.

   The docs for agents

• This page as markdown/agents.mdEverything on this page in one document, for a model to read end to end.
• Documentation index/llms.txtOne line per docs article, each with its markdown address.
• Every article in one file/llms-full.txtThe whole documentation in reading order.
• Documentation/docsHow to set up sourcesignal, track the questions buyers ask AI engines, work the opportunity queue, run outreach from your own inbox and report what changed.
• Docs inside the MCP connectionsourcesignal://docsThe same index and articles as resources, for an agent already connected.
• Pricing/pricingEvery plan, limit and feature, in USD, EUR and GBP.
• Free AI visibility report/free-reportA free read of how a brand shows up in AI answers.
• Research/research/100-days-of-ai-answersWhat AI answers reveal about mentions and sources.
• Backlinks are not mentions/research/backlinks-are-not-mentionsWhich brands AI engines name, measured against the pages they cite, the links on those pages and each brand’s domain authority.

The documentation describes what a customer sees and can do, never how a verdict is computed: how a page earns its priority, how a mention is read or how a page type is chosen is not published.