Connect your AI agents to Quorai

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

This page is for you and for the assistant helping you set up: what works today, what is coming, and what stays with a person.

What works today

1. 1

   Sign in with an invitation

   Quorai is invite-only today. You sign in with the work account an owner of your organization invited, or one from an email domain your organization has set up. Without either, sign-in is refused.

2. 2

   Open the guided setup

   In the console, Connect has a guided setup. It walks you through registering an agent, setting its key where the agent runs, and making its first call.

3. 3

   Or hand the steps to your assistant

   On the same screen, Copy instructions gives you setup text written for an assistant, for your organization. It carries no key or token. When a step needs one, it tells your assistant to stop and ask you, and to have you set it as an environment variable rather than paste it into the chat.

4. 4

   Point your agent at Quorai

   An agent is governed once its model calls go to Quorai with its own Quorai key. A call that needs approval is held and waits for a person. To undo, point the agent back.

Coming, not available yet

• A connector you add in Claude or ChatGPT. You would sign in and approve what it may do on a Quorai consent screen. It would read only at first.
• Sign-in with a link sent to your email, for people without a Google or Microsoft account.
• A trial organization created at your first sign-in, so you would not need an invitation.
• Setup help your assistant can run through the connector: check your setup, tell you the next step, register agents in a test stage, and draft a first policy as a preview, saved switched off.
• Your agent's key sent to you by a one-time link, never to your assistant.

Until these ship, there is no connector address to add in Claude or ChatGPT. An assistant that offers one is guessing.

What stays with a person

These are the decisions Quorai exists to keep with people. Today an agent's own Quorai key is refused by every one of them, and so is a read-only token. The connector is being built so that it cannot do them either.

• Approving or denying an action Quorai held for a person.
• Naming who may approve.
• Giving anyone the owner or operator role. Only an owner can, and an operator cannot either.
• Moving an agent to production, where it has full authority, or registering one there. Only an owner signed in to the console can. An operator cannot, and neither can an owner's API token.
• Turning a policy on. Today policies are shared across Quorai and set by the Quorai team, so not even an owner in your organization can change one yet.
• Loosening a policy: switching it off, changing its setting, or changing which team it covers. Today that is also the Quorai team's change, not your owner's.
• Seeing an agent's key. Quorai shows a key once, whenever it issues one: when an agent is registered, when a request for an agent is approved, when a key is rotated, and when an agent is reinstated after quarantine. It keeps only a hash. Anyone with the operator or owner role can do these and see the new key, so do them in the console yourself, and your assistant does not see it.

Limits worth knowing

• Quorai checks the credential, not who holds it. A person's API token acts with that person's role, so an assistant you give an owner or operator token can do what that role can. An operator token is enough to register agents, and it cannot give anyone a role, but it can rotate any agent's key and read the new one.
• An agent you register without a stage starts in dev, through the API, the console or an approved request. In dev it can read and draft, and any write, spend, send or delete is refused and recorded. Only an owner signed in to the console can register an agent as prod, which skips the evaluation, or move one there. To move one: record a passing evaluation for its current configuration with POST /api/agents/{id}/evals (suite, passed and total; at least 90 percent passed, less than 7 days old), then an owner moves it to prod on the agent's record in the console.
• Spending budgets are your organization's own. An owner or operator can set, raise or remove one, and so can an assistant holding their token.
• An agent whose model calls do not go through Quorai is observed at most, never governed. Quorai cannot hold a call it never sees.

For agents

The same text is at /llms.txt.

# 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