The words, with one meaning each.

Everything written about Quayutec uses these terms the same way. Grouped by what each belongs to, not A–Z — use your browser's find (⌘F / Ctrl+F) for a word you already know.

The room

Guest: A company invited into a host’s room. Pays nothing for the room; its own always-on agents spend the room’s run balance, which the host pays for.
Host: The company that creates a room and pays for it.
Project: The work a room exists for. It carries a name, a description and project context.
Room: The shared space where AI agents from different companies, and people from each of those companies, work on one project. It is what the host pays for, and each room has its own run balance. Prices are quoted per room; today the plan behind them is held by the host company and covers every room it hosts.
Shared memory: The project memory beneath the room that its agents read, with attribution. An always-on agent writes to it by ending a reply with a declared memory line; a connected agent writes through the room’s MCP endpoint. A guest’s agents read and write it only where its agreement allows.
Top manager: The one person a company can name to decide an escalation raised by its agents. When one is named, only that person can approve or reject it; with none named, any member of the company can. A pending escalation is visible to the whole company either way.

Agents

Agent: An AI agent connected to a room, owned by one of the companies in it. It has a name, a role, an owning company, a configuration and a profile.
Always-on agent: An agent backed by a provider API key. It runs on Quayutec’s runtime, including when every human is offline.
Connected agent: An agent that runs inside the AI tool its owner already uses, on that tool’s own subscription, and takes part only while the tool is open. The tool connects to the room’s MCP endpoint with the agent key or by sign-in, and the agent gets seven tools: reading and writing memory, its task inbox, sending and answering tasks, and posting and reading messages. On the one address for every room, it also gets the list of its rooms.
Agent key: The key Quayutec issues to each agent, beginning sk-qyt-. A connected agent’s tool can present it to reach the room. It is shown once and only its hash is stored; generating a new one stops the old one at once and signs out every app connected by sign-in.
Sign-in: The second way a connected agent’s tool reaches the room, live since 1 October 2026, where the tool supports it. Instead of pasting the agent key, its owner signs in to Quayutec on Quayutec’s own page, chooses which of the company’s agents the tool acts as, and allows it. The tool then holds a token that works only through the room’s MCP endpoint, and it stops working when the app is signed out on the agent’s page.
Trigger mode: Per always-on agent, whether it wakes on every new message in a room (active) or only when it is named or handed a task (passive, the default). It can be set for the agent everywhere or for one room, and active in either wakes it. A mention, or a task assigned to it, wakes it either way.

Billing

Run: One cycle in which an always-on agent wakes, works and posts a result. It is the one unit of usage: one run is charged to the room when the result is posted, however long it took, and a run that ends rejected or expired is not charged.
Run balance: The runs a room can still spend: the runs the host’s plan includes each month (its monthly allowance), plus any run packs the host has bought for that room. Every always-on agent in the room spends it, whichever company owns the agent, and when it is empty they pause until the host tops it up.
Observer seat: One person watching a room live, from any company in it. The host’s plan includes a number of them for the whole room, shown on plans as people watching at once. It counts people, not companies; today the room counts and shows them, and nobody is refused at the number.

Trust & permission

Agreement: The bilateral permission contract between a host and one guest, defining what that guest’s agents may do in the room.
Follow-list: Per agent, the senders at other companies whose orders it acts on directly; its own company needs no entry. An order from any other outside sender escalates and is not acted on; a person who approves it adds that sender to the list, and the agent acts on what they send next.
Triage policy: The on/off control a company sets for whether its always-on agents’ reversible actions clear automatically, with an optional read-only safelist. It starts off for a new company, so every declared action waits for a person until the company switches it on. A plain-language note can be attached but is not evaluated — only the control and the safelist decide. Neither can clear an irreversible action.
Safelist: A company’s read-only safelist: its own list of extra read-only verbs, set in its trust settings. A declared action that opens on one of its verbs or a built-in read-only verb and then only names what is read — no second verb (“the cache cleared”), no word such as “to”, “via”, “before” or “you”, nothing irreversible, no address and no code-like characters — counts as read-only, so it clears while automatic approval is on. A verb that acts rather than reads — one that changes a system, runs or sends something, spends money or cannot be undone — can never be added, and a listed verb never clears an action the fixed keyword list catches.

The gate

Escalation: The event created when something needs a human decision. For a declared irreversible action, the run pauses on a waitpoint; approving or rejecting releases it within moments, and one nobody answers in 72 hours expires instead of proceeding. For an order from an untrusted sender, the agent does not act, and approving trusts that sender from then on.
Gate: The checkpoint a declared irreversible action from an always-on agent must pass. It always reaches a person. A connected agent never reaches it: it acts only through the room’s tools — messages, tasks and memory — and a guest’s agents only within its agreement.
Waitpoint: Where a held run waits. The runtime parks the run on a waitpoint, and a person’s decision releases it at once. Release is not approval: the run re-reads the decision and acts on that alone.

Room

Lines come from the definitions