What TrustLens discovers
Agents
Models
Files and document libraries
Usage metrics
TrustLens collects per-agent usage via the Mistral Conversations API (beta):Token usage (input and output token counts) is not currently available via the Mistral API and will not appear in TrustLens.
Required access
Mistral uses API key authentication — no IAM roles or service principals are needed.Beta API access
Several Mistral API endpoints used by TrustLens are in beta and require your workspace to have beta access enabled:
If beta API access is not enabled:
- Agent discovery will return zero agents
- Usage metrics will be unavailable
- Document library discovery will be skipped
- Models and files will still be discovered
Step-by-step setup
1
Create an API key
- Log in to admin.mistral.ai
- Go to Organization → API Keys
- Click Create new key
- Set a name (e.g.,
neuraltrust-trustlens) and expiry, then click Create - Copy the key value and store it securely — it is only shown once
2
Configure the integration in TrustLens
Provide the following when creating the Mistral integration:
No additional configuration is required. TrustLens automatically discovers all agents, models, files, and libraries accessible to the key.
Guardrails discovery
TrustLens discovers the native guardrails policies configured on each Mistral agent via the Mistral Agents API. When an agent has guardrails attached, the full policy object is stored and surfaced in the UI.What is discovered
Mistral guardrails are stored per-agent under theguardrails object with the following shape:
Each entry in
policies is the raw guardrails object returned by the Mistral Agents API. Fields vary by policy type but the moderation_llm_v2 (v2) format includes:
Category keys in
custom_category_thresholds (v2 taxonomy):
Example
guardrails object for a Mistral agent:
Agents without guardrails
If an agent has no guardrails configured in the Mistral API, theguardrails field will be null. TrustLens surfaces this as a missing guardrails finding so you can identify agents running without content safety policies.
Feature availability
Known limitations
Security considerations
- The API key has access to all resources in your Mistral organisation. TrustLens uses it in a read-only pattern, but the key itself is not scoped to read-only by the Mistral platform.
- Rotate the API key regularly and update the integration in TrustLens when you do.
- TrustLens encrypts the API key at rest.
- If the key is compromised, revoke it immediately in the Mistral Console and create a new one.
Troubleshooting
No agents discovered
No agents discovered
- Verify your workspace has beta API access enabled. Contact Mistral support if not.
- Verify the API key is valid and not expired — go to admin.mistral.ai and confirm the key is listed.
- Verify agents exist in your workspace by checking the Mistral Console.
Agents showing null or missing guardrails
Agents showing null or missing guardrails
- The agent was created in Mistral without any guardrails policy attached. TrustLens reads and surfaces whatever is configured in the Mistral API — if none,
guardrailsisnull. - To add guardrails, update the agent in the Mistral Console or via
PATCH /v1/agents/{agent_id}to attach amoderation_llm_v2policy. - After adding guardrails, trigger a manual sync from the TrustLens integration settings page to pick up the new configuration immediately.
Document libraries not appearing
Document libraries not appearing
- Beta API access is required for the Libraries API.
- Verify at least one document library exists in your workspace.