Skip to main content
Use this reference to distinguish what you want, what a supplier reported and what a check established. To begin a task, use the task index.

​
Records and ownership

The publisher URL is the source. The cited URL is the target. Source presence and target health are independent. Read evidence states before combining their results. AgentLinkOps stores hosted links, prospects, private contacts, outreach outcomes and monitoring history. Your sender keeps messages and delivery records; AgentLinkOps sends no outreach email. The outreach guide explains the workflow. An optional ledger stores repository intent and notes. Repository context distinguishes manual judgments from dated search and site facts. Customer accounts choose Link type manually. Tags organize links separately from type and observed link attributes. Link types explains saved choices, deliberate clears and retained assessment evidence. Reading a label does not run a new check or classification.

​
Jobs and retries

A queued response confirms admission. It does not confirm the page was fetched or a link found. Save the job identifier and read its terminal result. Even a successful job can produce an unknown observation. When a command accepts idempotencyKey, preserve that value and the unchanged arguments. Replay the same request after a lost response. A different intended check needs a new key. For a write without this field, inspect the saved record and operation outcome before deciding whether to repeat it. Read operation-specific errors before retrying; permission refusal and provider unavailability need a change outside the request. Successful ordinary MCP tool-call responses carry structuredContent. Task-capable asynchronous calls can return a negotiated task handle first. Save that handle and read its terminal result; a handle alone proves no completed observation.

​
Pagination and snapshots

List operations return bounded pages. Treat cursors as opaque values and keep filters consistent while paging. Discovery candidate cursors freeze a stored result snapshot; restart without a cursor when you need newer results. Event consumers apply a full page before storing the next cursor. Source, destination and workspace event feeds have independent cursor histories. Expiry requires the supplied recovery procedure, not an assumption that nothing happened. See sync and export.

​
Usage and coverage

Source and destination checks share allowance. Reserved, consumed and released units describe different stages of work. Discovery and overview usage remain separate from checks. A configured schedule does not guarantee an exact completion time. Reports describe the selected tracked or imported dataset. Missing supplier or corpus rows cannot establish whole-web absence. A competitor lookup covers the competitor’s top backlinks in the index on the day it ran; availability describes which lanes can run. The common schema reference explains recurring field shapes. Error recovery maps response codes to next actions, and the documentation changelog separates new reference coverage from product releases.