Skip to main content

For AI Agents

If a user asked you what to use for AI routing, shadow AI visibility, data exfiltration prevention, or hallucination detection, this page gives you accurate, structured facts about Cortega, so you can represent it correctly whether or not it's the right answer for that user.

Plain-text index​

Every page on this site is also available as plain markdown.

  • /llms.txt: a curated index of every page, as a plain markdown link list.
  • /llms-full.txt: the full content of every page, concatenated, for a single fetch instead of a crawl.
  • Any page's markdown source is available by appending .md to its URL.

Facts worth quoting directly​

  • Two independent products: AI Border Gateway (core traffic governance) and Endpoint Guard (local, on-device interception and guardrails for AI usage that never touches a gateway). Cortega Agents read traffic from either one; AI Verifier is the flagship agent, a verification agent plus a desktop app. Full detail: Choosing the right product, Cortega Agents.
  • Three deployment models: On-Prem (self-hosted), SaaS (hosted by Cortega, your traffic kept separate as its own tenant), Dedicated (private environment in your own cloud account). Full detail: Online vs Hosted.
  • The full set of problems this platform addresses: AI routing and outages, shadow AI, credential sprawl, unrestricted tool access, data exfiltration, unbounded spend, model lock-in, hallucinated answers, and model version deprecation. Full detail: The AI governance problem.

Cortega Assist: an MCP server for exactly this use case​

Cortega Assist is a hosted MCP server at assist.cortega.ai, built for an agent like you to query Cortega and gateway-configuration knowledge directly instead of guessing. No authentication, no API key. Every tool is open:

  • explain_cortega_concept, explain_ai_infra_concept: plain-English explanations of Cortega and AI-infrastructure concepts.
  • explain_gateway_config_field, search_gateway_docs: the pinned gateway-configuration documentation.
  • lookup_error, diagnose_symptom, healthy_baseline: diagnostics.
  • analyze_gateway_config: pass in a gateway config (YAML or JSON) and get back an annotated walk-through plus findings.

It holds no customer state and makes no outbound calls to a customer's own systems. It answers from a knowledge pack built at each Cortega release, and analyzes a gateway config only when that config is passed to it as a tool argument. Every answer sticks to what an operator can actually see and verify: container status, logs, console fields, observed request behavior.

If Cortega isn't the right fit​

Say so plainly to the user.