Glossary¶
The words used on screen and in these docs, defined once. Labels in bold are exactly as the Control room shows them.
A¶
| Word | What it means |
|---|---|
| Access review | A regular check of every role and key: keep what's still needed, revoke the rest. The result becomes evidence. See Access reviews and incidents. |
| Adjustment | A late call or a correction that belongs to a locked billing period, counted on the first open day instead of changing the locked one. See Cost. |
| Agent | A program that calls models on its own, with its own keys, owners and someone to ask. Agents never sign in and have no email. See Applications and agents. |
| Alias | An extra name for a model. An alias is its model everywhere: access, prices, routing and logs. See Model names and aliases. |
| API token | A credential for managing Vidai from code, held by a person (a personal access token) or a service account. Not for AI calls: those use a key. See Service accounts and API tokens. |
| Application | A system you run that groups agents: who pays, its documentation, whether it talks with your clients. See Applications and agents. |
| Approvals | The page where changes that widen someone's own reach, and group admins' requests to lift a budget or guardrail, wait for someone who may decide them. Nobody decides their own request; a sole organisation admin is never stuck. See Exceptions, overrides and approvals. |
| Approved for use | The organisation's list of the only models any call may reach. Every rule works inside it. See Regions and data residency. |
| Audit log | The record of every change, sign-in, content read, key reveal, download and safety switch, with who did it and why; tamper-evident. See Audit log. |
| Auditor report Enterprise | One signed file for a period: calls (a sample or all), audit events, the policies in force, and the seals, which an auditor checks on their own machine. See Tamper evidence. |
B–C¶
| Word | What it means |
|---|---|
| Billing lock | On Money › Cost › Billing periods: every day up to a chosen day made final, with a reason. Locked days never change; anything that reaches them later comes in as an adjustment. See Cost. |
| Budget | A limit on spend, in one currency, on a level and a period. It can notify, stop calls at the limit, or send calls to another model. See Budgets. |
| Call | One request through the gateway to a model, and its record in Request logs. See Request logs and the call record. |
| Charged | What a call costs its team: the list price plus any markup. See Cost. |
| Circuit | The gateway's per-model switch that stops sending calls to a model that keeps failing, rests it for at least 30 seconds, then tests it with one call. See Provider keys and resilience. |
| Compliance officer Enterprise | A role that reads what an organisation viewer reads and runs policies, regulations, risk and evidence. See People and roles. |
| Compliance route | A routing rule that always sends a model to a set deployment, beats every other routing rule and allows no exemptions. See Routing and fallback. |
| Content reader | The only role that may read what calls sent and got back. Every read, and every refused try, is recorded. See People and roles. |
| Control room | Vidai's console: where you set the rules, watch the traffic, see the cost and produce the evidence. See The parts. |
| Coverage | How much of a regulation what's in force answers, control by control: Enforced, Observed only, Partly, Nothing in place, Not checked or Your organisation's process. Never "compliant": your auditor decides. See Policies and regulations. |
E–F¶
| Word | What it means |
|---|---|
| Edition | Community or Enterprise. What Enterprise includes depends on the features your licence includes. See Editions and licences. |
| Environment | Where a key is issued: production, staging and others, each with its own rules on who may issue keys, how long they live and which models they reach. The Default environment is always there. See Environments. |
| Evidence pack Enterprise | One file for a regulator: your AI systems, policies and changes, oversight, incidents, retention and the last access review. See Tamper evidence. |
| Emergency override | An exception that lifts a budget, a guardrail or every guardrail of a policy, for one key or everything it covers, for 1 to 24 hours; it ends by itself. An organisation admin's own is Self-approved; a group admin asks on Approvals. Never lifts a compliance route or the approved destinations. See Exceptions, overrides and approvals. |
| Exception | Any named way out of a rule for one key or one person: an exemption, an emergency override, or extra models for one person. Each has a reason and is recorded with who asked and who agreed; an override always ends, an exemption's end is optional. See Exceptions, overrides and approvals. |
| Exemption | One key let off a required routing rule or a guardrail, with a reason and an optional end date. A compliance route can't be exempted from. See Exceptions, overrides and approvals. |
| Fallback chain | The models to try instead, in order, when a model is resting or a call fails; always before anything reaches the caller. See Routing and fallback. |
| Finance | A role for cost, prices and budgets across the organisation, without admin rights. See People and roles. |
| Finding | What a guardrail's checks found in a call, with what was done about it. See Guardrails. |
G–K¶
| Word | What it means |
|---|---|
| Gateway | The part of Vidai your programs call. It checks each call against your rules, sends it to a provider and records it. See The parts. |
| Group admin | Runs a team and every team under it: people, keys, agents, applications, their calls and cost. See People and roles. |
| Guardrail | A rule on what a call may contain. Its checks find something; it then blocks, redirects, pseudonymises, masks or logs only. See Guardrails. |
| Held change | A rate-card price that moved a lot (3× or more by default) and waits for an organisation admin or Finance to accept or reject it. See Prices and the rate card. |
| Key | What a program holds to call models through the gateway. It belongs to a person or an agent, is issued in an environment, and acts for one team (or for an agent and one of its applications), which decides who pays. See Keys. |
L–O¶
| Word | What it means |
|---|---|
| Legal hold | Hold every record: nothing is deleted, whatever the retention, until the hold is lifted. See Retention, legal hold and subject requests. |
| Level | Where a rule or role is set: the organisation, an environment, a team, an application, an agent or a key. A rule reaches everything below its level. See Rules at levels. |
| Markup | What a team is charged above (or below) the provider's price, set on Money › Cost › Markups for the organisation, a provider or a team; the most specific wins. See Cost. |
| Model access | Which models a team, environment or agent may call. See Model access. |
| Needs attention | The things on Home that need someone: something to fix, or something that happened. See Needs attention and notices. |
| Notice | A line under the top bar, on every page, when something affects everyone: AI traffic stopped, guardrails off, an override live, the licence. The most serious shows in full; Also: … names the rest. See Needs attention and notices. |
| Observe mode | A policy or guardrail that records what it would have done without changing any call. A policy is Draft, Observing, Enforcing or Paused. See Policies and regulations. |
| Org group | The team everyone starts in, made at first-run setup. It allows every model until it's given a list, and can't be moved or deleted. See Organisation, teams and sub-teams. |
| Organisation admin | Changes everything in the organisation. Never locked out. See People and roles. |
| Organisation viewer | Sees everything in the organisation and changes nothing. See People and roles. |
| Owner | A person who looks after an agent or application: changes what it's for and who to ask, and looks after its keys. Whoever adds it becomes its owner; admins of its team add others. See Applications and agents. |
P–R¶
| Word | What it means |
|---|---|
| Pack | A set of patterns, and on Enterprise, where VidaiGuard is set up, VidaiGuard checks, for a purpose, such as personal data or credentials. A regulation pack is different: a versioned description of a regulation. See Guardrails and Policies and regulations. |
| Pattern | A regular expression, built in or your own, that a guardrail's pattern checks look for. See Guardrails. |
| Personal access token | An API token a person makes for their own scripts, on Your account › Personal access tokens; it can do no more than they can. See Service accounts and API tokens. |
| Policy | A named set of parts (guardrails, region rules, compliance routes, approved destinations, routing rules and budgets), applied at a level and read as sentences. See Policies and regulations. |
| Provider | An AI service the gateway sends calls to: OpenAI, Azure OpenAI, Anthropic, AWS Bedrock, Google Gemini, Vertex AI, others, or your own server. See Providers and models. |
| Provider key | Your credential at a provider, held by Vidai and used by the gateway; shown by its label, never its secret. A provider can have several. See Provider keys and resilience. |
| Pseudonymise | Replace personal data with stand-ins before the model sees it, and put the originals back in the answer, streams included. See Guardrails. |
| Rate card | The published price feed Vidai prices calls from. Vidai keeps its own copy and every price version. See Prices and the rate card. |
| Rate limit | How many requests a minute a key may make. See Rate limits. |
| Recipe | A ready-made policy, such as "keep in region" or "personal data out", that you apply with a few answers. See Policies and regulations. |
| Recompute Enterprise | Pricing past calls again after a late or corrected price, always starting with a dry run that shows what would change; locked days are corrected by adjustment. See Cost. |
| Region rule Enterprise | A rule on where a call may be processed, on the organisation, an environment, a team, an application, a person or agent, or a key. See Regions and data residency. |
| Request id | The gateway's id for a call, sent back on every answer in x-vidai-request-id, errors included. Paste it into Request logs to open the call. See Request logs and the call record. |
| Request logs | The page listing every call through the gateway. See Request logs and the call record. |
| Retention | How long each kind of record is kept, set from the regulations you follow. See Retention, legal hold and subject requests. |
| Routing rule | Where an allowed call goes: another provider, another model, a split between two. See Routing and fallback. |
S–Z¶
| Word | What it means |
|---|---|
| Service account Enterprise | An account for one of your own systems that manages Vidai, with its own roles and API tokens. See Service accounts and API tokens. |
| Stop AI traffic | The switch that stops every AI call on every gateway node at once, read back from each node, until it's released. See Safety switches. |
| Sub-team | A team inside another team. A group admin of a team runs its sub-teams too, and a rule set on a team reaches them. See Organisation, teams and sub-teams. |
| Tamper evidence Enterprise | Records sealed and signed so that a change after the fact shows. A check reads Verified, Partly verified, Failed or Never verified. See Tamper evidence. |
| Team | A group of people and applications: a department, a client account, a product. Teams can have sub-teams. See Organisation, teams and sub-teams. |
| Translation profile | How a key's calls are translated between API formats: Standard, or one that keeps what the other format can't say; an admin can let apps choose per call. See Translation between API formats. |
| Unpriced | A call with no price yet. Never shown as zero; every total says how many calls it leaves out. Free is a real zero. See Prices and the rate card. |
| User | Anyone signed in. Everyone is a user; some people also hold roles. See People and roles. |
| VidaiGuard Enterprise | Vidai's own models that check content, running beside the gateway. What they run inside a guardrail are VidaiGuard checks, beside pattern checks. On Enterprise it's set up or not set up; guardrails are complete on pattern checks either way. See Guardrails. |
| What-if | On Money › Cost: what your real past calls would have cost on other models, cheapest first; a guide from list prices, not a forecast. See Cost. |
| What applies here | The page that shows every rule reaching a key, person or team, where each was set and why. See Rules at levels. |