Use case · Data contracts

Make JSON expectations explicit, versioned and testable.

A data contract describes the shape and constraints that a downstream system expects. Zorqelio stores private JSON Schema contracts as immutable versions and validates incoming payloads against the version your workflow selects.

Create a private contract registry

Organize contracts inside a workspace. Each contract has its own access token and a version history. Tokens are returned once and stored as SHA-256 hashes; keep the original token in your own secret manager.

Compare changes before adopting them

Publish an intentional schema update as a new immutable version. Use contract_compare to see added, removed and changed schema paths. Older versions remain available for reproducible validation.

Enforce decisions in your application

Call contract_validate before data reaches a consumer or AI agent. A successful validation returns ALLOW; a contract violation returns BLOCK and issue evidence. Zorqelio does not silently rewrite the source payload.

What Zorqelio does—and does not do

Zorqelio validates JSON that your own integration submits. It does not fetch arbitrary customer URLs, store submitted raw payloads, or guarantee that an upstream provider is available. Its freshness monitor detects missed submissions against an interval you configure.