Cisco AI Defense Inspection API vs Lakera Guard (Check Point AI Guardrails)

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.

Lakera Guard (Check Point AI Guardrails)

OpenAI message format in, including tools, tool calls and tool results. Prompts and outputs are stored for the dashboard by default.

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

Lakera Guard (Check Point AI Guardrails)

1. Start the project in Detect mode and calibrate before Enforce. In Detect mode flagged is always false
2. Send the whole conversation, but expect only the last user, assistant or tool turn to be scored
3. Ask for breakdown=true and treat the confidence levels as a dial, not a boolean
4. Turn off prompt logging in General Settings if the dashboard shouldn't hold user content
5. Pin eu.api.lakera.ai or us.api.lakera.ai rather than api.lakera.ai when residency matters