Request a check

request_check Queue one metered recheck. Subject link rechecks a monitored placement (subjectId is the watch id); subject target rechecks a destination (subjectId is the target id). Reuse the idempotency key when retrying; blocked results remain unknown.

Name recorded in the 2026-10-27 deployment. This page describes current source; verify inputs and access in your connected catalog. Provider configuration and workspace access still apply.

Access	Behavior
`watches:write`	Writes or admits work

Checks and monitoring can consume workspace capacity. Queued admission is not a completed observation; inspect the returned job or saved state.

Example request

Connect through MCP, CLI, or HTTP. Replace example identifiers with records from your workspace.

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "request_check",
    "arguments": {
      "subject": "link",
      "subjectId": "watch_example",
      "idempotencyKey": "recheck-watch_example-2026-09-16"
    }
  }
}

agentlinkops call request_check --args '{"subject":"link","subjectId":"watch_example","idempotencyKey":"recheck-watch_example-2026-09-16"}'

curl --fail-with-body https://app.agentlinkops.com/v1/commands/request_check \
  -H "Authorization: Bearer $AGENTLINKOPS_TOKEN" \
  -H 'Content-Type: application/json' \
  --data '{"subject":"link","subjectId":"watch_example","idempotencyKey":"recheck-watch_example-2026-09-16"}'

Returned result

Schema-validated example; IDs and dates are illustrative. MCP returns this data in structuredContent and in a text content block; generic HTTP and CLI return the JSON result directly. A client requesting supported MCP task handling receives a task handle for the same job or batch instead of this ordinary call result. Poll using the negotiated task methods; see task protocol behavior. A cancellation acknowledgement does not establish that work stopped.

{
  "id": "job_example",
  "workspace_id": "ws_example",
  "project_id": "pr_example",
  "watch_id": "watch_example",
  "type": "link_check",
  "state": "queued",
  "execution_mode": "monitoring",
  "idempotency_key": "recheck-watch_example-2026-09-16",
  "payload_hash": "aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa",
  "attempt_count": 0,
  "max_attempts": 3,
  "lease_token": null,
  "lease_expires_at": null,
  "error_code": null,
  "error_message": null,
  "created_at": "2026-09-13T12:00:00.000Z",
  "updated_at": "2026-09-13T12:00:00.000Z",
  "completed_at": null,
  "replayed": false
}

Input fields

Omit optional fields when you do not want to supply them. Null is accepted only where listed. Unknown input properties are rejected.

Field	Type	Presence	Meaning and constraints
`subject`	string	Required	link for a monitored placement (source page → destination), target for a monitored destination URL. values: `"link"`, `"target"`
`subjectId`	string	Required	The watch id when subject is link, the target id when subject is target. minLength: `1`; maxLength: `200`
`idempotencyKey`	string	Required	Caller-generated key reused only for retries of the same operation and arguments in this workspace. minLength: `1`; maxLength: `200`

Validation and omitted values

subject selects what is checked: link rechecks a monitored placement and subjectId is its watch id; target rechecks a destination and subjectId is its target id. The retired names request_link_check (watchId) and request_target_check (targetId) resolve here with the subject implied and the id renamed. Save the returned job identifier and read get_check_job. A queue response is not a completed observation. Replay the same idempotencyKey for the same intended check. An existing queued/running watch job returns WATCH_BUSY with its job_id; a completed attempt enforces a sixty-second cooldown before a new check. Destination jobs and evidence are independent of source-link presence. Read get_check_job for either subject. Reuse the original idempotencyKey after a lost response. A paused or already-busy destination needs its current state inspected before new admission.

Output fields

Fields inside optional or nullable parents apply only when that parent exists. Common schema conventions explain evidence states, empty lists and extensions.

