Connect with the CLI

Use agentlinkops to check a supplied backlink or work with saved links in your hosted project. You need Node.js 22.13.0 or later. Prefix commands with npx -y or install once with npm install -g agentlinkops.

Start with one check

npx -y agentlinkops@0.6.13 check \
  --source https://publisher.example/resources \
  --target https://your-site.example/guide \
  --scope exact \
  --json

Replace both URLs. This path needs no account or ledger. Read the result to inspect the matched link, anchor and attributes.

Call a hosted project

The steps below work with the npm release checked on October 24, 2026: 0.6.13. The saved-key prompt documented in current source is intended for 0.6.14 or later and was not in that published package. The commands in this guide pin agentlinkops@0.6.13 so they use that released behavior. A separately installed global package can have a different version. Hosted access requires a pilot invitation. In the app, select your workspace and open Agent access. An owner or admin can create a scoped workspace API credential. Keep it in your terminal environment, outside committed files.

export AGENTLINKOPS_TOKEN="YOUR_WORKSPACE_API_KEY"
export AGENTLINKOPS_API_URL="https://app.agentlinkops.com"
npx -y agentlinkops@0.6.13 call list_projects --args '{}'

Choose an accessible project from the result. This read requires projects:read.

Read saved-link types and tags

When your workspace supports labels, request a detailed list to see saved-link types and tags:

npx -y agentlinkops@0.6.13 call list_link_watches \
  --args '{"projectId":"YOUR_PROJECT_ID","format":"detailed"}'

This read requires watches:read. Use display_category for the displayed Link type and tags for organizational labels.chosen_category keeps the saved choice or deliberate clear; page_assessment keeps its own evidence dates and state. These fields use category_contract: "link-category-v1". Reading them does not run classification.Link types and retained assessment evidence explains current and previous evidence. The saved-link reference documents the response; choose a type and attach tags cover those changes.

Connect a local ledger when you need sync

Use this optional path to keep local records connected to the hosted project. For a new ledger, run these commands in the folder that should own the files. If you already have a ledger, skip init to preserve its configuration:

npx -y agentlinkops@0.6.13 init
npx -y agentlinkops@0.6.13 connect \
  --workspace YOUR_WORKSPACE_ID \
  --project-id YOUR_PROJECT_ID
npx -y agentlinkops@0.6.13 sync --dry-run

Replace both IDs with existing records. Saving the connection and running sync writes require the CLI’s native lock on macOS or Linux. connect verifies access and saves the project binding; the preview shows proposed sync changes. It keeps the API credential in your environment. The connection requires projects:read, watches:read, watches:write, events:read and exports:create. Read connect options before automating it. Ledger files explains ownership and sync explains push and pull behavior.

Inspect commands and recover access

npx -y agentlinkops@0.6.13 tools
npx -y agentlinkops@0.6.13 describe list_projects --examples --output-schema

These use the bundled catalog. Add --refresh to inspect the connected server. Operator-only commands can appear in the bundled snapshot and remain hidden from ordinary authenticated catalogs.call NAME --file arguments.json accepts a larger JSON object. Call options covers flags and confirmation. AGENTLINKOPS_API_KEY is a credential alias; conflicting credential variables fail. Configuration covers saved-origin conflicts and compatibility aliases.Read troubleshooting for missing grants and request failures. A queued check still needs its completed observation.

Optional: CLI OAuth on Linux

This path needs an existing public OAuth client and a Linux credential store. macOS and Windows CLI OAuth are refused; use a terminal workspace API credential or OAuth through your MCP client on those platforms.

Connect an existing OAuth client on Linux

From an initialized ledger, remove conflicting API-credential configuration and use the existing workspace, project, client and issuer values:

npx -y agentlinkops@0.6.13 connect --oauth \
  --workspace YOUR_WORKSPACE_ID \
  --project-id YOUR_PROJECT_ID \
  --issuer https://issuer.example.com \
  --client-id YOUR_PUBLIC_CLIENT_ID

The CLI prints a browser authorization URL and receives consent through a bounded loopback callback using PKCE. It does not register a client. Have the client’s intended grant approved in Agent access before connecting.Tokens stay in permission-checked, user-owned files under ~/.agentlinkops/oauth/. The ledger stores a credential reference and issuer/client/resource binding. OAuth calls use MCP; these credentials do not authenticate REST requests. The CLI refreshes tokens through their bound issuer and refuses mixed credential modes or mismatched bindings.A successful connection verifies workspace/project reads. Start with npx -y agentlinkops@0.6.13 sync --pull-only; reads do not establish OAuth write permission. After an uncertain write, inspect its outcome before repeating it.For AGENT_APPROVAL_REQUIRED, preserve the session and follow the returned approvalUrl and clientId for human review. For WORKSPACE_REQUIRED, select an already approved workspace. Repeated sign-in does not approve a grant.

Agent setup is a separate installer that stores no credential. Source and issues: AgentLinkOps CLI, Apache-2.0.

Start here

Links and reports

Outreach

Connections and local files

Understand and troubleshoot

Start with one check

Call a hosted project

Connect a local ledger when you need sync

Optional: CLI OAuth on Linux

​Start with one check

​Call a hosted project

​Connect a local ledger when you need sync

​Optional: CLI OAuth on Linux

Start with one check

Call a hosted project

Connect a local ledger when you need sync

Optional: CLI OAuth on Linux