Glossary¶
These terms describe the current release. Links lead to explanations and practical guides; the separate Product direction archive may describe future resources.
| Term | Meaning |
|---|---|
| Agent | Managed application content: instructions, model, tools and account defaults. Lifecycle. |
| Allocation | A governance ceiling assigned to a scope. It is not a prepaid provider balance. Limits. |
| Catalog | The Organization's configured models, tools and related resources. |
| Connector | A configured MCP server and its upstream authentication. Models and tools. |
| Dataset | Versioned cases used to measure behavior; each item has input and expected output. Evaluation. |
| Deployment | A destination serving a published Agent version with its own access and execution settings. |
| Evaluator / grader | A versioned mechanism for scoring evidence: LLM judge, assertion or tool validator. The Console uses Evaluators. |
| Experiment | Recorded execution of a pinned subject against a pinned dataset selection. |
| Grading pass | A set of judgments over saved experiment answers, separate from generation. |
| Namespace | A server-resolved scope for grouping or customer attribution; labels alone grant no access. |
| Operating cap | A limit that narrows spending, rate or concurrent capacity. |
| Organization | The boundary owning the catalog, people, Teams and governance configuration. |
| Request | A canonical gateway decision and outcome. Observation concepts. |
| Score definition | The meaning and allowed type or range of an evaluation score. |
| Service account | An ordinary non-human owner for backend keys, independent of its creator's employment. |
| Session | Activity grouped by namespace and Session ID; distinct from a private Chat conversation. |
| Snapshot | An immutable saved Agent definition and account defaults. |
| Span | One observed unit of execution within a Trace. Uploaded spans are not billing authority. |
| Team | A scope with membership, resource allowance, keys and budgets inside an Organization. |
| Team allowance | The resource ceiling within which a Team's keys operate. |
| Tool set | A configured group of tools that allowance or key policy can follow. |
| Trace | Related spans scoped by Organization, Team and Trace ID. |
| Usage | Financial records for physical provider attempts and business tool dispatches. |
| Virtual key | A Mission Control credential and policy bound to one Team and exact owner. Access concepts. |
| Virtual model | A stable model identifier routed to configured provider infrastructure. |
For exact permissions, use Roles and permissions. For response codes and recovery, use Gateway errors.