Skip to main content
Use this path for a first result with nothing but Node.js 22 or later and network access: npm install -g agentlinkops, or prefix each command with npx -y to run it without installing. No account or ledger is needed. Connect with the CLI covers the hosted side. For hosted checks through your agent, follow Get started; availability tracks releases.

​
Run one check

Replace the checkout path and both example URLs:
The source is the publisher page; the target is your destination. exact matches that URL under the verifier’s normalization rules. Use a public page you are permitted to fetch.

​
Read the result

  • present: the read found a matching link. Inspect its occurrences and anchor.
  • absent: the read found no match. Check the source, target and scope.
  • unknown: the verifier could not decide. Read the reason, such as a challenge or timeout, and inspect the page with your browser when appropriate.
An unknown result never establishes removal. Evidence states separates one observation from confirmed loss.

​
Save it when useful

To save the original result in a new ledger:
Use expected when the placement should exist now, or wanted when you are pursuing it. Adopting preserves the observation and supports replay. It does not schedule future checks. Read file ownership before committing the ledger. For recurring checks, connect the CLI and use hosted monitoring. See troubleshooting if the command fails.