Skip to main content
The AgentLinkOps overview starts with your task. The records beneath that task separate what you want, what a source reported and what a check established. Keeping those records separate makes interrupted work and uncertain evidence easier to review.

​
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. Your ledger stores local intent and notes. Hosted records supply observations and history. Repository context distinguishes manual judgments from dated search and site facts.

​
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. For an idempotent write, preserve both the request’s idempotency value and its arguments. Replay that request after a lost response. A different intended check needs a new value. Read operation-specific errors before retrying; permission refusal and provider unavailability need a change outside the request.

​
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. Competitor research keeps coverage attached to comparisons; 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.