AI Exchange Node

Exchange information between organisations' AI systems and agents.

AI Exchange Node is a standard, secure MCP connector, IN and OUT, that joins your organisation to a trusted exchange. Your agents can work with partners' systems, and partners' agents with yours, under rules everyone shares.

How the exchange works
The exchange

A community of organisations that trust the same rules.

An exchange is a group of organisations whose nodes all work the same way and who trust one common trust anchor to vouch for every member. Join once, and you can work with every member.

Without an exchange

Every pair of organisations builds its own integration, swaps its own keys and signs its own contract. Six organisations already need fifteen of them.

With an exchange

Each organisation runs one node and is vouched for once by the trust anchor. Any member can then call any other directly; the anchor confirms who is who but never sees the data.

One standard

Every node speaks MCP and follows the same trust framework, so any member can connect to any other without custom work.

One trust anchor

An association, regulator or consortium vouches for who the members are, and can withdraw that at any time.

Direct calls

Information goes straight from one organisation to another. Each keeps its own data, its own rules and its own evidence.

The node

One secure connector for each organisation.

The node is the organisation's single, standard gateway into the exchange, for traffic in both directions.

MCP-IN

Open selected systems to partners

Three standard endpoints, from open to restricted: public (T0) for anyone, customer (T1) behind an OAuth login, and partner (T2) for agents that present a credential and a mandate. Each endpoint shows only the tools you attach to it; adapters connect those tools to your systems.

Inside an AI Exchange Node Internal systems connect through adapters to three standard MCP-IN endpoints: public (T0), customer (T1) and partner (T2). The organisation's AI agents call partners' nodes through MCP-OUT and an outbound trust gateway. A trust anchor and registry vouch for every member. Your organisation Internal systems CRM ERP Document management Databases & registers People and internal AI Your teams and internal AI systems AI Exchange Node mcp.<your-domain> MCP-IN Adapters REST, SOAP SQL, files T0 Public endpointOpen to anyone, no token T1 Customer endpointOAuth token via the customer's company login T2 Partner endpointAgent credential + mandate, re-checked in session Organisation identity, live key challenge, admission log, signed audit MCP-OUT Procurement agentMCP Fleet agentMCP Contract agentMCP Outbound trust gateway Checks every partner before a call leaves: • membership credential • revocation status • live key challenge Who calls you Any AI assistantPublic information only Customers' staffChatGPT, Claude via company login Partner agentsPresent MCPF credentials and a mandate Who you call MCPInsurer's node MCPVehicle register's node MCPUtility's node Trust anchor and registry Vouches for members, publishes revocations
MCP-OUT

Let your agents work with partners

Your AI agents live on the node, each with its own identity and mandate, and call partners' nodes through it. The outbound trust gateway checks each partner's membership, revocation status and key before any call leaves.

Trust framework

Built on MCPF, the trust layer for MCP.

The Model Context Protocol connects AI agents to tools, but it does not say who is on the other side. MCPF (MCP Trust Framework) adds that: verifiable identities for organisations and agents, credentials from the trust anchor, and revocation that reaches everyone.

Every AI Exchange Node implements MCPF, which is what lets organisations that have never met trust each other's agents from the first call.

Who is calling

Every organisation and every agent has its own verifiable identity, tied to the organisation responsible for it.

Vouched for by the anchor

The trust anchor issues each member a signed credential. Any node can check it without asking anyone.

Proof, not copies

A node proves on the spot that it holds its own key, so published documents alone cannot be used to impersonate it.

What it may do, until when

Each agent carries a mandate from its organisation. Withdraw the mandate or the membership and access ends everywhere, even mid-session.

One call

What happens when an agent asks a partner.

1

The agent asks

It shows who it is, which organisation it belongs to and what it is allowed to do.

2

The partner's node checks

Identity, membership with the trust anchor and the mandate. If anything fails, the call stops.

3

The answer comes back

Only what the mandate allows, and both sides keep a signed record of what happened.

Who joins

Everyone in the exchange, in their own role.

Data and service owners

Registers, insurers, utilities, public bodies. Share selected functions with partners' agents without building an API programme.

Organisations with AI agents

Give each agent one identity and one mandate, and reach every member without separate contracts or keys.

Employees using AI assistants

ChatGPT, Claude and similar assistants sign in with the person's normal company login and stay within the rights the company gave.

Trust anchor operators

Associations, regulators and consortia set the rules, admit members, and withdraw access across the whole exchange at once.

The node does not decide whether an agent is good. It makes an organisation's word about its agent — who it is, what it may do, until when — checkable by every partner and revocable everywhere at once.