They check the context each task needs, with the user’s permissions.
Your agents read, operate and transact in XEN.
With the permissions of the person who connects them, with approval when the action calls for it and with every call in the audit log. XEN speaks MCP, AP2 and UCP; no custom integration is needed.
They prepare actions inside your company and wait for approval when it matters.
They pay and order within a signed mandate, with the full record.
They read with permissions
An agent checks stock, invoices or a person’s file with the same scope as the user who connected it. Not one module more.
They operate with approval
They prepare a reminder, a purchase order or an adjustment. The sensitive action waits for the responsible person and is logged with who approved it.
They transact within a mandate
They pay and buy only within what a person authorized: limit, validity and payees. Outside the mandate, the payment does not run.
What each protocol does in XEN.
MCP connects the agent to context and tools; AP2 lets it pay with a verifiable authorization; UCP moves catalogs and orders between companies and agents.
The agent discovers and uses XEN’s tools.
MCP is the open standard through which a model or agent discovers and calls an application’s tools and data. XEN publishes one MCP server per organization: each module exposes tools (check stock, read an invoice, prepare a reminder) and the agent invokes them with the permissions of the user who connected it. Every call goes into the audit log.
- One MCP server per organization, with each module’s tools.
- Each tool’s scope is that of the user who connects the agent.
- Any client that speaks MCP connects without a custom integration.
inventory.stockThe agent pays only within what a person authorized.
AP2 is the protocol that lets an agent pay with a verifiable authorization. A person with permission signs a mandate with a limit, validity and payees; the agent builds the purchase within that mandate; the payment runs only if it fits, and mandate and payment stay linked in the audit log.
- A mandate signed by Treasury: limit, validity and payees.
- The payment runs only within the mandate; outside it, it does not.
- Mandate, purchase order and payment stay linked in the record.
- Signed by
- Treasury · Diego Torres
- Limit
- $6,000
- Validity
- September 1 to 30
- Payee
- Filtros Andinos
Catalogs and orders travel between companies and agents.
UCP is the protocol through which catalogs, orders and confirmations are exchanged between systems and agents without an integration per client. XEN publishes your catalog with prices and free stock; a client’s agent builds the order, XEN confirms it, reserves the stock and issues the invoice when it is due.
- A published catalog with price and free stock per product.
- The agent’s order comes in as one more order, with stock reserved.
- Confirmation, shipment and invoice go back to the agent through the same channel.
- Catalog published48 products with price and free stock
- Order from Northstar Supply’s agentPED-0099 · 40 filters · $4,800
- Confirmed and reserved40 units in Main · delivery Sep 22
- Invoice on deliveryF001-00847 is issued with the shipment
What each connection turns on, and who answers for it.
From the organization’s settings you switch on MCP servers, integrations and each agent’s permissions. Each one has a scope, a responsible person and its record.

- MCP servers
- 2 Active
- Integrations
- 4 Connected
- Agents with permissions
- 3 With a responsible person
Every transaction shows its mandate and its responsible person.
The $5,400 payment to Filtros Andinos shows the mandate that authorized it, the purchase order that started it and the record that stored it. An agent that transacts leaves the same trail as a person.
- Agent, tool and scope of every call.
- The mandate or approval that authorized the action.
- An exportable audit log, with date and responsible person.
- Agent
- Purchasing agent
- Tool
- Purchasing · pay
- Mandate
- $6,000 until September 30
- Payment
- $5,400 to Filtros Andinos
The company defines the scope. The agent works within it.
Permissions are applied before every call, approval is requested when the action requires it and everything is written down.
The scope is defined per tool.
Read, operate with approval or transact with a mandate. Every agent has its list and its responsible person.
- Inventory
- Read Stock and movements
- Sales
- Read Invoices and orders
- Accounts
- Operate With collections approval
- Purchasing
- Transact Within the AP2 mandate
Every action leaves its record.
Who asked, which tool was used, who approved and what ran. 318 records in September, exportable.
- 09:12 · Collections agent
- Reminder Cedar Distribution · approved by Diego Torres
- 10:40 · Purchasing agent
- Payment $5,400 Filtros Andinos · within the AP2 mandate
- 11:05 · Northstar Supply’s agent
- Order PED-0099 Received through UCP · confirmed
Before you connect your first agent.
What teams already using agents ask.
