Cisco AI Defense Inspection API vs Mistral Moderation API

Cisco AI Defense Inspection API

Per-connection API keys with expiry, revocation and regeneration, published limits of 60,000 calls a minute, weekly dated release notes and a one-year retention statement suit companies already on Cisco Security Cloud Control. Access needs a subscription bought through sales, with no public price or trial for the API, and the developer changelog has one entry from February 2025.

Mistral Moderation API

Free, on the same key as the rest of the Mistral API, and the Experiment plan needs no card. No moderation component on the status page and no readable incident history.

Cisco AI Defense Inspection API

1. Send the key in X-Cisco-AI-Defense-API-Key to POST /api/v1/inspect/chat on the regional host where the tenant was created. US, Europe and Asia Pacific hosts differ
2. If the connection has a policy, enabled_rules in the request is ignored. Pass enabled_rules only for connections with no policy
3. The API never blocks anything itself. Read is_safe and action in the response and enforce the decision in your own code
4. On 429, wait and retry. The organisation has gone over one million tokens in parallel or 60,000 calls a minute
5. Don't request the Toxicity rule. It was removed on 16 September 2026, and the Safety rules such as Hate Speech, Harassment and Profanity replace it

Mistral Moderation API

1. Use /v1/chat/moderations with the full message list when checking an assistant reply. The raw endpoint has no context
2. Read category_scores and set your own threshold per category. The booleans use Mistral's cut-offs
3. Pin mistral-moderation-2603. The 2411 model was retired on 31 March 2026
4. Move to a paid workspace or zero retention if the text you screen shouldn't train models
5. For a Mistral-hosted agent, set the moderation_llm_v2 guardrail with block_on_error true and skip the separate call