Use Ovyero from any CI

GitHub Actions has a ready-made workflow (GitHub). Any other CI system can call the HTTP API directly: send a file, read the verdict, fail the build on GATE.

Steps

1. Store your Ovyero API key as a secret in your CI system (the examples call it OVYERO_API_KEY).
2. For each changed file, POST its name and content to /api/v1/govern/file:

   jq -n --arg f "$FILE" --rawfile c "$FILE" '{filename:$f, content:$c}' \
     | curl -fsS -X POST https://ovyero.visnryentertainment.com/api/v1/govern/file \
         -H "Authorization: Bearer $OVYERO_API_KEY" \
         -H "Content-Type: application/json" --data-binary @-

3. Read verdict in the JSON response: PASS, WARN or GATE. Fail the build when it is GATE (passed is false).

Several files in one request

POST /api/v1/govern/files-bulk with {"files":[{"filename":"…","content":"…"}, …]}, up to 100 files per request. The response is {"verdicts":[…],"count":N}, one verdict object per file in the same shape as the single-file call.

Reading the response

• findings is a per-domain summary; violations is the flat list of individual issues (message, line).
• coverage is full, partial, baseline or none. A PASS whose coverage is not full means the file was not fully reviewed, not that it is clean; coverage_note says why.
• audit_id identifies the record written to your audit ledger.

Limits

• The govern endpoints have their own rate limit (600 requests a minute by default). A 429 means slow down and retry.
• The Free plan covers one developer and up to 2 repositories.

Full endpoint list: API. Problems: Troubleshooting.