@celigo/api-specs 0.2.156 → 0.2.158

package/dist/api.yml

@@ -3038,7 +3038,13 @@ components:
                   - Premium customers
               inputFilter:
                 type: object
-                description: Filter criteria for branch selection.
+                description: |-
+                  Filter criteria for branch selection. Send `version` and `rules` directly on
+                  `inputFilter` — not inside the `{type: "expression", expression: {...}}` wrapper
+                  that export and import filters use. A wrapped filter is saved without an error,
+                  but the branch is stored with no `inputFilter` and takes every request.
+                x-celigo-ai-guidance:
+                  - Read the API back after saving a branching router and check that each filtered branch still has its `inputFilter`; a filter sent in the export-filter wrapper is dropped on save without an error.
                 properties:
                   version:
                     type: string
@@ -3073,12 +3079,22 @@ components:
                         followed by operands which can be nested expressions.
               nextRouterId:
                 type: string
-                description: Next router to chain to (or "apiRouter" for final routing)
+                description: |-
+                  Next router to chain to, or "apiRouter" for the response router. Every branch needs
+                  one: a branch without it is saved, but every test run of the API is then refused
+                  with 400 "One or more branches are not merged back. Review the setup to ensure all
+                  branches converge.", whichever branch the request takes. An id that names no router
+                  fails the save with 422 "Invalid nextRouterId is defined on the branch. Please
+                  correct the branch configuration."
                 examples:
                   - apiRouter
               pageProcessors:
                 type: array
-                description: Processing steps to execute in this branch
+                description: |-
+                  Processing steps to execute in this branch. An export is a step at most once in an
+                  API: using it again, on another branch or in the same one, fails the save with 422
+                  "The export <id> is already included as a lookup in your API and cannot be added
+                  again."
                 items:
                   type: object
                   properties:
@@ -3344,6 +3360,11 @@ components:
             matches; the typed `context.success` filter doesn't prevent that, because
             `context.success` is true whenever no step failed, including when a lookup found nothing.
             A step that fails with `proceedOnFailure` off selects the `fail` response.
+
+            Send `version` and `rules` directly on `inputFilter`, not inside the
+            `{type: "expression", expression: {...}}` wrapper that export and import filters use. A
+            wrapped filter is saved without an error, but the response is stored with no
+            `inputFilter`, so it matches every request that reaches it.
           properties:
             version:
               type: string

package/dist/guardrail.yml

@@ -593,9 +593,10 @@ components:
       description: |
         LLM configuration for an `ai_agent` guardrail — which provider and model evaluate each
         record, with instructions, parameter tuning, and output format. Guardrails never invoke
-        tools, so unlike an AI agent import no block here accepts a `tools` array; MCP `prompts`
-        and `resources` remain available. Providers come in two families with two configuration
-        formats:
+        tools, so unlike an AI agent import no block here accepts a `tools` array. MCP `prompts`
+        and `resources` are accepted on save, but an unreachable MCP server doesn't fail the
+        run (verified on OpenAI), so put the policy the guardrail must apply in its
+        instructions. Providers come in two families with two configuration formats:
 
         - **Built-in providers** — each has its own configuration block.
           - **openai**: OpenAI models (GPT-4.1, GPT-5, etc.). Configure via the `openai` object.
@@ -759,7 +760,7 @@ components:
         prompts:
           type: array
           description: |-
-            MCP prompt entries available to a catalog-provider guardrail (generic flat format).
+            MCP prompt entries saved with a catalog-provider guardrail (generic flat format).
             Each entry references one MCP connection and the prompt names allowed from it.
           items:
             type: object
@@ -815,7 +816,6 @@ components:
                 - gpt-5-mini
                 - gpt-5-nano
                 - gpt-4.1-mini
-                - gpt-4o
               x-celigo-ui-override: Required by the AI agent configuration form. Encoded here to mirror the form so builders produce connectable configurations.
               x-celigo-ai-guidance:
                 - |-
@@ -1038,7 +1038,7 @@ components:
             prompts:
               type: array
               description: |-
-                MCP prompt entries available to the guardrail's model. Each item references one
+                MCP prompt entries saved with the guardrail. Each item references one
                 MCP connection and the prompt names allowed from it.
               items:
                 type: object
@@ -1227,7 +1227,7 @@ components:
                     prompts:
                       type: array
                       description: |-
-                        MCP prompt entries available to the Gemini model. Each item references one
+                        MCP prompt entries saved with a Gemini guardrail. Each item references one
                         MCP connection and the prompt names allowed from it.
                       items:
                         type: object
