Skip to main content
Start with your existing agent and a page you want to earn links to. Hosted access requires a pilot invitation. A supplied local toolkit or development checkout can keep a ledger and run local checks without an AgentLinkOps account.

​
Connect to the hosted pilot

Give your agent this prompt:
The HTTP MCP endpoint is:
For Claude Code, register the endpoint:
Complete sign-in and consent in the browser when your client requests it. The grant controls workspace access and tool scopes. Keep tokens in the client’s credential store or the documented local environment; do not paste them into the conversation. MCP OAuth grants and REST credentials have different purposes. After connecting, ask the agent to call list_projects. Confirm the intended project before creating a watch or importing data. If access fails, check the pilot invitation, selected account, consent and requested workspace before retrying. Client support varies; a listed endpoint alone does not establish a successful connection.

​
Choose a first task

For a supplied placement, start with monitor_link, request a check with request_link_check, then read the job and history. Use the returned identifiers. get_public_contacts reads saved HTML for a watch, so check the page before requesting contacts. See campaign workflows, evidence states and the tool reference for the inputs and limits.

​
Run the local development CLI

These commands require an authorized Linktrail development checkout with its dependencies installed, or the corresponding supplied toolkit. They are not a public npm install command. Public package and marketplace distribution remain separate from local validation.
The development checkout requires Node.js 22 or later. From that checkout, inspect the CLI:
To keep the ledger in your own project, run the CLI by its absolute path from that project’s directory. Replace the checkout path and example URLs:
check fetches public pages from your machine using the verifier shared with the cloud. It requires network access, but no AgentLinkOps account. It does not install a scheduler. Read the ledger guide before committing or syncing the files. Use doctor to inspect the ledger, verifier, cloud reachability and configured token. A local-only setup can still report missing cloud access. Read the capability status before treating a local command as a hosted feature. Return to the AgentLinkOps overview for the complete campaign flow.