Google Cloud Model Armor vs Prisma AIRS AI Runtime Security API

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.

Prisma AIRS AI Runtime Security API

A public OpenAPI document, ten detection types in one call, tool-call scanning, a remote MCP server, rotating API keys and OAuth roles suit teams already on Strata Cloud Manager. Access needs Software NGFW credits bought through sales, with no public price, trial or self-serve signup, and payloads flagged malicious are kept for up to 10 years.

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

Prisma AIRS AI Runtime Security API

1. Send x-pan-token and an ai_profile with profile_name or profile_id on every scan. Both come from Strata Cloud Manager, and a key works only in its own region
2. Put earlier turns first in contents. Only the last element is scanned, and the rest is context
3. Read action (allow or block) and category, then check timeout and error, because a detector that failed is reported in errors with a 200
4. Keep synchronous requests under 2 MB and asynchronous ones under 5 MB and 25 items, and fetch at most 5 scan or report IDs a call, 10 calls a minute
5. For MCP, connect to /mcp on the regional host with x-pan-token and x-pan-profile headers, and call pan_inline_scan yourself before and after generation