Three steps from install to a review verdict in your terminal. Use the GitHub App for the full pipeline, or trigger reviews on demand via the API.
Hound ships as a GitHub App — pick the repos you want reviewed and the rest is automatic. You'll need admin access on the target account or org.
See the setup guide for the full first-run walkthrough (install, repo selection, first review).
Hound exposes POST /api/reviews for triggering a review from CI, your terminal, or anywhere you can fire a request. Requires $HOUND_API_TOKEN and the GitHub App to already be installed on the target repo (see step 1).
curl -X POST https://<host>/api/reviews \
-H "Authorization: Bearer $HOUND_API_TOKEN" \
-H "Content-Type: application/json" \
-d '{"repo":"owner/name","pr_number":42}'
By default the endpoint responds immediately and runs the review async (the webhook-equivalent "ack fast" pattern). Pass ?wait=true to block until the review finishes and get the full verdict inline:
curl -X POST "https://<host>/api/reviews?wait=true" \
-H "Authorization: Bearer $HOUND_API_TOKEN" \
-H "Content-Type: application/json" \
-d '{"repo":"owner/name","pr_number":42}'
Hound posts a formatted review comment on the PR — that's the readable verdict. The JSON response is the acknowledgement.
Async (default) — confirms the review was queued:
{
"status": "queued",
"repo": "owner/name",
"pr_number": 42
}
Sync (?wait=true) — returns once the review finishes:
{
"status": "ok",
"repo": "owner/name",
"pr_number": 42,
"review_id": 17,
"comment_posted": true
}
status: "ok" with comment_posted: true means the verdict is on the PR.
status: "queued" means Hound accepted the job — check the PR for the comment when it lands.
400 (invalid body) or 500 (review failure) with a JSON error field.
Need the full schema, auth model, and error shapes? See the API reference. See the verdict usage guide for how to read severity, fix suggestions, and merge decisions on each finding. · Setup guide · Troubleshooting