Validate Metronome definition

POST/v1/metronomes/validate

Validate an inline workflow definition for basic shape or publish readiness without saving it.

How to call this endpoint

Every ACP API request uses bearer authentication. The examples here show the actual request path, auth header, and body shape that the platform expects.

Path, query, and header parameters

These parameters control which ACP object the endpoint acts on and how the request is processed.

Path parameters
None.
Query parameters
None.

Body schema

Content type: application/json · Required

FieldTypeRequiredDescription
modeshape | publishNoShape validates graph structure only. Publish validates required triggers, branches, resources, loop safety, and reachable end paths.
definitionobjectNo—
definition.executionPolicyobjectNo—
definition.executionPolicy.placementlocal_onlyYesRequires on-prem PostgreSQL, filesystem artifacts, local scraping, local deployable Functions and explicit local inference. Unsupported node kinds and external API Functions fail closed. This placement contract does not replace operator-enforced network egress policy.
definition.nodesobject[]No—
definition.nodes[].idstringNoUnique identifier.
definition.nodes[].typestringNo—
definition.nodes[].positionobjectNo—
definition.nodes[].dataobjectNo—
definition.nodes[].data.kindtrigger | condition | approval | action | code | imagine | function | firecrawl | table | database | ticket | metronome | inference | loop | end | noteNo—
definition.nodes[].data.subtypestringNo—
definition.nodes[].data.labelstringNo—
definition.nodes[].data.descriptionstringNoHuman-readable description.
definition.nodes[].data.configobjectNoKind-specific node configuration, versioned with the workflow. Thread (action) nodes opt into validated runtime results with outputMode=json_schema and a jsonOutputSchema (object or serialized JSON Schema), or the mutually exclusive jsonOutputSchemaFromInput naming one top-level field in the explicitly selected input. An input schema is validated before execution, removed from business input and retained with its fingerprint in the result receipt. The schema requires an object root, is limited to 64 KiB / 12 levels, and supports type, properties, required, additionalProperties (boolean), items, enum, numeric, string-length and array-length bounds, description and title. Unsupported keywords fail publication. maxValidationRetries is 0–2 (default 2). resultMode is inline (default) or artifact; outputKey defaults to data. Requires a Claw worker advertising json_schema_v1. Validated data comes from a dedicated runtime receipt, never assistant text. Failure retains Thread, usage and validation evidence without publishing partial data. Legacy outputMode=structured/json retains summary-parsing semantics until migrated.
definition.edgesobject[]No—
definition.edges[].idstringNoUnique identifier.
definition.edges[].sourcestringNo—
definition.edges[].targetstringNo—
definition.edges[].sourceHandlestringNo—
definition.edges[].targetHandlestringNo—
definition.edges[].labelstringNo—
definition.executionRecoveryPolicyobjectNo—
definition.executionRecoveryPolicy.schemaVersioncomputer_agents_metronome_recovery_policy_v1Yes—
definition.executionRecoveryPolicy.enforcementcheckpointedYes—
definition.executionRecoveryPolicy.inDoubtDefaultpauseYes—
definition.executionRecoveryPolicy.checkpointMaxBytesintegerYes—
nodesobject[]No—
nodes[].idstringNoUnique identifier.
nodes[].typestringNo—
nodes[].positionobjectNo—
nodes[].dataobjectNo—
nodes[].data.kindtrigger | condition | approval | action | code | imagine | function | firecrawl | table | database | ticket | metronome | inference | loop | end | noteNo—
nodes[].data.subtypestringNo—
nodes[].data.labelstringNo—
nodes[].data.descriptionstringNoHuman-readable description.
nodes[].data.configobjectNoKind-specific node configuration, versioned with the workflow. Thread (action) nodes opt into validated runtime results with outputMode=json_schema and a jsonOutputSchema (object or serialized JSON Schema), or the mutually exclusive jsonOutputSchemaFromInput naming one top-level field in the explicitly selected input. An input schema is validated before execution, removed from business input and retained with its fingerprint in the result receipt. The schema requires an object root, is limited to 64 KiB / 12 levels, and supports type, properties, required, additionalProperties (boolean), items, enum, numeric, string-length and array-length bounds, description and title. Unsupported keywords fail publication. maxValidationRetries is 0–2 (default 2). resultMode is inline (default) or artifact; outputKey defaults to data. Requires a Claw worker advertising json_schema_v1. Validated data comes from a dedicated runtime receipt, never assistant text. Failure retains Thread, usage and validation evidence without publishing partial data. Legacy outputMode=structured/json retains summary-parsing semantics until migrated.
edgesobject[]No—
edges[].idstringNoUnique identifier.
edges[].sourcestringNo—
edges[].targetstringNo—
edges[].sourceHandlestringNo—
edges[].targetHandlestringNo—
edges[].labelstringNo—

What the API returns

Each response code below includes the documented payload shape for the ACP API.

200Metronome validation resultapplication/json
FieldTypeRequiredDescription
objectstringNo—
dataobjectNo—
data.okbooleanNo—
data.modeshape | publishNo—
data.metronomeIdstringNo—
data.versionIdstringNo—
data.versionNumberintegerNo—
data.issuesobject[]No—
data.issues[].codestringNo—
data.issues[].messagestringNoMessage text.
data.issues[].nodeIdstringNo—
data.issues[].edgeIdstringNo—
data.issues[].severityerror | warningNo—
Validate Metronome definition
Loading...
Response 200
Loading...
See the ACP quickstart and SDK flow