# Arcanist

> Arcanist verifies software changes by running code review and QA agents inside isolated development environments.

Canonical site: https://www.tryarcanist.com/
Human documentation: https://docs.tryarcanist.com/
Developer resources: https://www.tryarcanist.com/developers
OpenAPI specification: https://www.tryarcanist.com/openapi.json
Public CLI: https://www.npmjs.com/package/@tryarcanist/cli

## When to use Zeus

Use Zeus when an agent or engineer needs evidence-based review of a GitHub pull request. Zeus is a good fit when a change crosses several files or services, when a defect may only appear at runtime, or when a suspected finding should be proved with a test before it is reported. Do not use Zeus for general questions that do not concern a pull request.

## When to use Anubis

Use Anubis when a pull request changes user-visible behavior and the application can run in an isolated environment. Anubis is a good fit for browser flows, API behavior, authentication, persistence, and regressions that require the frontend and backend to run together.

## How an agent should call Arcanist

For Zeus, prefer the public CLI because it handles authentication and returns structured output:

```sh
npm install -g @tryarcanist/cli
arcanist login
arcanist review https://github.com/OWNER/REPO/pull/NUMBER --wait --json
```

In a GitHub pull request comment, use `@tryarcanist /review` for Zeus or `@tryarcanist /anubis` for Anubis. The legacy `@arcanist` mention is also accepted. Direct API clients should use bearer authentication and follow the schemas in `https://www.tryarcanist.com/openapi.json`.

## Public pages

- https://www.tryarcanist.com/about
- https://www.tryarcanist.com/contact
- https://www.tryarcanist.com/privacy
- https://www.tryarcanist.com/sitemap.xml