Zerq Copilot
Natural language for the control plane—and for everyone you serve through the portal
Zerq Copilot is one product with two governed experiences. Zerq Copilot for Management helps platform and operations teams configure and run the gateway through Management MCP. Zerq Copilot for Gateway helps API consumers explore and validate published APIs through the Developer Portal and Gateway MCP. Same conversational patterns, your choice of model provider, and enforcement that never moves out of band.
Operations & platform engineering
Zerq Copilot for Management
Embedded alongside your day-to-day work in the Zerq console. Ask for status, apply changes, and orchestrate workflows using ordinary language—backed by the same APIs and permissions your team already trusts. No parallel login, no shadow configuration path.
How it works
Intent, not incantations
Describe outcomes in everyday language. Copilot maps your request to Management MCP actions using your signed-in session—no query language and no separate toolchain.
Full platform scope
Collections, proxies, workflows, policies, clients, credentials, audit history, and metrics—the same breadth as the graphical console. Create, inspect, or retire resources without tab-hopping.
Your models, your keys
OpenAI, Anthropic, Google, Groq, Azure OpenAI, Amazon Bedrock, Ollama, OpenRouter, or any OpenAI-compatible endpoint. Configured server-side; credentials never ship to the browser.
Identity-native guardrails
Every action runs under your OIDC session. Viewers read; editors change; administrators govern. The same role model as the rest of Zerq—nothing bypasses the control plane.
Where teams start
Representative prompts—your governance and retention policies still apply.
Ship a product end-to-end
Stand up a collection, wire proxies, attach a workflow, assign a policy, and publish—in one thread. Example: “Create Payments, add POST /payments, cap traffic at 500 RPM, and show me what changed.”
Triage incidents faster
Correlate errors, latency, and recent traffic without switching contexts. Example: “Why are 502s spiking on /orders? Pull the last failed calls and summarize.”
Onboard partners cleanly
Create clients, bind policies, configure profiles, and rotate credentials with explicit narration before destructive steps. Example: “New client for Partner X on the Standard policy with JWT.”
Model choice without lock-in
Configure providers once per environment. Swap models when your roadmap or policy changes—no image rebuild required. Keys remain on the server.
Partners & product consumers
Zerq Copilot for Gateway
An optional assistant inside the Developer Portal for teams integrating against your published APIs. It mirrors the conversational patterns of operations Copilot while remaining strictly consumer-scoped: only assigned products, only profile credentials, only what the gateway would allow for a real client.
How it works
Discovery through conversation
Partners ask what they need in plain language. Copilot invokes Gateway MCP—list collections and endpoints, inspect contracts, execute safe test calls—within the APIs they are entitled to use.
Credentials that match production
Uses the active access profile’s gateway identity—the same headers as the interactive test console and external MCP clients—so validation matches real traffic.
Consistent model strategy
Reuse the same server-side LLM configuration (`AI_MODELS`) as operations Copilot. One policy for model choice, key custody, and provider review.
The gateway stays authoritative
Every tool call is subject to rate limits, RBAC, and audit, identical to any other client. The model cannot widen scope or skip enforcement.
See Zerq Copilot on your roadmap
Shipped with the Zerq enterprise platform. Pair secure LLM configuration with a single conversational layer for operators and partners—without compromising auditability.