Reference
All the detail: what ClaraT can reach, how your key works, what ClaraT saves and who sees it, what "write access" means, when something changes, and what it does not do. ClaraT is both the connector you add to Claude and the assistant you then talk to. For the connection and your first asks, getting started.
What ClaraT can reach
ClaraT gives Claude a small set of tools, each a door onto something SearchLight already runs. You never call these yourself; ClaraT does, as you.
| Tool | What it reaches |
|---|---|
The knowledge base (kb_index, kb_read, one kb_<category> door per category) | SearchLight's organizational memory, organized in categories: attribution, the data dictionary, performance consulting, the SearchLight API and app, partner systems (ServiceTitan, other CRMs, call trackers, ad platforms), RevSync, billing, and more. ClaraT reads it before answering anything about SearchLight. What you see is its public part, plus what is yours or your organization's. |
kb_save, kb_capture, kb_suggest_doc_edit | Saving what a conversation taught, at the right scope; proposing a correction to SearchLight's documentation. |
searchlight_api | The SearchLight API as you: what you can reach (organizations, accounts, the field dictionary), benchmarks, insights. |
searchlight_events | Your events (spend, leads, revenue, grading, every documented dimension and metric) for an organization and a date range. |
searchlight_accounts | The account rows you reach, with the configuration you ask for (providers, fees, lead grading, CRMs). |
searchlight_middleware | SearchLight's user-gated services as you: accounts, groups, connections, connection checks, your cached data, and the platform proxies (Google, Microsoft, Facebook, ServiceTitan, FieldRoutes), which pass only non-modifying calls: reads, searches and reports. A change to your SearchLight configuration is confirmed with you first. |
Your token: how ClaraT authenticates
When you connect, SearchLight issues your Claude a key tied to your user account, the same key the app shows under Settings → API, where you can generate, rotate, rename and delete keys. One key serves the API, ClaraT and the platform alike. Rotating or deleting it in the app revokes the old key immediately and disconnects every copy; the connector then asks you to sign in again.
That key is yours to use outside ClaraT too:
- The SearchLight API is documented at the API overview: what you can reach, events, dimensions, metrics, filtering, benchmarks and insights. Send the key raw in the
Authorizationheader (noBearerprefix). A key reaches exactly what its owner reaches in the app, and its reach changes when your access changes. Requests are rate-limited per user per hour, as the API docs say. - The middleware layer, for advanced users only. The same key works on the user-gated services ClaraT itself calls: account and group configuration, connections and their checks, the cache directory, the platform proxies. This is real work with your own rights. The platform does exactly what your permissions allow, including changes to your SearchLight configuration. The provider proxies are different: they pass only non-modifying calls (a GET, or a POST the proxy lists as a read, such as a search or a report), and a call that would change anything at Google, Microsoft, Facebook, ServiceTitan or FieldRoutes answers
403with the bodyonly non-modifying calls are allowed through the proxy to regular users. Rely on ClaraT to connect you to it: ask it which endpoint answers your question, what the parameters are, and to make the call and read back the result. ClaraT confirms every change with you in words before sending it, and the knowledge base's middleware section carries the endpoint map and the rules. A403carrying that body is this rule; a bare403on a proxy path means the account named is not in your reach. A401means the key is no longer accepted: reconnect.
What ClaraT saves, and who sees it
The knowledge base is the memory ClaraT reads first and writes to last. It is organized as a tree of categories and skills (how SearchLight works, what every number means, how to do things), and it is open to every connected person at the level that fits them. Nothing else is kept: your questions, your answers and your numbers are not stored by ClaraT, and the data behind an answer stays in SearchLight.
- What a saved lesson is. A method, a definition, a gotcha, a way to do something: "how to tell a call-tracking gap from a CRM gap", "what this report's revenue column counts". It is never a record of your business: account names, keys, email addresses, phone numbers and the other particulars of an account or a person stay out of a lesson, which points at where they live instead.
- Three scopes. ClaraT saves a lesson as widely as it safely can: everyone (every connected person), your organization, or you alone. A lesson that holds something specific to your business lands at your organization's scope or yours; a general one lands for everyone. A lesson you save is signed with your email, visible to those who can see it.
- Who "your organization" is. Your SearchLight organization: the one your login is granted and your accounts sit under. A lesson at that scope is readable by every SearchLight login granted that organization and by no one outside it. If one organization holds several clients' accounts, every login granted that organization reads its lessons, which is why a lesson holds method and never a client's particulars; what is about one client alone is saved to you, or not at all.
- Seeing and correcting it. Ask ClaraT what it has saved for you or your organization; it reads the same lessons it writes. A lesson that is wrong is corrected in the conversation: ask ClaraT to rewrite it. To have one removed, contact support.
- Gated public saves. A save that could be an injection, or that holds what a public entry may not, is refused and queued for an administrator's review instead of landing. A first public save from someone new lands but is marked for a check.
- Protected categories. SearchLight's key ingredients (the data architecture, the accuracy layer, the access model, the knowledge base's own mechanics) are visible to everyone by name and description only; what sits beneath them is SearchLight's.
- No personal data in the tree. Account names, keys, email addresses and phone numbers never go into a saved lesson; the lesson points at where they live instead.
- Use a capable model. A save from a non-administrator needs Claude Opus or higher to land; on a smaller model ClaraT records the lesson as an observation for a person to pick up.
Changes through ClaraT: what "write access" means
ClaraT can change things in SearchLight: an account's configuration, a group, a connection. It cannot change anything at your providers (below). Read that as "can, with your rights, once you allow it and say yes", not as "will". In full:
- Nothing changes until you allow the write tools. The tools that can write arrive Blocked under the connector's Tool permissions, Claude's default. Leave them there and ClaraT answers questions and changes nothing. Needs approval is the cautious setting once you do want changes: Claude shows you each call and sends it only when you approve.
- Only what you could do in the app. Every call runs with your SearchLight permissions and the platform decides. A change to an account's or a group's configuration needs the manage-accounts permission on your user; without it the platform refuses the change, whatever ClaraT sends.
- ClaraT confirms every change with you in words (what will change, on which records, through which door) and sends only on your yes. A tool permission set to Always allow is not a yes.
- Nothing changes at a provider. SearchLight's provider proxies pass only non-modifying calls: ClaraT can read campaign settings, budgets, ads, a ServiceTitan job or a FieldRoutes appointment on your own connection, and never alters them. A call that would change anything at Google, Microsoft, Facebook, ServiceTitan or FieldRoutes is refused by the platform with "only non-modifying calls are allowed through the proxy", whatever the tool permission and whatever you say yes to. A change at a provider is made in that platform's own console.
- Every change is recorded as yours. A record changed through ClaraT carries your user and the time, the same as a change made in the app.
- When the app has a page for the change, ClaraT says so; the connector is for what a conversation makes faster or possible.
When something changes
- The tools changed (a release added or changed one): on the connector's page, ⋮ beside Disconnect → Refresh tools list, check the write tools' permissions again, start a new chat.
- Every call answers 401: the key on the connection is no longer accepted, usually rotated or revoked in the app. Disconnect, then Connect (the sign-in runs again), and start a fresh chat.
- Never toggle the connector during a running session. Open a new session instead.
What ClaraT does not do
- It does not see past your access. No account, organization or number you cannot open in the app. An administrator at SearchLight sees more because the app shows an administrator more.
- It does not keep your data. No copy of your numbers, no memory of a chat beyond what Claude itself keeps, nothing but the lessons described above.
- It does not change anything on its own. Nothing until you allow the write tools, and then nothing without your yes in the conversation.
- It does not change anything at your providers. Google, Microsoft, Facebook, ServiceTitan and FieldRoutes are read through SearchLight's proxies, never written: a modifying call is refused by the platform.
- It does not guarantee the reading. The numbers are the platform's; the explanation is ClaraT's analysis, and a number that matters is checked by asking how it was got.
- It does not replace the app. Reports, dashboards and the pages that manage users and connections stay in the app; ClaraT points you there when that is the better tool.
- It does not run outside Claude. ClaraT connects to claude.ai, the Claude desktop app, Claude Code and, once added on the web, the Claude mobile apps.
- It does not show keys or tokens, yours or a provider's, in any answer.
Limits worth knowing
- The platform answers each call within 25 seconds; a bigger ask is narrowed (a shorter range, fewer fields, one organization).
- Calls to the SearchLight API are rate-limited per user per hour, as the API docs say; a window over 90 days is read by month, week or day.
- Rates (book rate, ROAS) come back as decimals and are never summed across groups; counts and revenue are not additive across time buckets.