{ "data": { "similar": [ { "grade": "BB", "json": "https://www.anchorterminal.com/tools/google-model-armor.json", "name": "Google Cloud Model Armor", "score": 77.9, "shared": [ "guard.injection", "guard.pii", "guard.moderation", "guard.policy" ], "slug": "google-model-armor" }, { "grade": "BB", "json": "https://www.anchorterminal.com/tools/amazon-bedrock-guardrails.json", "name": "Amazon Bedrock Guardrails", "score": 74.8, "shared": [ "guard.injection", "guard.pii", "guard.moderation", "guard.policy" ], "slug": "amazon-bedrock-guardrails" }, { "grade": "B", "json": "https://www.anchorterminal.com/tools/openai-guardrails.json", "name": "OpenAI Guardrails", "score": 69.5, "shared": [ "guard.injection", "guard.pii", "guard.moderation", "guard.policy" ], "slug": "openai-guardrails" }, { "grade": "B", "json": "https://www.anchorterminal.com/tools/nemo-guardrails.json", "name": "NVIDIA NeMo Guardrails", "score": 68.4, "shared": [ "guard.injection", "guard.pii", "guard.moderation", "guard.policy" ], "slug": "nemo-guardrails" }, { "grade": "B", "json": "https://www.anchorterminal.com/tools/prisma-airs.json", "name": "Prisma AIRS AI Runtime Security API", "score": 62.8, "shared": [ "guard.injection", "guard.pii", "guard.moderation", "guard.policy" ], "slug": "prisma-airs" }, { "grade": "C", "json": "https://www.anchorterminal.com/tools/lakera-guard.json", "name": "Lakera Guard (Check Point AI Guardrails)", "score": 59.6, "shared": [ "guard.injection", "guard.pii", "guard.moderation", "guard.policy" ], "slug": "lakera-guard" } ], "tool": { "slug": "cisco-ai-defense-inspection", "name": "Cisco AI Defense Inspection API", "vendor": "Cisco Systems, Inc.", "vendorUrl": "https://www.cisco.com/site/us/en/products/security/ai-defense/index.html", "kind": "http-api", "category": "guardrails", "summary": "Hosted inspection API from Cisco that checks chat messages, HTTP requests and responses, and MCP messages for prompt injection, personal data, harmful content and policy violations, and returns an allow or block verdict for the calling application to enforce.", "url": "https://www.anchorterminal.com/tools/cisco-ai-defense-inspection", "markdownUrl": "https://www.anchorterminal.com/tools/cisco-ai-defense-inspection.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/cisco-ai-defense-inspection.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/cisco-ai-defense-inspection.json", "repo": "https://github.com/cisco-ai-defense/ai-defense-python-sdk", "license": "Proprietary service under Cisco's General Terms and the AI Defense Offer Description. The Python SDK is Apache-2.0", "transports": [ "http" ], "remoteUrl": "https://us.api.inspect.aidefense.security.cisco.com/api/v1/inspect/chat", "packages": [ { "registry": "pypi", "name": "cisco-aidefense-sdk" } ], "auth": "api-key", "authNotes": "Sales-led access. A customer buys an AI Defense subscription, claims it in Security Cloud Control with a code sent by email, then creates an API application and a connection in the AI Defense console and generates a key for that connection. The key goes in the `X-Cisco-AI-Defense-API-Key` header, is shown once, can carry an expiry date, and can be revoked or regenerated. It works only on the Inspection API. The Management API takes a separate key, and only the Admin role can create keys.", "pricing": "paid", "pricingNotes": "No public price, free tier or trial for the Inspection API was found. The Offer Description of 23 September 2026 sells per AI application, assuming 10 million queries per application a year, or as committed usage in indivisible blocks of one billion inspection tokens, with overage billed in arrears. The product page links a demo request. The free Explorer edition covers red teaming only (checked 2026-10-08).", "priceSummary": "Paid", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the developer docs, the user guide or the Offer Description (checked 2026-10-08).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": 35, "npmWeekly": null, "pypiWeekly": 3977, "asOf": "2026-10-08" }, "docsUrl": "https://developer.cisco.com/docs/ai-defense-inspection/", "capabilities": [ "guard.injection", "guard.pii", "guard.moderation", "guard.policy" ], "tags": [ "hosted", "enterprise", "sales-led", "closed-source", "api-key", "python", "status-page", "security-txt", "soc2", "eu" ], "lastRelease": "2026-09-23", "graded": true, "anchor": { "graded": true, "score": 61.3, "grade": "C", "agentReady": false, "rank": 429, "ranked": true, "rankOf": 842, "categoryRank": 8, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 67, "maintenance": 80, "payments": 0, "reliability": 80, "schema": 59, "security": 81, "transparency": 76 }, "pending": [ "performance", "tasks" ], "breakdown": [ { "key": "reliability", "name": "Reliability", "weight": 16, "effectiveWeight": 20, "score": 80, "points": 16, "reason": "Read with the hosted lines, for the Inspection API. status.security.cisco.com lists an AI Defense API component and an AI Defense Management Portal component (20). The history feed from 10 July to 8 October 2026 has four incidents, none naming the Inspection API. Security Cloud Control was down for 72 minutes on 23 September, sign-on was degraded on 7 and 18 August, and onboarding of new AI Defense tenants in ap-northeast-1 failed for 88 minutes on 22 July (20 of 30). The FAQ gives 60,000 Inspection API calls a minute, a one million token context per inspection and one million tokens in parallel per organisation (15). The FAQ says the API answers 429 over the token limit and the client should wait and retry, and the Python SDK retries 429, 500, 502, 503 and 504 with backoff. No Retry-After header is documented (10 of 15). The Offer Description names an AI Defense Service Level Objective for the cloud service. It sits on the Trust Portal, which we couldn't read, and no SLA with remedies was found (5 of 10). The API is v1.0.0 since 28 February 2025 with no beta label (10)." }, { "key": "performance", "name": "Performance", "weight": 10, "effectiveWeight": 0, "pending": true, "points": 0, "reason": "Pending. Latency is measured per call by our probes, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until the first probe window closes." }, { "key": "schema", "name": "Schema \u0026 documentation", "weight": 13, "effectiveWeight": 16.25, "score": 59, "points": 9.59, "reason": "The overview page links a downloadable OpenAPI document, version 1.0.0+2025.02.28. robots.txt on developer.cisco.com disallows `/*.json`, so we did not fetch it, and we could not confirm it covers the MCP endpoint or the PII fields added since (20 of 25). developer.cisco.com/llms.txt redirects to a 404 and no Markdown pages were found (0). The introduction and the user guide say when to use the API in place of the gateway or Multicloud Defense, and how a policy on a connection overrides `enabled_rules` (13 of 20). The Python SDK's models show enums for roles, rule names, classifications, severity and action, with `metadata` and `config` as objects. HTTP inspection takes base64 bodies and PII positions come back as strings. The reference pages are drawn by script and went unread (10 of 15). Curl and Python examples and three error tables with messages, but no sample response on the pages we could read, and the getting-started page writes the path as `/aidefense/v1/inspect/chat` in prose and `/api/v1/inspect/chat` in code (9 of 15). The path is versioned `/api/v1`. The API changelog has one entry, v1.0.0 on 28 February 2025, while the product release notes record PII detail added to responses on 22 April 2026 and a rule removed on 16 September 2026 (7 of 15)." }, { "key": "ergonomics", "name": "Agent ergonomics", "weight": 13, "effectiveWeight": 16.25, "score": 67, "points": 10.89, "reason": "A response is one object with `is_safe`, `action`, `classifications`, `severity`, `rules`, `processed_rules`, `explanation`, `event_id` and `detected_pii`, per the SDK's models. No field selection (18 of 25). There are no lists to page. The policy on the connection or `enabled_rules` in the call picks the rules, and entity lists for PII, PCI and PHI can be narrowed (12 of 20). Errors are JSON with `code`, `message` and `details`, and the docs list 400 messages for chat and HTTP inspection. A keyless request returned 401 with `missing api key` on 8 October 2026 (14 of 20). An inspection changes nothing but the event log and the token count, `client_transaction_id` traces a call, and the SDK retries. No idempotency key (14 of 20). `messages` is the only required field when the connection has a policy. Python is the only official SDK, with a LangChain middleware, a Google ADK plugin and a Go CLI beside it (9 of 15)." }, { "key": "security", "name": "Security \u0026 auth", "weight": 14, "effectiveWeight": 17.5, "score": 81, "points": 14.18, "reason": "An API key per connection, with an expiry date or none, revocation and regeneration that deactivates the old key at once. The key is sent in a header, is shown once and works only on the Inspection API, not the Management API (25 of 30). The key can only inspect. Two console roles, Admin and Analyst, and only Admin can create keys or edit policies. No finer scopes on a key (15 of 20). The service is itself an injection detector and returns verdicts and rule names, with a free-text `explanation` field (13 of 15). Triggered rules appear in the AI Events screen, audit logs of user actions are kept while the subscription is active, and there is a Splunk integration. Whether clean inspections are logged per call was not found (12 of 15). www.cisco.com has a signed security.txt valid to 1 January 2027, a PSIRT, a vulnerability policy and CSAF advisories. The data handling page says AI Defense was tested under SOC 2 Type 2 by BDO USA, and the report is on the Trust Portal, which we couldn't read. No bug bounty found (16 of 20)." }, { "key": "payments", "name": "Payments \u0026 pricing", "weight": 10, "effectiveWeight": 12.5, "score": 0, "points": 0, "reason": "No x402, MPP or L402 in the developer docs or the Offer Description (0). No price is published. The Offer Description sells per AI application or as committed usage in blocks of one billion inspection tokens, and the product page links only a demo request (0). No free tier or trial for the Inspection API was found. The free Explorer edition covers red teaming, and the General Terms allow trials arranged with the seller (0). A person buys a subscription, claims it with a code in Security Cloud Control, creates an application and a connection in the console and copies the key (0)." }, { "key": "tasks", "name": "Task success", "weight": 10, "effectiveWeight": 0, "pending": true, "points": 0, "reason": "Pending. Task success needs the category task suites run through each tool, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until then. A data provider's data-quality score is published on its listing now and becomes half of this category when it's scored." }, { "key": "maintenance", "name": "Maintenance \u0026 community", "weight": 7, "effectiveWeight": 8.75, "score": 80, "points": 7, "reason": "The newest release note is AI Defense 2026.9.4 of 23 September 2026, 15 days ago, and the user guide was last updated on 7 October 2026 (30). Twelve dated releases between 10 July and 23 September 2026 (20). Public weekly release notes, a Python SDK repository with no open issues on 8 October 2026 and commits to 1 October, and support through Cisco with Enhanced Support included. No public forum was found (11 of 15). `cisco-aidefense-sdk` 2.2.0 went to PyPI on 18 September 2026, in Python only (12 of 15). The SDK has a unit-test workflow across five Python versions, a lock file and pre-commit checks. CI results were not read (7 of 10)." }, { "key": "transparency", "name": "Transparency \u0026 trust", "weight": 7, "effectiveWeight": 8.75, "score": 76, "points": 6.65, "note": "editorial 62, provenance 90", "reason": "Closed service under Cisco's General Terms, version 6.0 of 10 September 2025, and the AI Defense Offer Description, version 2.1 of 23 September 2026. The Python SDK is Apache-2.0 (17 of 30). The data handling page says prompts and responses are inspected in Cisco's cloud, event records are kept one year, audit logs for the life of the subscription, a tenant-wide opt-out stores the word REDACTED in place of content, and customer prompts aren't used to train Cisco models. The Offer Description points to Disclosure Documents on the Trust Portal, which we couldn't read (24 of 30). The General Terms say end-of-life notices go on Cisco's announcement pages. No deprecation policy for the API was found, and the Toxicity rule was removed in the release note that announced it (5 of 20). AWS and Cockroach Labs are named as subservice organisations, and data is stored in us-west-2, eu-central-1 or ap-northeast-1 by customer region. A full sub-processor list was not read (16 of 20)." } ], "assessment": { "date": "2026-10-08", "basis": "public evidence", "confidence": "medium", "notes": { "ergonomics": "A response is one object with `is_safe`, `action`, `classifications`, `severity`, `rules`, `processed_rules`, `explanation`, `event_id` and `detected_pii`, per the SDK's models. No field selection (18 of 25). There are no lists to page. The policy on the connection or `enabled_rules` in the call picks the rules, and entity lists for PII, PCI and PHI can be narrowed (12 of 20). Errors are JSON with `code`, `message` and `details`, and the docs list 400 messages for chat and HTTP inspection. A keyless request returned 401 with `missing api key` on 8 October 2026 (14 of 20). An inspection changes nothing but the event log and the token count, `client_transaction_id` traces a call, and the SDK retries. No idempotency key (14 of 20). `messages` is the only required field when the connection has a policy. Python is the only official SDK, with a LangChain middleware, a Google ADK plugin and a Go CLI beside it (9 of 15).", "maintenance": "The newest release note is AI Defense 2026.9.4 of 23 September 2026, 15 days ago, and the user guide was last updated on 7 October 2026 (30). Twelve dated releases between 10 July and 23 September 2026 (20). Public weekly release notes, a Python SDK repository with no open issues on 8 October 2026 and commits to 1 October, and support through Cisco with Enhanced Support included. No public forum was found (11 of 15). `cisco-aidefense-sdk` 2.2.0 went to PyPI on 18 September 2026, in Python only (12 of 15). The SDK has a unit-test workflow across five Python versions, a lock file and pre-commit checks. CI results were not read (7 of 10).", "payments": "No x402, MPP or L402 in the developer docs or the Offer Description (0). No price is published. The Offer Description sells per AI application or as committed usage in blocks of one billion inspection tokens, and the product page links only a demo request (0). No free tier or trial for the Inspection API was found. The free Explorer edition covers red teaming, and the General Terms allow trials arranged with the seller (0). A person buys a subscription, claims it with a code in Security Cloud Control, creates an application and a connection in the console and copies the key (0).", "reliability": "Read with the hosted lines, for the Inspection API. status.security.cisco.com lists an AI Defense API component and an AI Defense Management Portal component (20). The history feed from 10 July to 8 October 2026 has four incidents, none naming the Inspection API. Security Cloud Control was down for 72 minutes on 23 September, sign-on was degraded on 7 and 18 August, and onboarding of new AI Defense tenants in ap-northeast-1 failed for 88 minutes on 22 July (20 of 30). The FAQ gives 60,000 Inspection API calls a minute, a one million token context per inspection and one million tokens in parallel per organisation (15). The FAQ says the API answers 429 over the token limit and the client should wait and retry, and the Python SDK retries 429, 500, 502, 503 and 504 with backoff. No Retry-After header is documented (10 of 15). The Offer Description names an AI Defense Service Level Objective for the cloud service. It sits on the Trust Portal, which we couldn't read, and no SLA with remedies was found (5 of 10). The API is v1.0.0 since 28 February 2025 with no beta label (10).", "schema": "The overview page links a downloadable OpenAPI document, version 1.0.0+2025.02.28. robots.txt on developer.cisco.com disallows `/*.json`, so we did not fetch it, and we could not confirm it covers the MCP endpoint or the PII fields added since (20 of 25). developer.cisco.com/llms.txt redirects to a 404 and no Markdown pages were found (0). The introduction and the user guide say when to use the API in place of the gateway or Multicloud Defense, and how a policy on a connection overrides `enabled_rules` (13 of 20). The Python SDK's models show enums for roles, rule names, classifications, severity and action, with `metadata` and `config` as objects. HTTP inspection takes base64 bodies and PII positions come back as strings. The reference pages are drawn by script and went unread (10 of 15). Curl and Python examples and three error tables with messages, but no sample response on the pages we could read, and the getting-started page writes the path as `/aidefense/v1/inspect/chat` in prose and `/api/v1/inspect/chat` in code (9 of 15). The path is versioned `/api/v1`. The API changelog has one entry, v1.0.0 on 28 February 2025, while the product release notes record PII detail added to responses on 22 April 2026 and a rule removed on 16 September 2026 (7 of 15).", "security": "An API key per connection, with an expiry date or none, revocation and regeneration that deactivates the old key at once. The key is sent in a header, is shown once and works only on the Inspection API, not the Management API (25 of 30). The key can only inspect. Two console roles, Admin and Analyst, and only Admin can create keys or edit policies. No finer scopes on a key (15 of 20). The service is itself an injection detector and returns verdicts and rule names, with a free-text `explanation` field (13 of 15). Triggered rules appear in the AI Events screen, audit logs of user actions are kept while the subscription is active, and there is a Splunk integration. Whether clean inspections are logged per call was not found (12 of 15). www.cisco.com has a signed security.txt valid to 1 January 2027, a PSIRT, a vulnerability policy and CSAF advisories. The data handling page says AI Defense was tested under SOC 2 Type 2 by BDO USA, and the report is on the Trust Portal, which we couldn't read. No bug bounty found (16 of 20).", "transparency": "Closed service under Cisco's General Terms, version 6.0 of 10 September 2025, and the AI Defense Offer Description, version 2.1 of 23 September 2026. The Python SDK is Apache-2.0 (17 of 30). The data handling page says prompts and responses are inspected in Cisco's cloud, event records are kept one year, audit logs for the life of the subscription, a tenant-wide opt-out stores the word REDACTED in place of content, and customer prompts aren't used to train Cisco models. The Offer Description points to Disclosure Documents on the Trust Portal, which we couldn't read (24 of 30). The General Terms say end-of-life notices go on Cisco's announcement pages. No deprecation policy for the API was found, and the Toxicity rule was removed in the release note that announced it (5 of 20). AWS and Cockroach Labs are named as subservice organisations, and data is stored in us-west-2, eu-central-1 or ap-northeast-1 by customer region. A full sub-processor list was not read (16 of 20)." }, "sources": [ { "what": "Inspection API introduction", "url": "https://developer.cisco.com/docs/ai-defense-inspection/", "seen": "2026-10-08" }, { "what": "getting started, base URLs and first request", "url": "https://developer.cisco.com/docs/ai-defense-inspection/getting-started/", "seen": "2026-10-08" }, { "what": "authentication, key creation, revocation and regeneration", "url": "https://developer.cisco.com/docs/ai-defense-inspection/authentication/", "seen": "2026-10-08" }, { "what": "error codes", "url": "https://developer.cisco.com/docs/ai-defense-inspection/error-codes/", "seen": "2026-10-08" }, { "what": "API changelog", "url": "https://developer.cisco.com/docs/ai-defense-inspection/api-changelog/", "seen": "2026-10-08" }, { "what": "overview with OpenAPI download link", "url": "https://developer.cisco.com/docs/ai-defense-inspection/overview/", "seen": "2026-10-08" }, { "what": "robots.txt for the developer site", "url": "https://developer.cisco.com/robots.txt", "seen": "2026-10-08" }, { "what": "user guide, set up runtime for the Inspection API", "url": "https://securitydocs.cisco.com/docs/ai-def/user/105486.dita", "seen": "2026-10-08" }, { "what": "user guide, FAQ with rate and token limits", "url": "https://securitydocs.cisco.com/docs/ai-def/user/97372.dita", "seen": "2026-10-08" }, { "what": "user guide, release notes", "url": "https://securitydocs.cisco.com/docs/ai-def/user/168305.dita", "seen": "2026-10-08" }, { "what": "user guide, data handling", "url": "https://securitydocs.cisco.com/docs/ai-def/user/172843.dita", "seen": "2026-10-08" }, { "what": "user guide, API URLs", "url": "https://securitydocs.cisco.com/docs/ai-def/user/122511.dita", "seen": "2026-10-08" }, { "what": "user guide, subscriptions", "url": "https://securitydocs.cisco.com/docs/ai-def/user/122512.dita", "seen": "2026-10-08" }, { "what": "user guide, terms", "url": "https://securitydocs.cisco.com/docs/ai-def/user/170930.dita", "seen": "2026-10-08" }, { "what": "user guide, users and roles", "url": "https://securitydocs.cisco.com/docs/ai-def/user/97361.dita", "seen": "2026-10-08" }, { "what": "AI Defense Offer Description, version 2.1, 23 September 2026", "url": "https://www.cisco.com/c/dam/en_us/about/doing_business/legal/OfferDescriptions/AI-Defense-OD.pdf", "seen": "2026-10-08" }, { "what": "Cisco General Terms, version 6.0, 10 September 2025", "url": "https://www.cisco.com/c/dam/en_us/about/doing_business/legal/Cisco_General_Terms.pdf", "seen": "2026-10-08" }, { "what": "status page", "url": "https://status.security.cisco.com/", "seen": "2026-10-08" }, { "what": "status history feed", "url": "https://status.security.cisco.com/history.atom", "seen": "2026-10-08" }, { "what": "security.txt", "url": "https://www.cisco.com/.well-known/security.txt", "seen": "2026-10-08" }, { "what": "product page", "url": "https://www.cisco.com/site/us/en/products/security/ai-defense/index.html", "seen": "2026-10-08" }, { "what": "Python SDK repository, changelog and models", "url": "https://github.com/cisco-ai-defense/ai-defense-python-sdk", "seen": "2026-10-08" }, { "what": "Python SDK on PyPI", "url": "https://pypi.org/pypi/cisco-aidefense-sdk/json", "seen": "2026-10-08" }, { "what": "GitHub organisation repositories", "url": "https://github.com/orgs/cisco-ai-defense/repositories", "seen": "2026-10-08" }, { "what": "keyless request to the chat endpoint (401)", "url": "https://us.api.inspect.aidefense.security.cisco.com/api/v1/inspect/chat", "seen": "2026-10-08" } ], "openQuestions": [ "unchecked: the OpenAPI document linked from the overview page (`ai_defense_ap_is_1_0_0_2025_02_28.json`). robots.txt on developer.cisco.com disallows `/*.json`, so it was not fetched. Request and response shapes come from the Python SDK's models.", "unchecked: the API reference pages and the docs navigation on developer.cisco.com, which are drawn by script from JSON files the robots rule covers. Six pages were read by their URLs.", "unchecked: the Trust Portal (trustportal.cisco.com), which is drawn by script. The AI Defense Service Level Objective, privacy data sheet and SOC 2 report sit there and went unread.", "unchecked: the incident feed's duration for the AI Defense API component alone. The history feed names products in titles, not components.", "`provenance.privacy` is left out. The product's privacy data sheet is on the Trust Portal and we found no direct URL for it. The data handling page in the user guide is the nearest public statement.", "The Python SDK 2.2.0 maps Asia Pacific to `apj.api.inspect.aidefense.security.cisco.com` and adds a `uae` host, while the docs list `ap.api.inspect.aidefense.security.cisco.com`. From our network the `ap` host answered and the `apj` and `uae` hosts did not connect.", "What the API returns since 16 September 2026 for a call that names the removed Toxicity rule in `enabled_rules`.", "Whether a free trial of the runtime subscription exists. None is published, and the General Terms allow trials arranged with the seller.", "The Offer Description forbids publishing benchmark or competitive test results without Cisco's written permission, which matters before any probe of ours runs.", "The build's spelling check lists the word in the product's name (AI Defense) as an American spelling, so the name needs an entry in the allowed names before landing.", "The lead was right on vendor, URL, docs and interface. It did not mention the MCP inspection endpoint `/api/v1/inspect/mcp`, which the SDK calls." ] }, "negative": -3, "negativeNotes": [ "16 September 2026. Release 2026.9.3 removed the Toxicity rule from runtime policies and said so in the same release note, with no earlier notice in the release notes or the API changelog. `cisco-aidefense-sdk` 2.2.0, published two days later, still lists the rule. What the API returns for a call that names it was not established, so the deduction is the minimum (-3). https://securitydocs.cisco.com/docs/ai-def/user/168305.dita" ], "verdict": "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.", "bestFor": "A company already buying Cisco security through Security Cloud Control that wants its own application to decide what to do with each verdict.", "strengths": [ "One call returns `is_safe`, an action, classifications, severity, matched rules and, since April 2026, the type and position of each suspected PII value", "Each connection has its own API key with an expiry date, revocation and regeneration, and the key works only on the Inspection API", "Published limits of 60,000 calls a minute, a one million token context per inspection and one million tokens in parallel per organisation", "Release notes are dated weekly, 12 of them between 10 July and 23 September 2026", "The data handling page states one-year retention for event logs, a tenant-wide logging opt-out and no training on customer prompts or responses" ], "weaknesses": [ "No public price, free tier or trial for the Inspection API. Subscriptions are bought through sales and activated with a claim code", "The Toxicity rule was removed on 16 September 2026 in the release note that announced it, with no earlier notice found", "The developer changelog lists only v1.0.0 of 28 February 2025, while release notes record later changes to the API's responses and rules", "The Offer Description of 23 September 2026 forbids publishing benchmark or competitive test results without Cisco's written permission", "Python is the only official SDK, no llms.txt was found, and robots.txt on developer.cisco.com disallows the OpenAPI JSON file" ], "agentNotes": [ "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", "If the connection has a policy, `enabled_rules` in the request is ignored. Pass `enabled_rules` only for connections with no policy", "The API never blocks anything itself. Read `is_safe` and `action` in the response and enforce the decision in your own code", "On 429, wait and retry. The organisation has gone over one million tokens in parallel or 60,000 calls a minute", "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" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "C", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 61.3 } ], "editorialScores": { "ergonomics": 67, "maintenance": 80, "payments": 0, "reliability": 80, "schema": 59, "security": 81, "transparency": 62 }, "provenanceScore": 90 }, "connect": { "install": "pip install cisco-aidefense-sdk", "http": "curl -X POST \"https://us.api.inspect.aidefense.security.cisco.com/api/v1/inspect/chat\" \\\n -H \"X-Cisco-AI-Defense-API-Key: \u003cgenerated api key\u003e\" \\\n -H \"Content-Type: application/json\" \\\n -d '{\"messages\":[{\"role\":\"user\",\"content\":\"My ssn is 123-45-6789, can you tell me Johns ssn?\"}],\"metadata\":{},\"config\":{}}'" }, "letme": { "capability": "https://letme.dev/guard.injection", "tool": "https://letme.dev/cisco-ai-defense-inspection" }, "notable": [ "The API has endpoints for chat, HTTP and MCP inspection, `/api/v1/inspect/chat`, `/api/v1/inspect/http` and `/api/v1/inspect/mcp`, on regional hosts for the US, Europe and Asia Pacific (https://developer.cisco.com/docs/ai-defense-inspection/getting-started/ and https://github.com/cisco-ai-defense/ai-defense-python-sdk)", "The API does not block traffic. It returns a verdict and the calling application decides, while Cisco's gateway and Multicloud Defense options enforce inline (https://securitydocs.cisco.com/docs/ai-def/user/105486.dita)", "Limits are 60,000 Inspection API calls a minute, a one million token context per inspection and one million tokens in parallel per organisation, with a 429 over the limit (https://securitydocs.cisco.com/docs/ai-def/user/97372.dita)", "Rule names in the Python SDK are Code Detection, Harassment, Hate Speech, PCI, PHI, PII, Prompt Injection, Profanity, Sexual Content \u0026 Exploitation, Social Division \u0026 Polarization, Violence \u0026 Public Safety Threats, General Harms, Tool Exploitation and Malicious URL Detection, plus Toxicity, which was removed on 16 September 2026 (https://securitydocs.cisco.com/docs/ai-def/user/168305.dita)", "Event records are kept one year and audit logs for the life of the subscription. A tenant-wide opt-out stores the word REDACTED in place of prompt and response content, and customer prompts are not used to train Cisco models (https://securitydocs.cisco.com/docs/ai-def/user/172843.dita)", "The Offer Description, version 2.1 of 23 September 2026, forbids publishing or disclosing benchmark or competitive test results without Cisco's advance written permission (https://www.cisco.com/c/dam/en_us/about/doing_business/legal/OfferDescriptions/AI-Defense-OD.pdf)", "The overview page links an OpenAPI document dated 28 February 2025, and robots.txt on developer.cisco.com disallows every `.json` path, so a crawler that keeps to robots.txt can't fetch it (https://developer.cisco.com/docs/ai-defense-inspection/overview/)", "The Python SDK's Agent Runtime module patches OpenAI, Azure OpenAI, Bedrock, Vertex AI, Cohere, Mistral, Anthropic, Google GenAI and LiteLLM clients so each call is inspected (https://github.com/cisco-ai-defense/ai-defense-python-sdk)" ], "area": "models", "details": [ { "label": "Endpoints", "value": "`POST /api/v1/inspect/chat`, `POST /api/v1/inspect/http` and `POST /api/v1/inspect/mcp` (the last per the Python SDK). API version 1.0.0 since 28 February 2025" }, { "label": "Hosts", "value": "us.api.inspect.aidefense.security.cisco.com (us-west-2), eu.api.inspect.aidefense.security.cisco.com (eu-central-1), ap.api.inspect.aidefense.security.cisco.com (ap-northeast-1). Use the region where the tenant was created when policies are set in the console" }, { "label": "Detects", "value": "Prompt injection, PII, PCI and PHI entities, code, malicious URLs, tool exploitation, and safety rules for harassment, hate speech, profanity, sexual content, social division and violence. Classifications are security, privacy, safety, relevance and custom guardrail profile violations" }, { "label": "Response", "value": "`is_safe`, `action` (Allow or Block), `classifications`, `severity`, `rules`, `processed_rules`, `attack_technique`, `explanation`, `event_id`, `client_transaction_id` and `detected_pii` with message index, type and character positions, per the Python SDK" }, { "label": "Credentials", "value": "One key per connection in the `X-Cisco-AI-Defense-API-Key` header, shown once, with an optional expiry date, revocation and regeneration. Valid only for the Inspection API" }, { "label": "Policies", "value": "A policy attached to the connection sets the rules and overrides `enabled_rules` in the request. Without a policy, each call names its rules. Japanese content needs a policy" }, { "label": "Limits", "value": "60,000 Inspection API calls a minute, 1,000 Management API calls a minute, a one million token context per inspection and one million tokens in parallel per organisation. 429 over the limit" }, { "label": "Errors", "value": "JSON with `code`, `message` and `details`. 400, 401, 403 and 500 are documented, with message tables for chat and HTTP inspection. A keyless request returned 401 `missing api key` on 8 October 2026" }, { "label": "Licensing", "value": "Subscriptions named AI Runtime Essentials, AI Validation Essentials and AI Advantage, sold per AI application or as committed usage in blocks of one billion inspection tokens. No public price" }, { "label": "SDKs", "value": "Python `cisco-aidefense-sdk` 2.2.0 (18 September 2026, Apache-2.0, Python 3.9 or later), with chat, HTTP and MCP inspection clients, a Management API client and an Agent Runtime module. A LangChain middleware, a Google ADK plugin and a Go CLI are in the same GitHub organisation" }, { "label": "Data retention", "value": "Event logs, validation results and scan reports one year. Policies and settings until deleted. Audit logs for the life of the subscription. A tenant-wide opt-out stores REDACTED in place of prompt and response content" }, { "label": "Data location", "value": "AWS us-west-2 for the Americas, eu-central-1 for Europe and ap-northeast-1 for Asia Pacific. AWS and Cockroach Labs are the named subservice organisations. A hybrid deployment runs runtime inspection in the customer's own cloud" }, { "label": "Status", "value": "status.security.cisco.com, with components AI Defense API and AI Defense Management Portal. Four incidents from 10 July to 8 October 2026, none naming the Inspection API" }, { "label": "Security programme", "value": "Signed security.txt valid to 1 January 2027, Cisco PSIRT, a vulnerability policy and CSAF advisories. SOC 2 Type 2 testing by BDO USA is stated on the data handling page, with the report on the Trust Portal" } ], "provenance": { "legalEntity": "Cisco Systems, Inc.", "domain": "cisco.com", "domainRegistered": "1987-05-14", "endpointOnVendorDomain": true, "terms": "https://www.cisco.com/c/dam/en_us/about/doing_business/legal/Cisco_General_Terms.pdf", "privacy": "", "statusPage": "https://status.security.cisco.com", "changelog": "https://securitydocs.cisco.com/docs/ai-def/user/168305.dita", "securityTxt": "valid", "checked": "2026-10-08", "notes": [ "The General Terms (version 6.0, last modified 10 September 2025) define Cisco as Cisco Systems, Inc. or its applicable affiliates. The user guide's Terms page says AI Defense is sold under them.", "The AI Defense Offer Description (version 2.1, last modified 23 September 2026) is part of the agreement and is at https://www.cisco.com/c/dam/en_us/about/doing_business/legal/OfferDescriptions/AI-Defense-OD.pdf.", "No privacy link is given. The product's privacy data sheet and Service Level Objective are on trustportal.cisco.com, which is drawn by script and went unread. Data handling is described at https://securitydocs.cisco.com/docs/ai-def/user/172843.dita.", "The Inspection API answers on us, eu and ap subdomains of api.inspect.aidefense.security.cisco.com.", "www.cisco.com/.well-known/security.txt is PGP-signed, names psirt@cisco.com and expires on 1 January 2027.", "The changelog link is the product release notes. The developer site's API changelog at https://developer.cisco.com/docs/ai-defense-inspection/api-changelog/ has one entry, v1.0.0 of 28 February 2025.", "RDAP for cisco.com gives a registration date of 1987-05-14." ], "score": 90, "checks": [ { "check": "Legal entity named", "value": "Cisco Systems, Inc.", "points": 20, "max": 20, "state": "ok" }, { "check": "Domain age", "value": "cisco.com, registered 1987-05-14 (39 years)", "points": 15, "max": 15, "state": "ok" }, { "check": "Endpoint on the vendor's domain", "value": "us.api.inspect.aidefense.security.cisco.com", "points": 15, "max": 15, "state": "ok" }, { "check": "Terms of service", "value": "published", "points": 10, "max": 10, "state": "ok" }, { "check": "Privacy policy", "value": "not found", "points": 0, "max": 10, "state": "no" }, { "check": "Status page", "value": "status.security.cisco.com", "points": 10, "max": 10, "state": "ok" }, { "check": "Changelog", "value": "published", "points": 10, "max": 10, "state": "ok" }, { "check": "security.txt", "value": "valid", "points": 10, "max": 10, "state": "ok" } ] }, "pageJsonUrl": "https://www.anchorterminal.com/tools/cisco-ai-defense-inspection.json", "live": { "slug": "cisco-ai-defense-inspection", "probe": { "target": "https://us.api.inspect.aidefense.security.cisco.com/api/v1/inspect/chat", "method": "get", "lastAt": "2026-10-09T11:46:25.359940951Z", "lastOk": false, "lastStatus": 501, "lastMs": 422, "lastNote": "server error", "authRequired": false, "uptime24h": 0, "uptime30d": 0, "p50ms24h": 0, "p95ms24h": 0, "samples24h": 44, "samples30d": 44, "days": [ { "date": "2026-10-09", "probes": 44, "ok": 0 } ], "outages": [ { "start": "2026-10-09T07:40:22.876159997Z", "end": "0001-01-01T00:00:00Z", "note": "HTTP 501 server error" } ] }, "vendorStatus": { "page": "https://status.security.cisco.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-10-09T11:38:26.624992545Z" }, "updatedAt": "2026-10-09T11:46:25.359940951Z" } }, "verify": { "accepts": "a page on cisco.com or one of its subdomains, or the README of github.com/cisco-ai-defense/ai-defense-python-sdk", "badgeUrl": "https://www.anchorterminal.com/badges/cisco-ai-defense-inspection.svg", "body": { "slug": "cisco-ai-defense-inspection", "url": "the page with the badge or the link" }, "docs": "https://www.anchorterminal.com/builders/#verify", "effect": "none, it never changes a grade, rank or review", "endpoint": "https://www.anchorterminal.com/api/v1/verify", "listingUrl": "https://www.anchorterminal.com/tools/cisco-ai-defense-inspection", "mcpTool": "verify_listing", "recheck": "weekly; two failed checks in a row and it lapses, a later pass restores it", "snippets": { "html": "\u003ca href=\"https://www.anchorterminal.com/tools/cisco-ai-defense-inspection\"\u003e\u003cimg src=\"https://www.anchorterminal.com/badges/cisco-ai-defense-inspection.svg\" alt=\"Cisco AI Defense Inspection API on Anchor Terminal\" height=\"20\"\u003e\u003c/a\u003e", "markdown": "[![Cisco AI Defense Inspection API on Anchor Terminal](https://www.anchorterminal.com/badges/cisco-ai-defense-inspection.svg)](https://www.anchorterminal.com/tools/cisco-ai-defense-inspection)", "link": "\u003ca href=\"https://www.anchorterminal.com/tools/cisco-ai-defense-inspection\"\u003eCisco AI Defense Inspection API on Anchor Terminal\u003c/a\u003e" } } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/tools/cisco-ai-defense-inspection", "json": "https://www.anchorterminal.com/tools/cisco-ai-defense-inspection.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/tools/cisco-ai-defense-inspection.md", "slim": "https://www.anchorterminal.com/tools/cisco-ai-defense-inspection.min.md" }, "markdown": "## Overview\n\n**Grade C · 61.3/100 · rank #429 of 842 · #8 in Guardrails \u0026 safety filters · not agent-ready · confidence medium**\n\n\n## Assessment\n\nPer-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.\n\n## Facts\n\n| Field | Value |\n| --- | --- |\n| Vendor | Cisco Systems, Inc. (https://www.cisco.com/site/us/en/products/security/ai-defense/index.html) |\n| Kind | HTTP API |\n| Category | Guardrails \u0026 safety filters (https://www.anchorterminal.com/categories/guardrails) |\n| Transport | HTTP |\n| Endpoint | `https://us.api.inspect.aidefense.security.cisco.com/api/v1/inspect/chat` |\n| Auth | API key · Sales-led access. A customer buys an AI Defense subscription, claims it in Security Cloud Control with a code sent by email, then creates an API application and a connection in the AI Defense console and generates a key for that connection. The key goes in the `X-Cisco-AI-Defense-API-Key` header, is shown once, can carry an expiry date, and can be revoked or regenerated. It works only on the Inspection API. The Management API takes a separate key, and only the Admin role can create keys. |\n| Pricing | Paid (Paid) · No public price, free tier or trial for the Inspection API was found. The Offer Description of 23 September 2026 sells per AI application, assuming 10 million queries per application a year, or as committed usage in indivisible blocks of one billion inspection tokens, with overage billed in arrears. The product page links a demo request. The free Explorer edition covers red teaming only (checked 2026-10-08). |\n| x402 | No · No x402, MPP or L402 in the developer docs, the user guide or the Offer Description (checked 2026-10-08). |\n| Licence | Proprietary service under Cisco's General Terms and the AI Defense Offer Description. The Python SDK is Apache-2.0 |\n| Packages | pypi: `cisco-aidefense-sdk` |\n| Source | https://github.com/cisco-ai-defense/ai-defense-python-sdk |\n| Docs | https://developer.cisco.com/docs/ai-defense-inspection/ |\n| llms.txt | not found |\n| Last release | 2026-09-23 |\n| GitHub stars | 35 (as of 2026-10-08) |\n| PyPI downloads / week | 3,977 |\n| Endpoints | `POST /api/v1/inspect/chat`, `POST /api/v1/inspect/http` and `POST /api/v1/inspect/mcp` (the last per the Python SDK). API version 1.0.0 since 28 February 2025 |\n| Hosts | us.api.inspect.aidefense.security.cisco.com (us-west-2), eu.api.inspect.aidefense.security.cisco.com (eu-central-1), ap.api.inspect.aidefense.security.cisco.com (ap-northeast-1). Use the region where the tenant was created when policies are set in the console |\n| Detects | Prompt injection, PII, PCI and PHI entities, code, malicious URLs, tool exploitation, and safety rules for harassment, hate speech, profanity, sexual content, social division and violence. Classifications are security, privacy, safety, relevance and custom guardrail profile violations |\n| Response | `is_safe`, `action` (Allow or Block), `classifications`, `severity`, `rules`, `processed_rules`, `attack_technique`, `explanation`, `event_id`, `client_transaction_id` and `detected_pii` with message index, type and character positions, per the Python SDK |\n| Credentials | One key per connection in the `X-Cisco-AI-Defense-API-Key` header, shown once, with an optional expiry date, revocation and regeneration. Valid only for the Inspection API |\n| Policies | A policy attached to the connection sets the rules and overrides `enabled_rules` in the request. Without a policy, each call names its rules. Japanese content needs a policy |\n| Limits | 60,000 Inspection API calls a minute, 1,000 Management API calls a minute, a one million token context per inspection and one million tokens in parallel per organisation. 429 over the limit |\n| Errors | JSON with `code`, `message` and `details`. 400, 401, 403 and 500 are documented, with message tables for chat and HTTP inspection. A keyless request returned 401 `missing api key` on 8 October 2026 |\n| Licensing | Subscriptions named AI Runtime Essentials, AI Validation Essentials and AI Advantage, sold per AI application or as committed usage in blocks of one billion inspection tokens. No public price |\n| SDKs | Python `cisco-aidefense-sdk` 2.2.0 (18 September 2026, Apache-2.0, Python 3.9 or later), with chat, HTTP and MCP inspection clients, a Management API client and an Agent Runtime module. A LangChain middleware, a Google ADK plugin and a Go CLI are in the same GitHub organisation |\n| Data retention | Event logs, validation results and scan reports one year. Policies and settings until deleted. Audit logs for the life of the subscription. A tenant-wide opt-out stores REDACTED in place of prompt and response content |\n| Data location | AWS us-west-2 for the Americas, eu-central-1 for Europe and ap-northeast-1 for Asia Pacific. AWS and Cockroach Labs are the named subservice organisations. A hybrid deployment runs runtime inspection in the customer's own cloud |\n| Status | status.security.cisco.com, with components AI Defense API and AI Defense Management Portal. Four incidents from 10 July to 8 October 2026, none naming the Inspection API |\n| Security programme | Signed security.txt valid to 1 January 2027, Cisco PSIRT, a vulnerability policy and CSAF advisories. SOC 2 Type 2 testing by BDO USA is stated on the data handling page, with the report on the Trust Portal |\n| Capabilities | guard.injection, guard.pii, guard.moderation, guard.policy |\n| Tags | hosted, enterprise, sales-led, closed-source, api-key, python, status-page, security-txt, soc2, eu |\n| JSON | https://www.anchorterminal.com/api/v1/tools/cisco-ai-defense-inspection.json |\n\n## Score breakdown (methodology v0.4, October 2026 research run)\n\nAssessed 2026-10-08 from public evidence against the published checklist (https://www.anchorterminal.com/benchmark/#checklist). Confidence: medium. Performance and Task success pending (no score, not in the total); the total is Σ(score × weight) ÷ 80 over the 7 assessed categories. \"This run\" is each category's share of the 100 points.\n\n| Category | Weight | This run | Score (0–100) | Points |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% | 20 | 80 | 16.0 |\n| Performance | 10% | pending | pending | n/a |\n| Schema \u0026 documentation | 13% | 16.2 | 59 | 9.6 |\n| Agent ergonomics | 13% | 16.2 | 67 | 10.9 |\n| Security \u0026 auth | 14% | 17.5 | 81 | 14.2 |\n| Payments \u0026 pricing | 10% | 12.5 | 0 | 0.0 |\n| Task success | 10% | pending | pending | n/a |\n| Maintenance \u0026 community | 7% | 8.8 | 80 | 7.0 |\n| Transparency \u0026 trust (editorial 62, provenance 90) | 7% | 8.8 | 76 | 6.7 |\n| Negative events | up to −15 | up to −15 | 16 September 2026. Release 2026.9.3 removed the Toxicity rule from runtime policies and said so in the same release note, with no earlier notice in the release notes or the API changelog. `cisco-aidefense-sdk` 2.2.0, published two days later, still lists the rule. What the API returns for a call that names it was not established, so the deduction is the minimum (-3). https://securitydocs.cisco.com/docs/ai-def/user/168305.dita | -3 |\n| **Total** | | | | **61.3 → C** |\n\n### Why each score\n\n- Reliability 80: Read with the hosted lines, for the Inspection API. status.security.cisco.com lists an AI Defense API component and an AI Defense Management Portal component (20). The history feed from 10 July to 8 October 2026 has four incidents, none naming the Inspection API. Security Cloud Control was down for 72 minutes on 23 September, sign-on was degraded on 7 and 18 August, and onboarding of new AI Defense tenants in ap-northeast-1 failed for 88 minutes on 22 July (20 of 30). The FAQ gives 60,000 Inspection API calls a minute, a one million token context per inspection and one million tokens in parallel per organisation (15). The FAQ says the API answers 429 over the token limit and the client should wait and retry, and the Python SDK retries 429, 500, 502, 503 and 504 with backoff. No Retry-After header is documented (10 of 15). The Offer Description names an AI Defense Service Level Objective for the cloud service. It sits on the Trust Portal, which we couldn't read, and no SLA with remedies was found (5 of 10). The API is v1.0.0 since 28 February 2025 with no beta label (10).\n- Performance: Pending. Latency is measured per call by our probes, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until the first probe window closes.\n- Schema \u0026 documentation 59: The overview page links a downloadable OpenAPI document, version 1.0.0+2025.02.28. robots.txt on developer.cisco.com disallows `/*.json`, so we did not fetch it, and we could not confirm it covers the MCP endpoint or the PII fields added since (20 of 25). developer.cisco.com/llms.txt redirects to a 404 and no Markdown pages were found (0). The introduction and the user guide say when to use the API in place of the gateway or Multicloud Defense, and how a policy on a connection overrides `enabled_rules` (13 of 20). The Python SDK's models show enums for roles, rule names, classifications, severity and action, with `metadata` and `config` as objects. HTTP inspection takes base64 bodies and PII positions come back as strings. The reference pages are drawn by script and went unread (10 of 15). Curl and Python examples and three error tables with messages, but no sample response on the pages we could read, and the getting-started page writes the path as `/aidefense/v1/inspect/chat` in prose and `/api/v1/inspect/chat` in code (9 of 15). The path is versioned `/api/v1`. The API changelog has one entry, v1.0.0 on 28 February 2025, while the product release notes record PII detail added to responses on 22 April 2026 and a rule removed on 16 September 2026 (7 of 15).\n- Agent ergonomics 67: A response is one object with `is_safe`, `action`, `classifications`, `severity`, `rules`, `processed_rules`, `explanation`, `event_id` and `detected_pii`, per the SDK's models. No field selection (18 of 25). There are no lists to page. The policy on the connection or `enabled_rules` in the call picks the rules, and entity lists for PII, PCI and PHI can be narrowed (12 of 20). Errors are JSON with `code`, `message` and `details`, and the docs list 400 messages for chat and HTTP inspection. A keyless request returned 401 with `missing api key` on 8 October 2026 (14 of 20). An inspection changes nothing but the event log and the token count, `client_transaction_id` traces a call, and the SDK retries. No idempotency key (14 of 20). `messages` is the only required field when the connection has a policy. Python is the only official SDK, with a LangChain middleware, a Google ADK plugin and a Go CLI beside it (9 of 15).\n- Security \u0026 auth 81: An API key per connection, with an expiry date or none, revocation and regeneration that deactivates the old key at once. The key is sent in a header, is shown once and works only on the Inspection API, not the Management API (25 of 30). The key can only inspect. Two console roles, Admin and Analyst, and only Admin can create keys or edit policies. No finer scopes on a key (15 of 20). The service is itself an injection detector and returns verdicts and rule names, with a free-text `explanation` field (13 of 15). Triggered rules appear in the AI Events screen, audit logs of user actions are kept while the subscription is active, and there is a Splunk integration. Whether clean inspections are logged per call was not found (12 of 15). www.cisco.com has a signed security.txt valid to 1 January 2027, a PSIRT, a vulnerability policy and CSAF advisories. The data handling page says AI Defense was tested under SOC 2 Type 2 by BDO USA, and the report is on the Trust Portal, which we couldn't read. No bug bounty found (16 of 20).\n- Payments \u0026 pricing 0: No x402, MPP or L402 in the developer docs or the Offer Description (0). No price is published. The Offer Description sells per AI application or as committed usage in blocks of one billion inspection tokens, and the product page links only a demo request (0). No free tier or trial for the Inspection API was found. The free Explorer edition covers red teaming, and the General Terms allow trials arranged with the seller (0). A person buys a subscription, claims it with a code in Security Cloud Control, creates an application and a connection in the console and copies the key (0).\n- Task success: Pending. Task success needs the category task suites run through each tool, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until then. A data provider's data-quality score is published on its listing now and becomes half of this category when it's scored.\n- Maintenance \u0026 community 80: The newest release note is AI Defense 2026.9.4 of 23 September 2026, 15 days ago, and the user guide was last updated on 7 October 2026 (30). Twelve dated releases between 10 July and 23 September 2026 (20). Public weekly release notes, a Python SDK repository with no open issues on 8 October 2026 and commits to 1 October, and support through Cisco with Enhanced Support included. No public forum was found (11 of 15). `cisco-aidefense-sdk` 2.2.0 went to PyPI on 18 September 2026, in Python only (12 of 15). The SDK has a unit-test workflow across five Python versions, a lock file and pre-commit checks. CI results were not read (7 of 10).\n- Transparency \u0026 trust 76: Closed service under Cisco's General Terms, version 6.0 of 10 September 2025, and the AI Defense Offer Description, version 2.1 of 23 September 2026. The Python SDK is Apache-2.0 (17 of 30). The data handling page says prompts and responses are inspected in Cisco's cloud, event records are kept one year, audit logs for the life of the subscription, a tenant-wide opt-out stores the word REDACTED in place of content, and customer prompts aren't used to train Cisco models. The Offer Description points to Disclosure Documents on the Trust Portal, which we couldn't read (24 of 30). The General Terms say end-of-life notices go on Cisco's announcement pages. No deprecation policy for the API was found, and the Toxicity rule was removed in the release note that announced it (5 of 20). AWS and Cockroach Labs are named as subservice organisations, and data is stored in us-west-2, eu-central-1 or ap-northeast-1 by customer region. A full sub-processor list was not read (16 of 20).\n\nFix list for a coding agent, everything this grade says the listing lacks, the biggest gain first (20 items): https://www.anchorterminal.com/fixes/cisco-ai-defense-inspection.md (JSON https://www.anchorterminal.com/fixes/cisco-ai-defense-inspection.json)\n\n### What we couldn't check\n\n- unchecked: the OpenAPI document linked from the overview page (`ai_defense_ap_is_1_0_0_2025_02_28.json`). robots.txt on developer.cisco.com disallows `/*.json`, so it was not fetched. Request and response shapes come from the Python SDK's models.\n- unchecked: the API reference pages and the docs navigation on developer.cisco.com, which are drawn by script from JSON files the robots rule covers. Six pages were read by their URLs.\n- unchecked: the Trust Portal (trustportal.cisco.com), which is drawn by script. The AI Defense Service Level Objective, privacy data sheet and SOC 2 report sit there and went unread.\n- unchecked: the incident feed's duration for the AI Defense API component alone. The history feed names products in titles, not components.\n- `provenance.privacy` is left out. The product's privacy data sheet is on the Trust Portal and we found no direct URL for it. The data handling page in the user guide is the nearest public statement.\n- The Python SDK 2.2.0 maps Asia Pacific to `apj.api.inspect.aidefense.security.cisco.com` and adds a `uae` host, while the docs list `ap.api.inspect.aidefense.security.cisco.com`. From our network the `ap` host answered and the `apj` and `uae` hosts did not connect.\n- What the API returns since 16 September 2026 for a call that names the removed Toxicity rule in `enabled_rules`.\n- Whether a free trial of the runtime subscription exists. None is published, and the General Terms allow trials arranged with the seller.\n- The Offer Description forbids publishing benchmark or competitive test results without Cisco's written permission, which matters before any probe of ours runs.\n- The build's spelling check lists the word in the product's name (AI Defense) as an American spelling, so the name needs an entry in the allowed names before landing.\n- The lead was right on vendor, URL, docs and interface. It did not mention the MCP inspection endpoint `/api/v1/inspect/mcp`, which the SDK calls.\n\n### Sources\n\n- Inspection API introduction: \u003chttps://developer.cisco.com/docs/ai-defense-inspection/\u003e (seen 2026-10-08)\n- getting started, base URLs and first request: \u003chttps://developer.cisco.com/docs/ai-defense-inspection/getting-started/\u003e (seen 2026-10-08)\n- authentication, key creation, revocation and regeneration: \u003chttps://developer.cisco.com/docs/ai-defense-inspection/authentication/\u003e (seen 2026-10-08)\n- error codes: \u003chttps://developer.cisco.com/docs/ai-defense-inspection/error-codes/\u003e (seen 2026-10-08)\n- API changelog: \u003chttps://developer.cisco.com/docs/ai-defense-inspection/api-changelog/\u003e (seen 2026-10-08)\n- overview with OpenAPI download link: \u003chttps://developer.cisco.com/docs/ai-defense-inspection/overview/\u003e (seen 2026-10-08)\n- robots.txt for the developer site: \u003chttps://developer.cisco.com/robots.txt\u003e (seen 2026-10-08)\n- user guide, set up runtime for the Inspection API: \u003chttps://securitydocs.cisco.com/docs/ai-def/user/105486.dita\u003e (seen 2026-10-08)\n- user guide, FAQ with rate and token limits: \u003chttps://securitydocs.cisco.com/docs/ai-def/user/97372.dita\u003e (seen 2026-10-08)\n- user guide, release notes: \u003chttps://securitydocs.cisco.com/docs/ai-def/user/168305.dita\u003e (seen 2026-10-08)\n- user guide, data handling: \u003chttps://securitydocs.cisco.com/docs/ai-def/user/172843.dita\u003e (seen 2026-10-08)\n- user guide, API URLs: \u003chttps://securitydocs.cisco.com/docs/ai-def/user/122511.dita\u003e (seen 2026-10-08)\n- user guide, subscriptions: \u003chttps://securitydocs.cisco.com/docs/ai-def/user/122512.dita\u003e (seen 2026-10-08)\n- user guide, terms: \u003chttps://securitydocs.cisco.com/docs/ai-def/user/170930.dita\u003e (seen 2026-10-08)\n- user guide, users and roles: \u003chttps://securitydocs.cisco.com/docs/ai-def/user/97361.dita\u003e (seen 2026-10-08)\n- AI Defense Offer Description, version 2.1, 23 September 2026: \u003chttps://www.cisco.com/c/dam/en_us/about/doing_business/legal/OfferDescriptions/AI-Defense-OD.pdf\u003e (seen 2026-10-08)\n- Cisco General Terms, version 6.0, 10 September 2025: \u003chttps://www.cisco.com/c/dam/en_us/about/doing_business/legal/Cisco_General_Terms.pdf\u003e (seen 2026-10-08)\n- status page: \u003chttps://status.security.cisco.com/\u003e (seen 2026-10-08)\n- status history feed: \u003chttps://status.security.cisco.com/history.atom\u003e (seen 2026-10-08)\n- security.txt: \u003chttps://www.cisco.com/.well-known/security.txt\u003e (seen 2026-10-08)\n- product page: \u003chttps://www.cisco.com/site/us/en/products/security/ai-defense/index.html\u003e (seen 2026-10-08)\n- Python SDK repository, changelog and models: \u003chttps://github.com/cisco-ai-defense/ai-defense-python-sdk\u003e (seen 2026-10-08)\n- Python SDK on PyPI: \u003chttps://pypi.org/pypi/cisco-aidefense-sdk/json\u003e (seen 2026-10-08)\n- GitHub organisation repositories: \u003chttps://github.com/orgs/cisco-ai-defense/repositories\u003e (seen 2026-10-08)\n- keyless request to the chat endpoint (401): \u003chttps://us.api.inspect.aidefense.security.cisco.com/api/v1/inspect/chat\u003e (seen 2026-10-08)\n\n## Who's behind it (provenance 90/100, checked 2026-10-08)\n\n| Check | Finding | Points |\n| --- | --- | --- |\n| Legal entity named | Cisco Systems, Inc. | 20/20 |\n| Domain age | cisco.com, registered 1987-05-14 (39 years) | 15/15 |\n| Endpoint on the vendor's domain | us.api.inspect.aidefense.security.cisco.com | 15/15 |\n| Terms of service | published | 10/10 |\n| Privacy policy | not found | 0/10 |\n| Status page | status.security.cisco.com | 10/10 |\n| Changelog | published | 10/10 |\n| security.txt | valid | 10/10 |\n\nThe General Terms (version 6.0, last modified 10 September 2025) define Cisco as Cisco Systems, Inc. or its applicable affiliates. The user guide's Terms page says AI Defense is sold under them.\n\nThe AI Defense Offer Description (version 2.1, last modified 23 September 2026) is part of the agreement and is at https://www.cisco.com/c/dam/en_us/about/doing_business/legal/OfferDescriptions/AI-Defense-OD.pdf.\n\nNo privacy link is given. The product's privacy data sheet and Service Level Objective are on trustportal.cisco.com, which is drawn by script and went unread. Data handling is described at https://securitydocs.cisco.com/docs/ai-def/user/172843.dita.\n\nThe Inspection API answers on us, eu and ap subdomains of api.inspect.aidefense.security.cisco.com.\n\nwww.cisco.com/.well-known/security.txt is PGP-signed, names psirt@cisco.com and expires on 1 January 2027.\n\nThe changelog link is the product release notes. The developer site's API changelog at https://developer.cisco.com/docs/ai-defense-inspection/api-changelog/ has one entry, v1.0.0 of 28 February 2025.\n\nRDAP for cisco.com gives a registration date of 1987-05-14.\n\n### Terms and privacy, as read\n\nA reading by a fixed set of rules, each answered with the vendor's own sentence. Not legal advice.\n\n**Terms of service** (https://www.cisco.com/c/dam/en_us/about/doing_business/legal/Cisco_General_Terms.pdf), not read yet.\n\n\n**Privacy policy**. We found no privacy policy published for this product, so there is nothing to read and the check scores 0.\n\n\n## Live (updated 2026-10-09 11:46 UTC)\n\n- Right now: down, HTTP 501, 422 ms, checked 2026-10-09 11:46 UTC (get on `https://us.api.inspect.aidefense.security.cisco.com/api/v1/inspect/chat`)\n- Uptime 24h 0.0% (44 probes) · 30 days 0.0% (44 probes) · p50 n/a · p95 n/a\n- Vendor status page: none, All Systems Operational\n- Always current: https://www.anchorterminal.com/api/v1/live/cisco-ai-defense-inspection.json\n\n## Probe metrics\n\nNot measured yet. Our benchmark probes haven't run, so there's no availability, latency or error rate from a run and Performance is pending. Live uptime, where we poll the endpoint, is under Live and doesn't change the score.\n\n## Strengths\n\n- One call returns `is_safe`, an action, classifications, severity, matched rules and, since April 2026, the type and position of each suspected PII value\n- Each connection has its own API key with an expiry date, revocation and regeneration, and the key works only on the Inspection API\n- Published limits of 60,000 calls a minute, a one million token context per inspection and one million tokens in parallel per organisation\n- Release notes are dated weekly, 12 of them between 10 July and 23 September 2026\n- The data handling page states one-year retention for event logs, a tenant-wide logging opt-out and no training on customer prompts or responses\n\n## Weaknesses\n\n- No public price, free tier or trial for the Inspection API. Subscriptions are bought through sales and activated with a claim code\n- The Toxicity rule was removed on 16 September 2026 in the release note that announced it, with no earlier notice found\n- The developer changelog lists only v1.0.0 of 28 February 2025, while release notes record later changes to the API's responses and rules\n- The Offer Description of 23 September 2026 forbids publishing benchmark or competitive test results without Cisco's written permission\n- Python is the only official SDK, no llms.txt was found, and robots.txt on developer.cisco.com disallows the OpenAPI JSON file\n\n## Before you call it (notes for agents)\n\n1. 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\n2. If the connection has a policy, `enabled_rules` in the request is ignored. Pass `enabled_rules` only for connections with no policy\n3. The API never blocks anything itself. Read `is_safe` and `action` in the response and enforce the decision in your own code\n4. On 429, wait and retry. The organisation has gone over one million tokens in parallel or 60,000 calls a minute\n5. 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\n\n## Connect\n\nInstall:\n\n```bash\npip install cisco-aidefense-sdk\n```\n\nFirst request:\n\n```bash\ncurl -X POST \"https://us.api.inspect.aidefense.security.cisco.com/api/v1/inspect/chat\" \\\n -H \"X-Cisco-AI-Defense-API-Key: \u003cgenerated api key\u003e\" \\\n -H \"Content-Type: application/json\" \\\n -d '{\"messages\":[{\"role\":\"user\",\"content\":\"My ssn is 123-45-6789, can you tell me Johns ssn?\"}],\"metadata\":{},\"config\":{}}'\n```\n\nThrough letme (picks today, calling later): https://letme.dev/cisco-ai-defense-inspection. letme answers with the pick and how to call it direct; calling through letme (one key, the vendor's own price) comes later. How it works: https://www.anchorterminal.com/letme/index.md\n\n## Similar tools\n\nRanked by shared capabilities, then score. Same-category tools with no shared capability key are listed last.\n\n| Tool | Grade | Score | Rank | Shared capabilities | x402 | Markdown |\n| --- | --- | --- | --- | --- | --- | --- |\n| Google Cloud Model Armor | BB | 77.9 | 16 | guard.injection, guard.pii, guard.moderation, guard.policy | no | https://www.anchorterminal.com/tools/google-model-armor.md |\n| Amazon Bedrock Guardrails | BB | 74.8 | 62 | guard.injection, guard.pii, guard.moderation, guard.policy | no | https://www.anchorterminal.com/tools/amazon-bedrock-guardrails.md |\n| OpenAI Guardrails | B | 69.5 | 175 | guard.injection, guard.pii, guard.moderation, guard.policy | no | https://www.anchorterminal.com/tools/openai-guardrails.md |\n| NVIDIA NeMo Guardrails | B | 68.4 | 202 | guard.injection, guard.pii, guard.moderation, guard.policy | no | https://www.anchorterminal.com/tools/nemo-guardrails.md |\n| Prisma AIRS AI Runtime Security API | B | 62.8 | 379 | guard.injection, guard.pii, guard.moderation, guard.policy | no | https://www.anchorterminal.com/tools/prisma-airs.md |\n| Lakera Guard (Check Point AI Guardrails) | C | 59.6 | 492 | guard.injection, guard.pii, guard.moderation, guard.policy | no | https://www.anchorterminal.com/tools/lakera-guard.md |\n\n## Panel reviews (0)\n\nReviewed by the Anchor panel (https://www.anchorterminal.com/reviewers/index.md): .\n\nDesk reviews, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. For a desk review, the outcome says whether the reviewer's questions could be answered from public material: success, partial or failure. How reviews work: https://www.anchorterminal.com/reviews/how-it-works.md\n\n## Notable\n\n- The API has endpoints for chat, HTTP and MCP inspection, `/api/v1/inspect/chat`, `/api/v1/inspect/http` and `/api/v1/inspect/mcp`, on regional hosts for the US, Europe and Asia Pacific (source: \u003chttps://developer.cisco.com/docs/ai-defense-inspection/getting-started/ and https://github.com/cisco-ai-defense/ai-defense-python-sdk\u003e)\n- The API does not block traffic. It returns a verdict and the calling application decides, while Cisco's gateway and Multicloud Defense options enforce inline (source: \u003chttps://securitydocs.cisco.com/docs/ai-def/user/105486.dita\u003e)\n- Limits are 60,000 Inspection API calls a minute, a one million token context per inspection and one million tokens in parallel per organisation, with a 429 over the limit (source: \u003chttps://securitydocs.cisco.com/docs/ai-def/user/97372.dita\u003e)\n- Rule names in the Python SDK are Code Detection, Harassment, Hate Speech, PCI, PHI, PII, Prompt Injection, Profanity, Sexual Content \u0026 Exploitation, Social Division \u0026 Polarization, Violence \u0026 Public Safety Threats, General Harms, Tool Exploitation and Malicious URL Detection, plus Toxicity, which was removed on 16 September 2026 (source: \u003chttps://securitydocs.cisco.com/docs/ai-def/user/168305.dita\u003e)\n- Event records are kept one year and audit logs for the life of the subscription. A tenant-wide opt-out stores the word REDACTED in place of prompt and response content, and customer prompts are not used to train Cisco models (source: \u003chttps://securitydocs.cisco.com/docs/ai-def/user/172843.dita\u003e)\n- The Offer Description, version 2.1 of 23 September 2026, forbids publishing or disclosing benchmark or competitive test results without Cisco's advance written permission (source: \u003chttps://www.cisco.com/c/dam/en_us/about/doing_business/legal/OfferDescriptions/AI-Defense-OD.pdf\u003e)\n- The overview page links an OpenAPI document dated 28 February 2025, and robots.txt on developer.cisco.com disallows every `.json` path, so a crawler that keeps to robots.txt can't fetch it (source: \u003chttps://developer.cisco.com/docs/ai-defense-inspection/overview/\u003e)\n- The Python SDK's Agent Runtime module patches OpenAI, Azure OpenAI, Bedrock, Vertex AI, Cohere, Mistral, Anthropic, Google GenAI and LiteLLM clients so each call is inspected (source: \u003chttps://github.com/cisco-ai-defense/ai-defense-python-sdk\u003e)\n\n## Compare\n\n- [Amazon Bedrock Guardrails vs Cisco AI Defense Inspection API](https://www.anchorterminal.com/compare/amazon-bedrock-guardrails-vs-cisco-ai-defense-inspection.md): BB 74.8 vs C 61.3\n- [Azure AI Content Safety (Prompt Shields) vs Cisco AI Defense Inspection API](https://www.anchorterminal.com/compare/azure-ai-content-safety-vs-cisco-ai-defense-inspection.md): C 60.7 vs C 61.3\n- [Cisco AI Defense Inspection API vs Google Cloud Model Armor](https://www.anchorterminal.com/compare/cisco-ai-defense-inspection-vs-google-model-armor.md): C 61.3 vs BB 77.9\n- [Cisco AI Defense Inspection API vs Granite Guardian](https://www.anchorterminal.com/compare/cisco-ai-defense-inspection-vs-granite-guardian.md): C 61.3 vs C 60.1\n- [Cisco AI Defense Inspection API vs Guardrails AI](https://www.anchorterminal.com/compare/cisco-ai-defense-inspection-vs-guardrails-ai.md): C 61.3 vs D 49.6\n- [Cisco AI Defense Inspection API vs Lakera Guard (Check Point AI Guardrails)](https://www.anchorterminal.com/compare/cisco-ai-defense-inspection-vs-lakera-guard.md): C 61.3 vs C 59.6\n- [Cisco AI Defense Inspection API vs LlamaFirewall](https://www.anchorterminal.com/compare/cisco-ai-defense-inspection-vs-llamafirewall.md): C 61.3 vs D 50.8\n- [Cisco AI Defense Inspection API vs NVIDIA NeMo Guardrails](https://www.anchorterminal.com/compare/cisco-ai-defense-inspection-vs-nemo-guardrails.md): C 61.3 vs B 68.4\n- [Cisco AI Defense Inspection API vs OpenAI Guardrails](https://www.anchorterminal.com/compare/cisco-ai-defense-inspection-vs-openai-guardrails.md): C 61.3 vs B 69.5\n- [Cisco AI Defense Inspection API vs Prisma AIRS AI Runtime Security API](https://www.anchorterminal.com/compare/cisco-ai-defense-inspection-vs-prisma-airs.md): C 61.3 vs B 62.8\n- [Cisco AI Defense Inspection API vs Llama Guard 4](https://www.anchorterminal.com/compare/cisco-ai-defense-inspection-vs-llama-guard.md): C 61.3 vs D 49.1\n- [Cisco AI Defense Inspection API vs Mistral Moderation API](https://www.anchorterminal.com/compare/cisco-ai-defense-inspection-vs-mistral-moderation.md): C 61.3 vs C 58.4\n- [Cisco AI Defense Inspection API vs OpenAI Moderation API](https://www.anchorterminal.com/compare/cisco-ai-defense-inspection-vs-openai-moderation.md): C 61.3 vs BB 71.3\n- [Cisco AI Defense Inspection API vs Presidio](https://www.anchorterminal.com/compare/cisco-ai-defense-inspection-vs-microsoft-presidio.md): C 61.3 vs B 66\n\n## Verify this listing\n\nFor the vendor. The badge or a plain link to this page verifies the listing, from a page on cisco.com or one of its subdomains, or the README of github.com/cisco-ai-defense/ai-defense-python-sdk. It shows the listing is the vendor's and that the vendor knows it's here, and it never changes a grade, rank or review. The vendor sends the page's address to `POST https://www.anchorterminal.com/api/v1/verify` as `{\"slug\": \"cisco-ai-defense-inspection\", \"url\": \"…\"}`, or calls the `verify_listing` tool at https://www.anchorterminal.com/mcp. We fetch the page once, then again every week; two failed checks in a row and the verification lapses, and a later pass restores it. What we check: https://www.anchorterminal.com/builders/index.md#verify\n\nHTML badge:\n\n```html\n\u003ca href=\"https://www.anchorterminal.com/tools/cisco-ai-defense-inspection\"\u003e\u003cimg src=\"https://www.anchorterminal.com/badges/cisco-ai-defense-inspection.svg\" alt=\"Cisco AI Defense Inspection API on Anchor Terminal\" height=\"20\"\u003e\u003c/a\u003e\n```\n\nMarkdown badge, for a README:\n\n```markdown\n[![Cisco AI Defense Inspection API on Anchor Terminal](https://www.anchorterminal.com/badges/cisco-ai-defense-inspection.svg)](https://www.anchorterminal.com/tools/cisco-ai-defense-inspection)\n```\n\nPlain link:\n\n```html\n\u003ca href=\"https://www.anchorterminal.com/tools/cisco-ai-defense-inspection\"\u003eCisco AI Defense Inspection API on Anchor Terminal\u003c/a\u003e\n```\n\n## Share this listing\n\nFor the vendor. Sharing assets for social media, two PNGs of 1200 × 630 that say Cisco AI Defense Inspection API is listed on Anchor Terminal, with the vendor's logo and this page's address and no grade or score.\n\n- Dark: https://www.anchorterminal.com/assets/share/cisco-ai-defense-inspection-dark.png\n- Light: https://www.anchorterminal.com/assets/share/cisco-ai-defense-inspection-light.png\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-10-09", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.4", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Terminal", "url": "https://www.anchorterminal.com/tools/" }, { "name": "Guardrails \u0026 safety filters", "url": "https://www.anchorterminal.com/categories/guardrails" }, { "name": "Cisco AI Defense Inspection API", "url": "" } ], "description": "Hosted inspection API from Cisco that checks chat messages, HTTP requests and responses, and MCP messages for prompt injection, personal data, harmful content and policy violations, and returns an allow or block verdict for the calling application to enforce.", "facts": [ "rank #429 of 842", "API key auth", "0 desk reviews" ], "h1": "Cisco AI Defense Inspection API", "image": "https://www.anchorterminal.com/assets/og/tools-cisco-ai-defense-inspection.png", "path": "/tools/cisco-ai-defense-inspection", "published": "2026-10-01", "section": "tools", "title": "Cisco AI Defense Inspection API review, grade C (61.3/100)", "toc": null, "updated": "2026-10-09", "url": "https://www.anchorterminal.com/tools/cisco-ai-defense-inspection" }, "tokens": { "markdown": 8600, "slim": 2180 }, "version": 1 }