Developers: API and MCP server
Sentinel opens up to your tools in two ways: a REST API for your scripts and applications, and an MCP server for AI assistants (Claude, ChatGPT, Copilot Studio, your own agents).
Three uses
- Feed your tools. Pull a watch’s analysed articles and alerts into your CRM, intranet or dashboard, through the API or a signed webhook.
- Query your watches from an assistant. Ask Claude or ChatGPT what your watches saw this week, or draft a client update from a note, citing the source articles.
- Manage watches from an agent. Create a watch, adjust its keywords or add sources from an agent, with write access granted explicitly.
Getting access
- The API and the MCP server are included in the workspace’s Firm and Enterprise plans.
- API: create a key in Sentinel, account menu, “API keys & extension”, then send it as Authorization: Bearer.
- AI assistants: in Sentinel, account menu, “AI assistants”; the assistant connects through OAuth, no key to copy, and you choose the workspace it sees.
Limits
- Firm: 120 requests per minute, 100,000 calls per month.
- Enterprise: 600 requests per minute, no monthly cap.
- Read-only by default; creating and changing watches requires write access.
Isolation and traceability
Each key or connection is confined to one workspace: it never sees another client’s watches. Every call is logged, and changes appear in the workspace audit log.