CI Integration
Add an Orq gate step to your pipeline. If eval metrics regress below configured thresholds, the step exits non-zero and the deploy is blocked.
GitHub Actions
Add the following step after your test suite:
YAML
- name: Run Orq eval gate
uses: orq-ai/eval-gate-action@v1
with:
api_key: ${{ secrets.ORQ_API_KEY }}
suite: production-quality-v2
environment: production
Generic CI (curl)
Any CI system can call the gate endpoint directly:
Shell
curl -s -o /dev/null -w "%{http_code}" -X POST https://api.getorqai.com/v1/gate -H "Authorization: Bearer $ORQ_API_KEY" -H "Content-Type: application/json" -d '{"suite":"production-quality-v2","environment":"production"}'
Exit code 0 = gate passes. Exit code 1 = gate blocked. The response body contains the metrics that failed.
Environment configuration
Each environment (staging, production) can have separate threshold overrides. A staging run at 0.65 correctness might pass while production requires 0.80.
Next steps
- Eval metrics for threshold configuration options
- REST API reference for gate endpoint details