Glossary
Every page of these docs uses the terms below with exactly this meaning.
Core objects
Section titled “Core objects”Workspace — The top-level container for your company in Orqane. It holds your teams, employees, connectors, wallets, policies and billing. Data never crosses workspaces.
Member — A human with access to a workspace. Each member has a role: Owner, Admin, Builder, Manager or Viewer. See Workspaces and roles.
Virtual employee (or Employee) — An AI agent with a job. It has a role, a mission, skills, tools, memory, an identity, a budget and a human manager. See Virtual employees.
Human manager — The member accountable for an employee. They receive its approvals and escalations, and they review its performance.
Team — A group of employees, and optionally members, that work toward a shared goal. A team can have a manager employee that splits work and delegates it. See Teams and org chart.
Org chart — The tree of teams, employees and human managers in a workspace.
Template — A ready-made employee definition you can hire from the Marketplace or from your own library.
Task — A unit of work given to an employee, such as “Qualify the 40 new leads from yesterday”. A task has a goal, inputs, a deadline and an owner.
Run — One execution of a task. A run records every step: what the employee planned, which tools it called, what it spent and what it produced. See Tasks and runs.
Step — One action inside a run: a reasoning step, a tool call, a message, a payment or a hand-off.
Checkpoint — A saved state of a run. Orqane resumes a run from its last checkpoint after a pause, an approval or a failure.
Trigger — What starts a task: a chat message, a schedule, an incoming email, a webhook, a business event or a request from another employee. See Triggers.
Hand-off — When an employee passes a task, or part of it, to another employee or to a human.
Control
Section titled “Control”Autonomy level — How much an employee may do without asking. It goes from L0 Suggest to L4 Delegate. See Autonomy levels.
Approval — A request from an employee to a human before it performs an action above its autonomy level or a policy threshold. See Approvals.
Policy — A workspace rule that limits what employees can do, such as “never email a domain outside the allowlist” or “never spend more than 50 USDC per task”. See Policies.
Guardrail — An automatic check that runs on every step to block unsafe content or actions, such as a prompt-injection attempt or a leak of personal data.
Probation — The first period of a new employee’s life, during which it runs at a lower autonomy level and its work is reviewed more closely. See Lifecycle.
Performance review — A periodic report on an employee’s results, quality, cost and incidents. It is the basis for a promotion or a demotion.
Abilities
Section titled “Abilities”Skill — Know-how an employee can apply, such as “Write a cold email” or “Reconcile invoices”. A skill bundles instructions, examples and the tools it needs. See Skills and tools.
Tool — A single action an employee can perform in another system, such as “Create a HubSpot deal” or “Search the web”.
Connector — An authenticated link between your workspace and an outside app, such as Google Workspace, Slack or Salesforce. Connectors provide tools. See Connectors.
Channel — Where people talk to an employee: the Orqane chat, Slack, Microsoft Teams, email, WhatsApp or voice. See Channels.
Sandbox — An isolated environment where an employee runs code, browses the web or uses a computer. See Sandboxes.
Memory — What an employee remembers across runs: past work, facts, preferences and learned procedures. See Memory and knowledge.
Knowledge base — A set of documents an employee, team or workspace can search, such as your product docs or your sales playbook.
Protocols
Section titled “Protocols”MCP (Model Context Protocol) — An open protocol to connect AI agents to tools and data. Orqane employees use any MCP server, and you can expose any employee as an MCP server. See MCP.
A2A (Agent2Agent) — An open protocol for agents to discover each other and work together. Orqane employees can collaborate with agents outside Orqane. See A2A.
x402 — An open payment protocol built on the HTTP 402 Payment Required status. It lets an employee pay for an API call, a dataset or another agent’s work in stablecoins, per use. See x402 payments.
Wallet — The account an employee pays and gets paid with. Each employee can have its own wallet, funded from the workspace treasury. See Wallets and budgets.
Treasury — The workspace’s main wallet. It funds employee wallets and receives marketplace earnings.
Budget — The maximum an employee may spend over a period, across model usage and payments.
Spend limit — The maximum an employee may spend on a single payment or a single task.
Merchant allowlist — The list of services an employee is allowed to pay.
Credits — The unit Orqane uses to bill model usage and platform features. See Billing.
Marketplace
Section titled “Marketplace”Marketplace — The catalog where you find and hire employee templates, skills, MCP tools, workflows and knowledge packs. See Marketplace.
Listing — An item published on the marketplace, with its versions, permissions, price and reviews.
Publisher — A workspace that publishes listings on the marketplace.
Agent-to-agent economy — The ability for your employees to hire marketplace agents for a task and pay them with x402, within their budget. See Agent-to-agent economy.
Certification — Orqane’s review of a listing’s permissions, security and behavior before it gets the Certified badge.