Cisco AI Defense Inspection API vs Google Cloud Model Armor

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.

Google Cloud Model Armor

2 million free tokens a month, then $0.10 per million. OAuth only, and a template must exist in the same location as the endpoint before the first call.

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

Google Cloud Model Armor

1. Create one template per location you call from. A template in us-central1 doesn't answer on the europe-west2 endpoint
2. Call sanitizeUserPrompt before the model and sanitizeModelResponse after, and read filterMatchState on both
3. Treat EXECUTION_SKIPPED as unchecked, not clean. It means the input went over the filter's 65,536-token cap
4. Pin the template to the Stable alias and move off v1 and v2 before 17 December 2026. In asia-northeast3, v1 stays the Stable version
5. Retry 500, 502, 503 and 504 with truncated exponential backoff, and keep fan-out under the 1,200 queries a minute shared by the project