@@ -1449,7 +1449,7 @@ components:
                     prompts:
                       type: array
                       description: |-
-                        MCP prompt entries available to the Claude model. Each item references one
+                        MCP prompt entries saved with a Claude guardrail. Each item references one
                         MCP connection and the prompt names allowed from it.
                       items:
                         type: object
@@ -1543,7 +1543,11 @@ components:
           Guardrails never invoke tools. A non-empty `tools` array anywhere under `aiAgent`
           (`aiAgent.tools`, `aiAgent.openai.tools`, `aiAgent.litellm._overrides.gemini.tools`,
           `aiAgent.litellm._overrides.anthropic.tools`) fails the save with 422
-          `guardrail_tools_not_allowed`; MCP `prompts` and `resources` are still accepted.
+          `guardrail_tools_not_allowed`. MCP `prompts` and `resources` are still accepted on
+          save, but don't rely on them for the check: with their MCP server unreachable, a
+          guardrail runs on its instructions and input alone, with no error, where an AI agent's
+          run fails (verified on OpenAI). Put the policy the guardrail must apply in its
+          instructions.
       properties:
         type:
           type: string

package/dist/import.yml

@@ -10668,9 +10668,10 @@ components:
       description: |
         LLM configuration for an `ai_agent` guardrail — which provider and model evaluate each
         record, with instructions, parameter tuning, and output format. Guardrails never invoke
-        tools, so unlike an AI agent import no block here accepts a `tools` array; MCP `prompts`
-        and `resources` remain available. Providers come in two families with two configuration
-        formats:
+        tools, so unlike an AI agent import no block here accepts a `tools` array. MCP `prompts`
+        and `resources` are accepted on save, but an unreachable MCP server doesn't fail the
+        run (verified on OpenAI), so put the policy the guardrail must apply in its
+        instructions. Providers come in two families with two configuration formats:
 
         - **Built-in providers** — each has its own configuration block.
           - **openai**: OpenAI models (GPT-4.1, GPT-5, etc.). Configure via the `openai` object.
@@ -10834,7 +10835,7 @@ components:
         prompts:
           type: array
           description: |-
-            MCP prompt entries available to a catalog-provider guardrail (generic flat format).
+            MCP prompt entries saved with a catalog-provider guardrail (generic flat format).
             Each entry references one MCP connection and the prompt names allowed from it.
           items:
             type: object
@@ -10890,7 +10891,6 @@ components:
                 - gpt-5-mini
                 - gpt-5-nano
                 - gpt-4.1-mini
-                - gpt-4o
               x-celigo-ui-override: Required by the AI agent configuration form. Encoded here to mirror the form so builders produce connectable configurations.
               x-celigo-ai-guidance:
                 - |-
@@ -11113,7 +11113,7 @@ components:
             prompts:
               type: array
               description: |-
-                MCP prompt entries available to the guardrail's model. Each item references one
+                MCP prompt entries saved with the guardrail. Each item references one
                 MCP connection and the prompt names allowed from it.
               items:
                 type: object
@@ -11302,7 +11302,7 @@ components:
                     prompts:
                       type: array
                       description: |-
-                        MCP prompt entries available to the Gemini model. Each item references one
+                        MCP prompt entries saved with a Gemini guardrail. Each item references one
                         MCP connection and the prompt names allowed from it.
                       items:
                         type: object
@@ -11524,7 +11524,7 @@ components:
                     prompts:
                       type: array
                       description: |-
-                        MCP prompt entries available to the Claude model. Each item references one
+                        MCP prompt entries saved with a Claude guardrail. Each item references one
                         MCP connection and the prompt names allowed from it.
                       items:
                         type: object
