Workflow Gate
One request, three legs, one envelope - the clearest signal your pipeline can act on before production.
What you get
Send a structured snapshot of your repo and proposed change; get back a single JSON envelope that already ran audit, plan, and validation - no stitching responses in CI.
- workflow.safe_to_deploy - a boolean your GitHub Action or deploy script can gate on
- risk_score - comparable across runs for trends and alerting
- Standard v1 envelope - same error codes and request_id discipline as every other engine
- Idempotent POST with Idempotency-Key for safe retries from flaky runners
Why teams use it
Stop silent failures
When AI touches routes, APIs, or schema, you see combined health before merge - not after users hit prod.
Faster than three hops
One round-trip replaces chained audit to plan to validate calls, cutting latency and failure modes in the runner.
Built for automation
Machine-readable fields only - no prose parsing, no ambiguous "looks fine" output for agents or scripts.
CI-native
Designed for merge queues, deploy workflows, and policy checks where exit codes and JSON fields drive the pipeline.
When to use it
Use Workflow Gate on every merge or deploy candidate where you can supply project structure, routes, APIs, and database schema next to the diff or snapshot you want judged.