Skip to main content
Check one public source page against the target URL you expect it to cite. This local path needs Node.js 22 or later, an authorized checkout or supplied toolkit, and network access. It needs no AgentLinkOps account or ledger.

​
Run one check

From your repository, replace the checkout path and both example URLs:
The source is the publisher page. The target is your destination. exact asks whether the page links to that URL under the verifier’s normalization rules. Use an actual public page you are permitted to fetch.

​
Read the result

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

​
Save it when useful

To keep the original result in a new ledger:
Choose expected only when you expect the placement to exist now; choose wanted for a placement you are pursuing. Adopting saves the original observation and supports replay. It does not install a scheduler. Read the ledger guide before committing files. To keep checking after your terminal exits, connect the CLI and review hosted monitoring. If the command fails before fetching, use troubleshooting.