@@ -11649,7 +11649,9 @@ components:
           `aiAgent.openai.tools`, `aiAgent.litellm._overrides.gemini.tools`, `….anthropic.tools`) —
           any non-empty array fails the save with 422 `guardrail_tools_not_allowed` ("Tools aren't
           supported on a guardrail AI agent configuration…"), on create and on update. `prompts` and
-          `resources` are accepted; the server still echoes `openai.tools: []` on OpenAI guardrails.
+          `resources` are accepted on save, but an unreachable MCP server doesn't fail the run
+          (verified on OpenAI), so put the policy in the instructions. The server still echoes
+          `openai.tools: []` on OpenAI guardrails.
       properties:
         type:
           type: string

package/dist/tool.yml

@@ -460,9 +460,10 @@ paths:
       summary: Delete a tool
       description: |-
         Deletes a tool. Soft-deleted and retained in the recycle bin for 30 days.
-        Fails with 422 if other resources (MCP servers, access tokens) still
-        reference this tool — call `GET /v1/tools/{_id}/dependencies` first to
-        check.
+        Fails with 422 if other resources (MCP servers, access tokens, or a
+        `ToolImport` import whose `tool._toolId` names it: "import <id> must be
+        deleted before you can delete tool <id>") still reference this tool — call
+        `GET /v1/tools/{_id}/dependencies` first to check; it lists those imports.
       operationId: deleteTool
       tags:
         - Tools
@@ -1231,8 +1232,12 @@ paths:
         '422':
           description: |-
             A step failed, or the Tool was refused before any step ran: a connection binding is
-            missing (`connection_not_overridden`) or has no `_id`, or its branches don't all merge
-            back (`tool_dangling_branch`). A failed step answers 422 even when it has
+            missing (`connection_not_overridden`) or has no `_id`, its branches don't all merge
+            back (`tool_dangling_branch`), or the input fails `input.schema` (a missing `required`
+            property answers `tool_input_schema_validation_failed`). The output stage answers 422 too when the stored
+            `output.schema` holds `additionalProperties: false` and the output mappings write a field
+            it doesn't list ("Tool output validation failed: must NOT have additional properties").
+            A failed step answers 422 even when it has
             `proceedOnFailure: true`: the later steps still run, but the response carries the error,
             not the output. Either way the response includes `invocationId` when logging is active,
             so the run can be opened in the run history.
@@ -6354,7 +6359,16 @@ components:
             JSON Schema describing the expected input data structure.
 
             Used for validation, documentation, and AI-assisted tooling.
-            Must be a valid JSON Schema document.
+            Must be a valid JSON Schema document. Leave `$schema` out or name draft-07: a
+            `$schema` naming draft 2020-12 fails the save with 422 "Invalid input.schema -
+            no schema with key or ref ...". An `$id` saves.
+
+            Each invoke's input is validated against it. A missing `required` property
+            refuses the call with 422 `tool_input_schema_validation_failed` ("Tool input
+            validation failed: must have required property '<name>'"), and a failed
+            `pattern` with 422 "Tool input validation failed: <field>: must match pattern
+            ...". A property made required later therefore breaks callers that don't send
+            it.
           additionalProperties: true
           examples:
             - type: object
@@ -6468,6 +6482,11 @@ components:
 
             Used for documentation and validation of the tool's output.
             Must be a valid JSON Schema document.
+
+            The mapped output is validated against it. While the stored schema holds
+            `additionalProperties: false`, `POST /v1/tools/{_id}/invoke` answers 422 "Tool
+            output validation failed: must NOT have additional properties" when the output
+            mappings write a field the schema doesn't list.
           additionalProperties: true
           examples:
             - type: object
@@ -6760,7 +6779,12 @@ components:
                 description: |
                   Filter criteria to determine if this branch should be selected.
 
-                  Uses Celigo's expression-based filter format.
+                  Uses Celigo's expression-based filter format. Send `version` and `rules`
+                  directly on `inputFilter` — not inside the `{type: "expression", expression: {...}}`
+                  wrapper that export and import filters use. A wrapped filter is saved without an
+                  error, but the branch is stored with no `inputFilter` and takes every input.
+                x-celigo-ai-guidance:
+                  - Read the tool back after saving a branching router and check that each filtered branch still has its `inputFilter`; a filter sent in the export-filter wrapper is dropped on save without an error.
                 properties:
                   version:
                     type: string
@@ -6800,6 +6824,13 @@ components:
 
                   Use "outputRouter" as a special terminal value to exit the tool
                   and return the processing results.
+
+                  Every branch needs one. A branch without it is saved, but every invoke is
+                  then refused with 422 and every test run with 400 `tool_dangling_branch`
+                  ("One or more branches are not merged back. Review the setup to ensure all
+                  branches converge."), whichever branch the input takes. An id that names no
+                  router fails the save with 422 "Invalid nextRouterId is defined on the branch.
+                  Please correct the branch configuration."
                 examples:
                   - router_002
                   - outputRouter
@@ -6809,7 +6840,10 @@ components:
                   Processing steps to execute in this branch.
 
                   Each processor references an export (lookup) or import resource
-                  for data retrieval or submission.
+                  for data retrieval or submission. An export is a step at most once in a
+                  tool: using it again, on another branch or in the same one, fails the save
+                  with 422 "The export <id> is already included as a pageProcessor in your
+                  flow, and cannot be added again."
                 items:
                   type: object
                   properties:
@@ -7064,6 +7098,12 @@ components:
 
             Branches can chain to other routers or use the special "outputRouter"
             terminal value to exit the tool.
+
+            A tool saves without `routers`, but it can't run: `POST /v1/tools/{_id}/invoke`
+            and a test run answer 400 `tool_empty_router` ("Tool has no steps configured.
+            Add at least one step before executing the tool."). A full PUT that omits
+            `routers` removes the steps the same way. Put linear steps in one pass-through
+            router with a single branch.
           items:
             $ref: '#/components/schemas/Router'
         aiDescription:
@@ -22136,9 +22176,10 @@ components:
       description: |
         LLM configuration for an `ai_agent` guardrail — which provider and model evaluate each
         record, with instructions, parameter tuning, and output format. Guardrails never invoke
-        tools, so unlike an AI agent import no block here accepts a `tools` array; MCP `prompts`
-        and `resources` remain available. Providers come in two families with two configuration
-        formats:
+        tools, so unlike an AI agent import no block here accepts a `tools` array. MCP `prompts`
+        and `resources` are accepted on save, but an unreachable MCP server doesn't fail the
+        run (verified on OpenAI), so put the policy the guardrail must apply in its
+        instructions. Providers come in two families with two configuration formats:
 
         - **Built-in providers** — each has its own configuration block.
           - **openai**: OpenAI models (GPT-4.1, GPT-5, etc.). Configure via the `openai` object.
@@ -22302,7 +22343,7 @@ components:
         prompts:
           type: array
           description: |-
-            MCP prompt entries available to a catalog-provider guardrail (generic flat format).
+            MCP prompt entries saved with a catalog-provider guardrail (generic flat format).
             Each entry references one MCP connection and the prompt names allowed from it.
           items:
             type: object
@@ -22358,7 +22399,6 @@ components:
                 - gpt-5-mini
                 - gpt-5-nano
                 - gpt-4.1-mini
-                - gpt-4o
               x-celigo-ui-override: Required by the AI agent configuration form. Encoded here to mirror the form so builders produce connectable configurations.
               x-celigo-ai-guidance:
                 - |-
@@ -22581,7 +22621,7 @@ components:
             prompts:
               type: array
               description: |-
-                MCP prompt entries available to the guardrail's model. Each item references one
+                MCP prompt entries saved with the guardrail. Each item references one
                 MCP connection and the prompt names allowed from it.
               items:
                 type: object
@@ -22770,7 +22810,7 @@ components:
                     prompts:
                       type: array
                       description: |-
-                        MCP prompt entries available to the Gemini model. Each item references one
+                        MCP prompt entries saved with a Gemini guardrail. Each item references one
                         MCP connection and the prompt names allowed from it.
                       items:
                         type: object
@@ -22992,7 +23032,7 @@ components:
                     prompts:
                       type: array
                       description: |-
-                        MCP prompt entries available to the Claude model. Each item references one
+                        MCP prompt entries saved with a Claude guardrail. Each item references one
                         MCP connection and the prompt names allowed from it.
                       items:
                         type: object
@@ -23117,7 +23157,9 @@ components:
           `aiAgent.openai.tools`, `aiAgent.litellm._overrides.gemini.tools`, `….anthropic.tools`) —
           any non-empty array fails the save with 422 `guardrail_tools_not_allowed` ("Tools aren't
           supported on a guardrail AI agent configuration…"), on create and on update. `prompts` and
-          `resources` are accepted; the server still echoes `openai.tools: []` on OpenAI guardrails.
+          `resources` are accepted on save, but an unreachable MCP server doesn't fail the run
+          (verified on OpenAI), so put the policy in the instructions. The server still echoes
+          `openai.tools: []` on OpenAI guardrails.
       properties:
         type:
           type: string

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@celigo/api-specs",
-  "version": "0.2.156",
+  "version": "0.2.158",
   "private": false,
   "description": "Public OpenAPI bundles (dist/) and the celigo-cli lint schema pack (schemas.json).",
   "keywords": [

package/schemas.json

@@ -1,7 +1,7 @@
 {
 	"provenance": {
 		"repo": "celigo/integrator-api-specs",
-		"iasCommit": "e8ef66bd",
+		"iasCommit": "e641651b",
 		"generatedAt": "2026-10-21"
 	},
 	"roots": {