SNT Counsel Developers
Build with Sentinel
Read a firm's matters, documents and search results over a REST API, or connect AI assistants through MCP. Both run as a Sentinel user, and see only what that user can see.
List your matters
curl https://yourfirm.api.sntlabs.io/api/v1/matters \
-H "Authorization: Bearer $SENTINEL_KEY"import httpx
r = httpx.get(
"https://yourfirm.api.sntlabs.io/api/v1/matters",
headers={"Authorization": f"Bearer {key}"},
)
matters = r.json()["data"]const r = await fetch("https://yourfirm.api.sntlabs.io/api/v1/matters", {
headers: { Authorization: `Bearer ${key}` },
});
const { data: matters } = await r.json();REST API
Plain HTTPS and JSON for your own code: list matters and documents, read text, and search.
MCP server
Connect Claude, ChatGPT, Copilot or Claude Code so lawyers work with their matters from the assistant.
Which one should I use?
| REST API | MCP server | |
|---|---|---|
| For | Scripts, integrations, litigation-support tools | AI assistants your lawyers already use |
| Endpoint | https://<your firm>.api.sntlabs.io/api/v1 |
https://<your firm>.api.sntlabs.io/mcp |
| Auth | API key | OAuth sign-in, or an API key |
| Can | Read matters and Library documents, search | Read, search, review, tag, code and record findings |
| Reference | API Reference | Available tools |
Each firm has its own Sentinel address. Copy yours from Your account → Connected apps, and use it wherever these docs show yourfirm.api.sntlabs.io.
Built for confidential work
The user's access, never moreEvery call is checked against matter assignments, room permissions and document fences, the same rules as the Sentinel app.On the recordSearches, document reads and MCP tool calls are written to the firm's audit log.Keys you controlCreate, expire and revoke keys in Connected apps. Admins see every key in the firm.Predictable limits120 requests a minute per key, with clear errors and Retry-After.