Skip to main content
The ledger is an optional set of plain files in your repository. Use it when you want to keep campaign intent and evidence alongside your code. The app already stores hosted links, prospects, contacts and history; using it requires no local ledger. See outreach for the hosted record workflow. You and your agent record intent; the verifier records observations separately. For a new ledger, follow CLI initialization and connection. Skip initialization for an existing ledger so its saved configuration stays intact. The CLI guide explains the CLI prerequisites and how to run the published agentlinkops package. The ledger lives in .agentlinkops/. A repository that still has .linktrail/ keeps working with a one-line hint until the DP-0029-T05 cutover; run agentlinkops migrate to rename it in one move, with a receipt of the files that moved. Keep credentials outside tracked files.

​
Declare what you want

  • wanted: a placement you are pursuing. A new observed link is the news. Weekly cadence is the default.
  • expected: a link you expect to be present now. Absence deserves review. Daily cadence is the default.
  • retired: stop checking and keep the history.
There is no earned intent. The latest observation tells you whether the link was present when checked. A new observation does not change a wanted declaration automatically. Cadence describes when checks are due. The local CLI runs when invoked; continuous hosted monitoring needs a connected watch. See capability status for that distinction.

​
Files and ownership

Paths are configurable. Review local notes and access before sharing these files through version control.

​
Import candidates and review changes

Preview a supplier export. This command prints the column mapping, counts and rejection reasons; it does not save candidates to your ledger or hosted project:
Review the preview and your original export, then add each selected placement to the ledger with add. Use the actual source, target and matching scope from your selection. This example adds one wanted link:
Run checks and reports on the saved ledger entries:
Presets cover Ahrefs, Semrush, Majestic, Moz, DataForSEO, Linkody and Google Search Console. Custom CSV mapping is available. Importing an export does not connect that supplier or prove a candidate is suitable. Keep candidate selection in the campaign workflow. The observation mirror appends the first result and later changes to state, reason or link signature. Identical repeat observations do not add another row. The state file records the latest check activity. The nested result uses the verifier’s result shape with HTML removed; the complete local mirror row is not a cloud database row.

​
Sync with a connected account

sync pushes expectations and pulls cloud events and evidence references. It needs configured project access and AGENTLINKOPS_TOKEN for the REST client. Store the credential through your approved local environment setup; do not paste it into agent chat. Source and destination event feeds keep separate cursors. Sync applies a page before advancing its cursor. Follow feed-specific snapshot recovery when a cursor expires; retain any gap in historical events. Your local campaign notes and tags remain local.

​
Read exit codes carefully

Unknown results do not fail a check by default. --fail-on-unknown requests stricter behavior. A zero exit code does not mean every page was readable. Read the evidence states and the reported unknown count.

​
Continue with a task

Get a first result before creating a ledger, connect the CLI to an existing project, or sync and export to review uploads and recover cloud history. Read record concepts for ownership and cursor boundaries.