Skip to main content
monitor_target Register an exact public destination URL for recurring health checks. Duplicates within a project are reused. Each completed check uses one unit of the shared monthly check allowance.
Name recorded in the 2026-10-17 deployment. This page describes current source; verify inputs and access in your connected catalog. Provider configuration and workspace access still apply.
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.

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.

Input fields

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

Validation and omitted values

A normalized destination already registered in this project is reused without replacing its settings. A new destination is due immediately. Destination health checks consume allowance separately from source checks.

Defaults when omitted

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.
  • workspace_id (string, required): Workspace that owns this record.
  • project_id (string, required): Project that owns this record.
  • status (string, required): Resource lifecycle status.
  • cadence_seconds (number, required): Configured check interval in seconds. Scheduling and admission can delay completion.
  • state (string, required): Saved lifecycle or evidence state, as enumerated for this record.
  • observation_state (object, required): Saved observation state. Before the first check, this object can be empty.
  • created_at (string, required): UTC timestamp when the record was created.
  • updated_at (string, required): UTC timestamp of the last record update.
  • last_attempt_at (string / null, required): UTC timestamp of the latest saved attempt, including an inconclusive attempt; null before any attempt.
  • last_success_at (string / null, required): UTC timestamp of the latest complete, conclusive observation; null before one exists. This does not mean the link was present.
  • last_observation_id (string / null, required): Identifier returned by the related operation.
  • next_check_at (string / null, required): Saved scheduling eligibility time in UTC, not a promised completion time. Read status before treating it as an active schedule.
  • overdue_reason (string / null, required): Recorded scheduling or admission delay; null when no delay reason is saved.
  • url (string, required).
  • created (boolean, optional): True when this request created the record; false when an existing record was reused.
  • last_successful_observation_id (string / null, optional): Identifier returned by the related operation.
Types, allowed values, limits and nested fields:
Download input schema · Download output schema

Errors and retries

This write is not annotated idempotent. After a timeout, inspect existing state before repeating it. 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.

Continue

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