id (string, required): Resource identifier returned by the operation.
state (string, required): Saved lifecycle or evidence state, as enumerated for this record.
workspace_id (string, required): Workspace that owns this record.
project_id (string, required): Project that owns this record.
watch_id (string, optional): Identifier returned by the related operation.
target_id (string, optional): Identifier returned by the related operation.
type (string, optional).
execution_mode (string, optional).
idempotency_key (string, required): Caller retry identifier, bound to the original request arguments.
payload_hash (string, required).
attempt_count (number, required).
max_attempts (number, required).
lease_token (string / null, required).
lease_expires_at (string / null, required).
error_code (string / null, required): Error code recorded for this result, or null.
error_message (string / null, optional).
created_at (string, required): UTC timestamp when the record was created.
updated_at (string, required): UTC timestamp of the last record update.
completed_at (string / null, required).
replayed (boolean, optional): True when the response reuses an earlier request with the same idempotency value.
usage (object / null, optional).

All fields and nested objects

Types, allowed values, limits and nested fields:

Field	Type	Presence	Meaning and constraints
`id`	string	Required	Resource identifier returned by the operation.
`state`	string	Required	Saved lifecycle or evidence state, as enumerated for this record. values: `"queued"`, `"running"`, `"succeeded"`, `"failed"`, `"cancelled"`
`workspace_id`	string	Required	Workspace that owns this record.
`project_id`	string	Required	Project that owns this record.
`watch_id`	string	Optional	Identifier returned by the related operation.
`target_id`	string	Optional	Identifier returned by the related operation.
`type`	string	Optional
`execution_mode`	string	Optional
`idempotency_key`	string	Required	Caller retry identifier, bound to the original request arguments.
`payload_hash`	string	Required
`attempt_count`	number	Required
`max_attempts`	number	Required
`lease_token`	string / null	Required
`lease_expires_at`	string / null	Required
`error_code`	string / null	Required	Error code recorded for this result, or null.
`error_message`	string / null	Optional
`created_at`	string	Required	UTC timestamp when the record was created.
`updated_at`	string	Required	UTC timestamp of the last record update.
`completed_at`	string / null	Required
`replayed`	boolean	Optional	True when the response reuses an earlier request with the same idempotency value.
`usage`	object / null	Optional
`usage.units`	number	Required
`usage.state`	string	Required	Saved lifecycle or evidence state, as enumerated for this record.
`usage.period`	string	Required

Download input schema · Download output schema

Errors and retries

When retrying with idempotencyKey, reuse the original value and the same arguments; preserve originally omitted optional fields. Generic HTTP puts idempotencyKey in the JSON body, while resource routes use the header where listed below. A changed payload under a reused key can conflict. See error recovery for status, scope, cooldown, cursor and retry handling. Unknown observations are result data and do not establish loss.

HTTP resource routes

These existing resource routes share the operation’s domain behavior. Their parameter placement, status and response envelope can differ from generic invocation. See HTTP route details.

Method and route	Success	Details
`POST /v1/watches/{watchId}/recheck`	202	The URL fixes subject and subjectId. Supply idempotencyKey through the Idempotency-Key header; this resource route reads no JSON body. HTTP 202 admits queued work and does not report a completed observation.
`POST /v1/targets/{targetId}/recheck`	202	The URL fixes subject and subjectId. Supply idempotencyKey through the Idempotency-Key header; this resource route reads no JSON body. HTTP 202 admits queued work and does not report a completed observation.

Continue

get_check_job · get_history Follow the related workflow. See capability status for availability or the command index for another operation.

Overview

MCP, CLI and API commands

CLI client

HTTP and events

Optional local workflows

Example request

Returned result

Input fields

Validation and omitted values

Output fields

Errors and retries

HTTP resource routes

Continue

​Example request

​Returned result

​Input fields

​Validation and omitted values

​Output fields

​Errors and retries

​HTTP resource routes

​Continue

Example request

Returned result

Input fields

Validation and omitted values

Output fields

Errors and retries

HTTP resource routes

Continue