Agent-orchestration platform for enterprise workflow automation.
- Operator
- IBM
- Open source
- Not indicated
- Payment capability
- Not indicated
- Supports MCP
- Yes
- Supports agent-to-agent protocols
- Yes
- Enterprise-managed
- Yes
- Cryptographically signed
- Not indicated
- Independent audit on record
- No public independent audit found
- Operator confirmed this listing
- Not indicated
- Last reviewed
- 2026-09-28
Verification notes: Re-checked this pass via IBM's own release notes. A2A is now specifically pinned to protocol version 0.3.0, with 0.2.1 support deprecated and scheduled for removal — worth knowing if integrating an older A2A agent against Orchestrate. The tool-adding UI was redesigned to make MCP servers easier to discover alongside OpenAPI specs and local-instance tools. Third-party agent support has broadened to explicitly include Langflow and LangGraph agents, not just Orchestrate's own native agent format. No change to the MCP-only-via-toolkits limitation flagged previously. Re-checked again this pass: IBM's public release notes for this product don't yet show an entry beyond what's already captured here, so A2A 0.3.0 pinning, the redesigned tool-adding UI, and the broadened third-party agent support remain the most current confirmed state. No flag changes. Re-checked 2026-09-28: A2A version pinning reconfirmed verbatim on IBM's developer docs — 0.3.0 is currently supported, with earlier versions such as 0.2.1 deprecated and scheduled for removal. LangGraph import support is confirmed via an official IBM announcement (May 8, 2026); Langflow import is documented separately in an IBM tutorial but wasn't part of that same announcement, so treat Langflow support as real but slightly less prominently GA'd than LangGraph. MCP remains toolkit/gateway-mediated (the ContextForge MCP Gateway pattern) rather than a native protocol client — no evidence found of that changing. No flag changes.
Suggest a correction to this profile →