API and MCP Gateway
Gateway is different from simple request routing. Each route can trigger a workflow that calls services, branches, waits for humans, retries failures, applies compensation, and records a full execution history.
Use API Gateway when external applications or internal services need a stable HTTP interface for invoking workflow logic. Use MCP Gateway when AI agents need discoverable tools that execute governed business workflows.
5-minute path
Create the workflow first, grant an application permission to execute it, create an authenticated Gateway service, add a route, test the route, then monitor the execution in Conductor.
Gateway routes inherit authentication, authorization, schema validation, caching, rate limits, and operational metrics from Orkes Conductor. This keeps endpoint behavior tied to durable execution instead of scattering orchestration, retries, and audit trails across clients.