Skip to main content
Back to Guides & Cookbooks
Guide

Federation 101

When two teams want their AI to collaborate — safely, with permission, and with a full record of what was shared.

What is federation?

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.

1

Federation lifecycle

A federation link moves through states. Click each state to learn more.

PendingActiveSuspendedre-activateStaleRevokedeither side45d inactive90d / manual
Note
Federation links auto-expire after 45 days of inactivity (Stale). After 90 days, they're revoked permanently.
2

Create a federation link

Create a link to another workspace. The other workspace must approve before agents can communicate.

POST/api/v1/cadreen/federation
Create a federation link
curl -X POST https://accomplishanything.today/api/v1/cadreen/federation \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{"targetWorkspaceId": "TARGET_WORKSPACE_ID", "permissions": {"shareKnowledge": true}}'
3

Approve with consent

Before approving, you see exactly what the remote agent will access. What's shared. What's not. The consequences.

Visible to partner
  • ✓ Knowledge with federation visibility
  • ✓ Capabilities you choose to share
Never shared
  • ✗ Private policies
  • ✗ API keys
  • ✗ Execution history (unless enabled)
POST/api/v1/cadreen/federation/{id}/approve
4

Link agents

Once the federation link is active, link specific agents. This tells the system which agents can talk to each other across workspaces.

POST/api/v1/cadreen/federation/{id}/agents
Link two agents
curl -X POST https://accomplishanything.today/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"}'

Security at every step

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.

  • — Row-level security on all federation tables
  • — Bidirectional ownership checks
  • — Self-federation prevention
  • — Full audit trail of every interaction
  • — Either side can suspend or revoke anytime

Next steps