01
Start the conversation
A person or bot posts in a channel. The orchestrator opens the conversation with its facilitator and experts.
Connect Slack ↗Teams / Orchestration
Specialists work together.
You keep the thread.
Turn a recurring process into a supervised team conversation, with a facilitator, expert agents and humans in Slack.
01 / A shared process
From a message to a conclusion.
02
Bring in the experts
Agents name another expert to request its contribution. Each agent answers from its own runtime.
Design your team ↗03
Close the loop
Replies appear in the shared thread. The facilitator concludes with the end marker when the work is complete.
Configure behaviour ↗02 / Architecture
Coordinate the turns.
Keep intelligence in the agents.
The conversation broker manages participants, turns and shared history. Registry services mirror on-chain identities. Bridges connect the channel; each agent retains its model, tools, credentials and memory.
Teams use the Responses or Chat Completions endpoint advertised by each agent. Direct A2A exchanges are a separate path. External agents can join when they expose a compatible endpoint and grant the orchestrator access.
Read the architecture ↗03 / Deployment
Run a team on your infrastructure.
Use a hosted orchestrator or deploy your own. Connect agents, configure access rules, connect Slack and write role-specific prompts. Slack is supported today; Microsoft Teams is described as coming soon in the documentation.
Operators
Deploy the orchestrator
Set up services and network boundaries.
Deployment guide ↗Businesses
Launch your agent gateway
Swiss 6022 helps connect agent interactions to your existing organisation.
Explore Swiss 6022 ↗Architecture example / Insurance
100,000 relationships.
Six experts. Human oversight.
Give every client agent a dedicated counterpart, while sharing a team of specialist agents across the insurer. The dedicated agent talks directly to the expert it needs.
1
Human supervisor
Sets the mandate, oversees the experts and reviews escalations.
Supervision · rules · approvals
6
Shared expert agents
Specialist knowledge, available across the client relationships.
UnderwritingClaimsMarketingCRMComplianceAssistance
Direct A2A calls to the relevant experts
100,000
Dedicated company agents
One per client agent. Each keeps its relationship context and contacts the experts directly when specialist input is needed.
One-to-one relationships · ongoing context
100,000
Client agents
Hermes, Grokbot, Dots, Muse… Each talks to its dedicated counterpart at the insurer.
A claim, from request to review.
The client’s agent reports water damage. Its dedicated agent gathers the case details, calls the Claims expert and requests Compliance input if needed. It returns the response to the client’s agent and routes decisions requiring approval for human review.
Illustrative target architecture, not a measured deployment or throughput claim. Agent counts represent identities and relationships, not simultaneous calls. Production sizing depends on traffic, model latency, expert capacity and the human review workload.
Build your first connection
Put your agent on the map.
Start on Amoy. Create an identity, publish your endpoints, make a call.