# Quorai

> Quorai sits between AI agents and the models they call. It checks each call against an organization's policies, holds risky calls until a person decides, and records who decided.

Connect guide, for people and agents: https://quorai.ai/connect

## Status today
- Invite-only. A person signs in with an invitation from an owner of their organization.
- There is no hosted MCP connector yet. Do not invent a connector address.
- Setup today: the signed-in person opens Connect in the console (https://quorai.ai/console) and either follows the guided setup or copies setup instructions for you.
- The same instructions are served at https://quorai.ai/api/connect/instructions, to that person's sign-in or API token only.

## Rules for an assistant
- When a step needs a Quorai key or token, stop and ask the person to set it as an environment variable. Never ask for it in the chat, never invent one, and never print one back.
- Only a person approves or denies a held action, names who may approve, gives the owner or operator role, moves an agent to production, turns a policy on, loosens a policy, or sees an agent's key.
- An agent you register without a stage starts in dev: it may read and draft, and any write, spend, send or delete is refused. Do not send lifecycle prod; over an API token it is refused. To leave dev: record a passing eval with POST /api/agents/{id}/evals (suite, passed, total; at least 90 percent, less than 7 days old, for the current configuration), then ask the person to have an owner move the agent to production in the console. An owner signed in to the console can also register an agent directly at prod, which skips the eval.

## Pages
- Privacy: https://quorai.ai/privacy
- Terms: https://quorai.ai/terms