AI Agent Orchestration Platform · View 06 of 32 · 2 · Structure
Contract ownership
- The platform owns and versions every inbound contract; breaking changes go through a new API version, never a mutation
- Two contracts are owned elsewhere: the MCP wire protocol and the Microsoft Graph adaptive-card schema
- Partner webhooks are HMAC signed with a replay window; an unsigned call is rejected at the edge, not at the handler
Numbers
- 38 public API operations across agent, workflow, runtime, governance and observability surfaces
- 6 published Event Grid topics; consumers subscribe, the platform does not maintain per-consumer routes
- Outbound egress is FQDN-restricted; the allow-list is versioned with the infrastructure
Omitted here
- Queue-level topology and delivery semantics — see Event and Messaging Topology
- Authentication detail on each hop — see Identity and Delegation