Skip to content

Capabilities overview

Capabilities are how an employee reaches the world outside Orqane. Each capability you enable becomes one or more tools the employee can call, and every tool call goes through the same checks: autonomy level, policies, budget and guardrails.

Capability What it gives an employee Example tools
Connectors Authenticated access to your business apps hubspot.create_deal, gmail.send_email, notion.search
MCP Any MCP server as a source of tools, and a way to expose the employee to other AI tools linear.create_issue, stripe.list_invoices
A2A Collaboration with agents outside Orqane, in both directions a2a.send_task to a supplier’s quoting agent
x402 payments Per-use payments for APIs, data and other agents, in USDC Automatic payment when a paid API answers 402
Channels Conversations with people on chat, Slack, Teams, email, WhatsApp and voice email.reply, slack.post_message, voice.call
Sandboxes An isolated machine to run code, browse the web or use a desktop code.run, browser.open, computer.click
Models The language models the employee thinks with, and how Orqane picks one per step Not a tool; a setting of the employee and its skills

Every capability follows the same path before an employee can use it:

  1. Connect it once at the workspace level. An Admin or Builder opens Settings → Capabilities and connects the app, the MCP server or the external agent.
  2. Discover its tools. Orqane lists every tool the capability provides and assigns each one an impact class.
  3. Grant tools to employees. On an employee’s Tools tab, or inside a skill, you choose which tools the employee may call. An employee never sees a tool you didn’t grant.
  4. Use them in runs. Each tool call appears as a step in the run, with its inputs, its output, its duration and its cost.

Orqane classifies every tool by what it can change. The class decides how the tool interacts with the employee’s autonomy level.

Impact class Meaning Example
Read Looks up data, changes nothing Search the CRM, read a file
Draft Produces content that stays inside Orqane Draft an email, prepare a report
Write internal Creates or updates records in your own systems Update a deal stage, create a Jira ticket
Communicate Sends a message to someone outside the employee’s team Reply to a customer email
Spend Moves money from the employee’s wallet Pay for an API call over x402
Delegate Gives work to another employee or agent Send an A2A task, hire a marketplace agent
Irreversible Can’t be undone Delete a record, publish a post, sign a contract

Orqane sets a default class for every catalog tool and for every tool it discovers on an MCP server. A Builder can raise or lower the class on the capability’s Tools list. Lowering a class below Orqane’s default is recorded in the audit log.

Before every tool call, Orqane runs these checks in order. The first one that fails stops the call.

Check What it verifies If it fails
Grant The tool is granted to this employee The call is refused
Policy No workspace policy blocks it The call is refused, or an approval is required if the policy says so
Autonomy The impact class is allowed at the employee’s level and under its thresholds The employee creates an approval and the run pauses
Budget The cost fits the employee’s budget and spend limits The employee creates an approval or stops, depending on the budget setting
Guardrails The inputs contain no prompt injection, data leak or unsafe content The call is blocked and the employee’s manager is notified

These checks apply the same way whatever the capability. A message sent on WhatsApp, a payment over x402 and an MCP tool call are all steps of the same run, under the same rules.

Some capabilities are off by default and need an Owner or Admin to turn them on in Settings → Capabilities:

  • x402 payments, because they move real money.
  • Computer use sandboxes, because they act on full desktops.
  • Inbound MCP and inbound A2A, because they let outside clients reach your employees.