Integrations overview
Connect search evidence, delivery systems, developer clients, assistants, and reporting tools.
Integrations extend Sight with first-party search evidence, event delivery, complete API automation, assistant access, typed clients, and reporting exports. Each integration has a different availability and trust model. Google Search Console uses project-level authorization, while public platform contracts use organization-scoped bearer keys.
Deployment-level model routing is an internal service configuration and should not be presented as a customer-managed provider connection. Capabilities that are missing or partial are listed explicitly below so product packaging, sales language, and technical documentation stay aligned with the current implementation.
Integration setup should include an owner and a maintenance plan. OAuth connections can lose access, webhook endpoints can fail, API keys can be exposed or revoked, and external schemas can change. Record who controls each connection, how failures are detected, which data is expected, and how to disable or rotate credentials without interrupting unrelated projects.
| Integration | Availability | Purpose |
|---|---|---|
| Google Search Console | Implemented | Queries, pages, clicks, impressions, CTR, and average position |
| Signed webhooks | Starter and Pro | Send scan, report, and test events to an HTTPS endpoint |
| REST API v1 and OpenAPI 3.1 | Pro | Automate projects, evidence, reports, alerts, credits, crawl insights, webhooks, and exports |
| API keys | Pro creation | Create named bearer keys, list prefixes, and revoke keys |
| OpenRouter or DeepSeek routing | Server configured | Run Sight's internal LLM workloads through the deployment's configured provider |
| MCP server | Implemented | Give compatible assistants read-only access to organization-scoped project evidence |
| TypeScript SDK and CLI | Implemented | Build typed integrations or operate the API from a terminal |
| Customer model-provider connection | Not implemented | Planned bring-your-own-provider or bring-your-own-key workflow |
| Bulk exports and Looker Studio | Implemented | Create CSV or JSONL datasets for recurring reporting and warehouses |
Provider status is not a customer connection
The Integrations endpoint can report which model provider the deployment uses. Customers cannot currently connect their own OpenAI, Anthropic, Google, or OpenRouter accounts in the product.
Do not expose deployment credentials or imply that customers control provider routing. A true customer connection requires a supported setup flow, scoped secret storage, usage ownership, and clear failure behavior.