AxonFlow · Schema

PreCheckResponse

CompanyAI GovernanceAI AgentsPolicy EnforcementAudit LoggingComplianceMCPOpen Source

Properties

Name Type Description
decision_id string The decision identifier, and the CANONICAL name for it. Every other plane that mints a decision calls it `decision_id`: `POST /api/v1/decide`, `POST /api/v1/mcp/check-input`, `POST /api/v1/mcp/check-o
verdict string The CANONICAL answer to "may I do this?", in the same vocabulary and with the same values `POST /api/v1/decide` returns. Read this rather than `approved` in new integrations. Across the governed surfa
approved boolean Whether the request is allowed. RETAINED and not deprecated - every shipped SDK reads it. Prefer `verdict`.
context_id string DEPRECATED ALIAS of `decision_id`, carrying the identical value. Retained because every shipped SDK reads it and removing it would break them all. New integrations should read `decision_id`; this memb
approved_data object Data fetched from MCP connectors
policies array Policies that were evaluated. `segment_resolution_failed` no longer appears here (it did from #3312). No segment gate stands on the pre-check any more: it resolved the caller's governance segments and
rate_limit object
expires_at string When the context expires
block_reason string Reason if request was blocked
trace_id string W3C OpenTelemetry trace_id (32-char lowercase hex) emitted by the decision tracer. Optional: present when the tracer is enabled via AXONFLOW_OTEL_ENDPOINT, omitted otherwise. Policy Enforcement Points
engine string Which policy engine authored this verdict: the ADR-065 decision plane, the only author on this route (PRD v11 §1.1). Omitted on a refusal no engine decided - an authentication failure, or a request re
subject_type string The type of principal the verdict was decided for (PRD v11 §1.6): `User` for a verified user token, `Client` when the request presented no user identity and its client credential is the principal. Omi
policy_bundle string The digest of the policy set that decided: the system corpus's restriction for this route and the organization root - the organization's active typed document composed with the deployment's baseline p
legacy_validators array A checksum validator that acted BEFORE the anchored engine decided (#4122): under an organization's recorded `pii=block` or `pii=redact` detection override, the Indonesia or India validator blocked th
View JSON Schema on GitHub

JSON Schema

axonflow-pre-check-response-schema.json Raw ↑
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "$id": "https://raw.githubusercontent.com/api-evangelist/axonflow/main/json-schema/axonflow-pre-check-response-schema.json",
  "title": "PreCheckResponse",
  "x-generated": "2026-10-09",
  "x-method": "derived",
  "x-generator": "derive-json-schema.py",
  "x-source": "openapi/axonflow-agent-openapi.yml#/components/schemas/PreCheckResponse",
  "type": "object",
  "properties": {
    "decision_id": {
      "type": "string",
      "description": "The decision identifier, and the CANONICAL name for it. Every other\nplane that mints a decision calls it `decision_id`:\n`POST /api/v1/decide`, `POST /api/v1/mcp/check-input`,\n`POST /api/v1/mcp/check-output`, and the AuthZEN adapter's\n`context.decision_id`.\n\nIT IS THE KEY TO ANOTHER ENDPOINT, and that linkage was\npreviously documented nowhere:\n\n  * `GET /api/v1/decisions/{decision_id}/explain` returns the full\n    policy explanation for this decision.\n\nA caller that reads only `context_id` below still has the value, but\nnothing told it that the value works on that endpoint, so\nintegrations built against this plane silently lost a capability\nthat integrations built against `/api/v1/decide` got for free.\n\n`POST /api/v1/overrides` was the second such endpoint until\nv11.0.0. It is keyed on a policy, never on `decision_id`, and from\nv11.0.0 it writes nothing and answers\n`409 LEGACY_POLICY_WRITE_FROZEN` (#4252).\n\nAlso valid for the subsequent `POST /api/audit/llm-call` for five\nminutes, which is what `context_id` was originally named for.\n"
    },
    "verdict": {
      "type": "string",
      "enum": [
        "allow",
        "deny"
      ],
      "description": "The CANONICAL answer to \"may I do this?\", in the same vocabulary and\nwith the same values `POST /api/v1/decide` returns.\n\nRead this rather than `approved` in new integrations. Across the\ngoverned surface the same question was answered by five different\nkeys in two different types - `verdict` (string) on\n`/api/v1/decide`, `approved` (bool) here, `allowed` (bool) on both\nMCP check endpoints, `decision` (bool) on the AuthZEN adapter and\n`decision` (string) on the decisions feed - so a client typed from\none plane could not deserialise another.\n\nSince v11 the pre-check never holds a request: a `require_approval`\npolicy is a deny, because an anchored CHALLENGE is a refusal. So\n`verdict` and `approved` never disagree.\n\nThe AuthZEN adapter (`POST /api/v1/access/evaluation`) keeps its\nboolean `decision` and is not a divergence to be fixed: AuthZEN 1.0\nmandates a boolean, and the four-valued state rides in that\nendpoint's response context behind profile negotiation.\n"
    },
    "approved": {
      "type": "boolean",
      "description": "Whether the request is allowed. RETAINED and not deprecated - every\nshipped SDK reads it. Prefer `verdict`.\n"
    },
    "context_id": {
      "type": "string",
      "deprecated": true,
      "description": "DEPRECATED ALIAS of `decision_id`, carrying the identical value.\n\nRetained because every shipped SDK reads it and removing it would\nbreak them all. New integrations should read `decision_id`; this\nmember will be removed no earlier than the release after the one\nthat introduced `decision_id`.\n"
    },
    "approved_data": {
      "type": "object",
      "additionalProperties": true,
      "description": "Data fetched from MCP connectors"
    },
    "policies": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Policies that were evaluated.\n\n`segment_resolution_failed` no longer appears here (it did from\n#3312). No segment gate stands on the pre-check any more: it\nresolved the caller's governance segments and refused the request\nwhen that failed, on behalf of an organization's segment-scoped\nstatic rows. Those rows no longer decide: the anchored engine\nauthors this verdict and reads no segments (PRD v11 §1.1, §1.2).\n"
    },
    "rate_limit": {
      "$ref": "#/$defs/RateLimitInfo"
    },
    "expires_at": {
      "type": "string",
      "format": "date-time",
      "description": "When the context expires"
    },
    "block_reason": {
      "type": "string",
      "description": "Reason if request was blocked"
    },
    "trace_id": {
      "type": "string",
      "description": "W3C OpenTelemetry trace_id (32-char lowercase hex) emitted\nby the decision tracer. Optional: present when the tracer\nis enabled via AXONFLOW_OTEL_ENDPOINT, omitted otherwise.\nPolicy Enforcement Points propagate this id downstream so\nmulti-gateway decisions stitch into one end-to-end trace.\n"
    },
    "engine": {
      "type": "string",
      "enum": [
        "anchored"
      ],
      "description": "Which policy engine authored this verdict: the ADR-065 decision\nplane, the only author on this route (PRD v11 §1.1). Omitted\non a refusal no engine decided - an authentication failure, or a\nrequest refused before the policy pass ran.\n"
    },
    "subject_type": {
      "type": "string",
      "description": "The type of principal the verdict was decided for (PRD v11 §1.6):\n`User` for a verified user token, `Client` when the request\npresented no user identity and its client credential is the\nprincipal. Omitted wherever `engine` is.\n"
    },
    "policy_bundle": {
      "type": "string",
      "description": "The digest of the policy set that decided: the system corpus's\nrestriction for this route and the organization root - the\norganization's active typed document composed with the\ndeployment's baseline permission pack, or, while it has published\nnothing, the implicit bundle of that pack and the organization\ntemplate. A rollback reinstates an earlier digest. Omitted wherever\n`engine` is.\n"
    },
    "legacy_validators": {
      "type": "array",
      "description": "A checksum validator that acted BEFORE the anchored engine decided\n(#4122): under an organization's recorded `pii=block` or\n`pii=redact` detection override, the Indonesia or India validator\nblocked the request or masked the response ahead of the decision\nplane. Omitted when none did, which is every request without\nsuch an override.\n",
      "items": {
        "type": "object",
        "required": [
          "validator",
          "action"
        ],
        "properties": {
          "validator": {
            "type": "string",
            "enum": [
              "indonesia_pii",
              "india_pii"
            ]
          },
          "action": {
            "type": "string",
            "enum": [
              "blocked",
              "masked"
            ]
          }
        }
      }
    }
  },
  "$defs": {
    "RateLimitInfo": {
      "type": "object",
      "properties": {
        "limit": {
          "type": "integer",
          "description": "Rate limit per window"
        },
        "remaining": {
          "type": "integer",
          "description": "Remaining requests in current window"
        },
        "reset_at": {
          "type": "string",
          "format": "date-time",
          "description": "When the rate limit resets"
        }
      }
    }
  }
}

Work with this as data

Every JSON Schema here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for schemas

4 MCP tools reach this
  • find_json_schemasBrowse and filter every JSON Schema in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This JSON Schema
curl "https://apis.io/api/v1/json-schemas/axonflow-pre-check-response"
All schemas
curl "https://apis.io/api/v1/json-schemas?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.