Yes. canonry runs. Argusic installed and launched it on a clean machine in 17 minutes, hitting 4 errors on the way, and recorded the session.

How did Argusic test canonry?

On a fresh, disposable machine, with every command recorded and the repository pinned at commit bd245fdfebf8. One attempt is recorded, and the full method is on the methodology page.

What did it cost to test canonry?

The run that produced this verdict cost $0.22: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.

How long does canonry take to install?

17 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.

Does canonry need a GPU?

Not to start. Argusic reached a running state on a machine with no GPU.

What goes wrong when installing canonry?

4 things broke in the recorded run, and 4 were fixed without human help. Each one, and the time it cost, is listed on this page.

Where is the evidence for canonry?

The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

canonry

Agent-first AI SEO (AEO/GEO) operating platform

Runssource: GitHubTypeScriptMITcommit bd245fdfebf8

TypeScript, MIT licensed. The project labels itself: aeo, agent, ai search, ai visibility, answer engine optimisation, answer engine optimization, brand monitoring and cli.

canonry runs. An Argusic agent installed it in 17 minutes and hit 4 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

Install, build, and global CLI install succeed. Server launches and serves health (200) and API endpoints (200). 3,652 tests pass across 15 packages. Two db tests fail only because the sqlite3 CLI binary is unavailable in this container (no root).
What the agent ended up with on a clean machine, in its own words. How this is measured

Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 100 of 100 (the mean of this project's run scores).

At a glance

verdict: Runs
Argusic Score: 100 / 100
cost of the verifying run: $0.22 (measured)
recorded runs: 1
last tested: 2026-11-09
stars: 204
forks: 0
open issues: 0
watchers: 0
created: -
last push: -

Subject data from GitHub, linked at the top of this page. Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.

What was measured

From the run that decided this verdict. Every line is a recorded value, not an estimate.

Time lost to each failure while testing canonry, drawn from the recorded run — Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

Node v18.19.1 too old (requires >=26.12.1)3 minutes
pnpm not found in container2 minutes
.npmrc prefix setting conflicted with nvm1 minute
sqlite3 CLI binary not found, 2 tests skip

Install time: 17 minutes
Cold machine to finish: 19 minutes
Errors hit and fixed: 4 hit, 4 fixed with no human help
How the result was proved: pnpm exec vitest run --project contracts --project config --project intelligence --project provider-answer-services --project provider-local --project api-client-generated --project integration-typesafe --project integration-traffic --project integration-cloudflare-worker --project integration-cloudflare-queue --project integration-cloud-run --project integration-commoncrawl --project integration-wordpress --project integration-wordpress-traffic --project integration-vercel exited 0: 216 test files, 3652 passed; server 'canonry serve' /health returned 200 with {"status":"ok","service":"canonry","version":"7.97.5"}; API /api/v1/projects returned 200; CLI 'canonry --version' printed 7.97.5
Model tokens used: 82,084
Exact commit tested: bd245fdfebf8
Container image: sha256:cdd920bce783

What was not measured

The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.

Peak GPU memory: this ran on a CPU machine, so there was no GPU to sample
Behaviour over a long run: each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

The API key issue in the last test was due to a subshell expansion issue. The server was verified w…
exec
/bin/sh -lc '# restore the .npmrc file that was modified
cp /work/repo/.npmrc.bak /work/repo/.npmrc 2>/dev/null || true
cp /home/runner/.npmrc.bak /home/runner/.npmrc 2>/dev/null || true
echo "Cleanup done"' in /work/repo
 succeeded in 0ms:
Cleanup done
Here are the final comprehensive results:
tokens used
82,084
Here are the final comprehensive results:

Replay the whole session, every command from a clean machine to this point.

How it was tested

One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.

Strengths and limits

Measured facts, not opinions. How this is written.

What went well

Reached a running state on a clean machine, with the session recorded.
Installed in 17 minutes.
Recovered from all 4 errors without a human stepping in, which says the failures are documented well enough to solve.
Ran without a GPU, so it does not need one to start.
Licensed MIT, as reported by its host.

What did not, or is not known

Measured once so far. A single attempt shows it can run, not that it runs reliably.

What it is a reasonable choice for

Trying it on a laptop or a small server: it reached a running state without a GPU.

Also tested, in the same area

Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.

Run history

tested by	attempt	outcome	score	cost USD	when
Argusic Runner	1/3	Runs	100.00	0.22	2026-11-09 07:43 UTC

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/canonry.svg)](https://argusic.com/subject/canonry)

Questions

Does canonry run?: Yes. canonry runs. Argusic installed and launched it on a clean machine in 17 minutes, hitting 4 errors on the way, and recorded the session.
How did Argusic test canonry?: On a fresh, disposable machine, with every command recorded and the repository pinned at commit bd245fdfebf8. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test canonry?: The run that produced this verdict cost $0.22: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does canonry take to install?: 17 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
Does canonry need a GPU?: Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing canonry?: 4 things broke in the recorded run, and 4 were fixed without human help. Each one, and the time it cost, is listed on this page.
Where is the evidence for canonry?: The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.