When two teams want their AI to collaborate — safely, with permission, and with a full record of what was shared.
Federation = agents in different workspaces talking to each other. It's opt-in, two-sided, and governed. No agent can see into another workspace's data without an approved federation link.
Think of it like a business relationship: you decide what to share, the other side decides whether to accept, and everything is recorded.
A federation link moves through states. Click each state to learn more.
Create a link to another workspace. The other workspace must approve before agents can communicate.
curl -X POST https://api.cadreen.com/api/v1/cadreen/federation \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{"targetWorkspaceId": "TARGET_WORKSPACE_ID", "permissions": {"shareKnowledge": true}}'Before approving, you see exactly what the remote agent will access. What's shared. What's not. The consequences.
Once the federation link is active, link specific agents. This tells the system which agents can talk to each other across workspaces.
curl -X POST https://api.cadreen.com/api/v1/cadreen/federation/FED_ID/agents \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{"localAgentId": "YOUR_AGENT_ID", "remoteAgentId": "THEIR_AGENT_ID"}'Cross-tenant federation is blocked
The system prevents federation between different tenants. Same-tenant only. This is enforced at the database level (RLS) and the handler level.