Knowledge Base

Working with Saidot APIs

Saidot provides programmatic access to your governance data via two methods: API tokens and service accounts for direct REST API access, and OAuth 2.1 via Connected Apps for MCP Connector access. This page covers both. You can access the latest REST API documentation here: Saidot API Swagger Documentation. We're continuously rolling out new APIs; please follow our Release notes for the latest updates.

Creating and managing API tokens

API tokens can be created by your organisation’s Admins in the Admin interface. Navigate to the ‘API tokens’ section of the Organisation page to get started. There, Admins can see and remove all their organisation’s tokens. Members can also add and update their personal API Tokens in their Account Settings.

image-20260315-074159.png

API tokens are created by clicking the ‘Create token’ button. You will be asked to provide the name, expiration time and access (read-only or full access) for your token. After providing the needed information, click ‘Create’ button to access the API key. Please note that it is important that you copy your API token and store it in a secure location, as you won’t be able to view it again after closing the step. The API tokens can be managed and deleted after creation.

Screenshot 2026-11-16 at 17.16.52.png
Create and manage API tokens - Admin settings

Admins can set a default expiration period in number of days under the API tokens section of the Admin settings' Organisation page. This enforces a validity period for all created tokens.

Screenshot 2026-11-16 at 17.18.06.png
Enforcing expiration periods for API tokens - Admin settings

Service accounts

A service account belongs to the organisation rather than to a person. They can be used for pipelines and integrations that need to keep working outside work hours and regardless of personnel changes. Service accounts can be revoked just like API tokens or Connected apps.

Screenshot 2026-11-16 at 17.13.09.png
Creating a service account - Admin settings


Service accounts are created by Admins under Service accounts in the Admin settings. When creating a service account, give it a descriptive name to ensure traceability in the Audit log. They authenticate with OAuth 2.0 client credentials: the integration obtains its tokens from Saidot with a client ID and secret and sends them as bearer tokens. Store its client ID and secret in the secret store of the integration that uses it.

Service accounts have Admin reach across the organisation, limited by the read or write scope of their credentials. To check which user or service account is behind a token, call GET /api/v1/introspection. It returns the account, its access role and the token’s permission scope.

Connected apps

Administrations can review and block approved connected applications in Connected apps. This page also displays all active user grants. Admins can Revoke these user grants centrally.

image-20260315-074654.png

OAuth apps can be registered in Admin view by giving the App name, client type, Redirect URLs, and the Scope, including identity verification, profile name, email, ability to have offline address and the read and/or write permissions shared.

Screenshot 2026-11-16 at 17.20.36.png


MCP Connectors - Agentic AI Integration

MCP (Model Context Protocol) Connectors let you connect AI coding assistants and automation tools directly to Saidot. Building on the Saidot API, MCP enables agentic access for tools such as Claude Desktop, VS Code (GitHub Copilot), Microsoft Copilot Studio and the Saidot MCP CLI for use in CI/CD and automation pipelines.

Available MCP Servers

Saidot offers three specialised MCP servers depending on what your integration needs. Connect to whichever servers are relevant for your team's workflows.

MCP Server

Endpoint URL

Purpose

Governance MCP

mcp.saidot.ai/governance

AI inventory and catalogue management, including reading and managing your AI systems, risks, datasets, and models programmatically.

Library MCP

mcp.saidot.ai/library

Read access to Saidot's curated AI governance library, including risk cards, model cards, and policy content.

Docs MCP

docs.saidot.ai/mcp

Read access to Saidot's governance documentation and methodology directly from your AI tool.

After you have added Saidot MCP servers to your Connectors in your AI tool, Members can Authorise the AI tool. Please follow AI tool specific guidelines for Connecting to Saidot. When activating the Connector, the Saidot login window opens up and prompt the member to authorize Saidot. Authorization can be limited to Read-only and also Offline access can be limited.

image-20260315-075558.png

Authentication: OAuth 2.1 via Connected Apps

MCP connections are secured using OAuth 2.1 scoped token grants through Connected Apps. This gives you least-privilege control over what each integration can access, separate from API tokens, which are used for direct REST API access.

To configure authentication, navigate to OAuth Apps in your Admin settings and create a new Connected App for your MCP integration, selecting the appropriate scopes for the server(s) you are connecting to.

For the latest MCP updates, follow our Release notes.