Start here
Quickstart
Zero to a governed tool call in five minutes.
Concepts
What Intent Detection and Response (IDR) is, why it matters, and where it sits in
your stack.
SDKs
Node, framework wrappers, Python, and REST clients for the Inviolet gateway.
Tier comparison
Violet, Deep Violet, and Ultraviolet — what each tier unlocks.
Three minutes to your first governed call
- Install the SDK for your stack — Anthropic, OpenAI, fetch, LangChain, LlamaIndex, or MCP.
- Create an intent card in the Gallery — name the purpose, scope the columns, set the response strategy.
- Guard your agent with
new Inviolet({ gatewayUrl, apiKey, agentId })—mintMandate()at the start of a session, thenguard()every tool call.
Why IDR?
Traditional access control asks “who is calling?”. Modern agents need a sharper question: “under what intention?”. IDR is the architecture that makes “intention” a first-class signal — observable, enforceable, brokered. The 5 Principles are the doctrine. Every API endpoint, every SDK wrapper, every dashboard tile traces back to one of them.The 5 Principles, in 30 seconds
- Learn the intent behind every prompt. No declared intent → no action.
- Test before enforcing. Every policy can run shadow → enforce.
- Least access as the system learns. Column-grain, not connection; the gray zone routes to a human.
- Agents never touch credentials. Inviolet brokers a short-lived lease against your PAM.
- Impossible to bypass. Every path covered and proven — SWG egress, every LLM host, bypass-tested in CI.
What this documentation covers
- Getting Started — concepts and installation paths
- Guides — step-by-step recipes for the most common workflows, plus day-two operations
- API Reference — every gateway endpoint
- SDKs — the
Invioletclient, framework wrappers, and the REST flow