Trust3 Ai Authentication

generated: '2026-07-21'
method: searched
source: https://docs.trust3ai.com/how-to-guides/mcp-configuration.html
docs: https://docs.trust3ai.com/how-to-guides/mcp-configuration.html
summary:
  types:
  - apiKey
  api_key_in:
  - header
  sso:
  - SAML 2.0
schemes:
- name: Trust3 scoped API key (MCP)
  type: apiKey
  in: header
  parameter: x-trust3ai-key
  description: >-
    Scoped API keys are generated in the Trust3 console (Settings -> API Keys
    -> Generate scoped key) with a name, optional description, expiry (7/30/90
    days, 1 year, or custom), and a scope. The MCP (read) scope grants
    read-only access to governance context through the hosted MCP server.
    Keys are shown once at creation.
  docs: https://docs.trust3ai.com/how-to-guides/mcp-configuration.html
- name: Trust3 API key (AI Assets Collector)
  type: apiKey
  in: header
  parameter: AI_GOVERNANCE_API_KEY (collector configuration)
  description: >-
    AI Assets Collectors running in the customer data plane authenticate every
    request to the Trust3 API server (the public AI Governance API edge) with a
    Trust3 API key configured as AI_GOVERNANCE_API_KEY. The API server
    validates the key and routes allowed calls to Trust3 backend services.
  docs: https://docs.trust3ai.com/platform-concepts/control-data-plane.html
- name: Console SSO (SAML)
  type: sso
  protocol: SAML 2.0
  description: >-
    User access to the Trust3 console supports SAML single sign-on with
    documented setups for Azure AD, Okta, OneLogin, Ping Identity, and other
    SAML identity providers.
  docs: https://docs.trust3ai.com/get-started/user-management/sso/
notes: >-
  No public OAuth 2.0 / OpenID Connect surface is documented for programmatic
  API access; the docs site's generic REST API reference page is marked as a
  placeholder by the provider, so only the API-key and SSO mechanisms
  documented on real pages are recorded here.