INTEGRATION GUIDE
Connect Zorqelio over MCP
Zorqelio exposes its data-contract and validation tools through a remote Model Context Protocol endpoint.
https://zorqelio.xyz/mcp
Protocol: MCP over Streamable HTTP, stateless JSON request/response mode. Each request is independent; persistent sessions and resumable event streams are not provided by this transport.
Discover Zorqelio services programmatically
Before selecting tools, an agent or integration can read the public service catalogue at GET https://zorqelio.xyz/api/v1/catalog. It describes the actual service groups, MCP transport, tool names, authentication expectations, and whether pricing or payment is enabled. The catalogue is informational; tool availability and input schemas returned by MCP remain authoritative.
curl https://zorqelio.xyz/api/v1/catalog
Pricing is currently marked not_enabled. Zorqelio does not currently advertise billable per-call prices or claim x402 support. Do not infer that a successful MCP tool call incurs a charge.
Workspace-aware usage attribution
Workspace-authenticated MCP tools are metered against their owning workspace. Contract tools use the contract access token, monitor tools use the monitor token, and workspace-management tools use the workspace token. Stateless JSON/data tools can opt into attribution by including an optional workspaceToken alongside their normal inputs. Existing calls without that optional field continue to work and are not attributed to a workspace.
Connect your MCP client
In an MCP client that supports remote HTTP servers, add a server using the endpoint above. If the client requires a transport selection, choose Streamable HTTP. Client configuration formats vary; follow the client’s current instructions for remote HTTP servers rather than copying a local stdio configuration.
Discover available tools
Use the MCP client’s tool discovery interface to list tools. The workspace workflow usually begins with workspace_create, followed by contract_create and contract_validate.
| Tool family | Tools | Purpose |
|---|---|---|
| Workspace | workspace_create, workspace_list, workspace_token_rotate, workspace_revoke | Isolate customer data and manage workspace access. |
| Contracts | contract_create, contract_get, contract_publish, contract_compare, contract_history, contract_validate | Store versioned JSON Schemas and validate data deterministically. |
| Monitors | monitor_create, monitor_status, monitor_history, monitor_revoke | Detect blocked payloads and missed freshness heartbeats. |
| JSON and quality | json_format, json_diff, json_to_csv, json_schema_validate, data_quality_profile, data_quality_check, data_normalize | Transform, compare, validate and profile JSON data. |
Create a workspace
Call workspace_create with a name (2–120 characters). The response includes workspaceId and workspaceToken. The token is displayed once and is required for workspace operations. Save it securely.
Create a contract
Call contract_create with workspaceToken, name, optional description, and schema. The schema argument is a JSON string. Contract creation returns contractId and a one-time accessToken.
Validate before agent handoff
Call contract_validate with contractId, accessToken, json (the payload as JSON text), and optional version. If omitted, the latest published version is used. The result contains decision, valid, issueCount, and issue paths. Use ALLOW/BLOCK as a deterministic gate in your workflow; do not treat the model’s interpretation as a substitute for checking the structured result.
Version changes safely
Use contract_publish to add an immutable version. Older versions remain available. Use contract_compare to inspect changes and pass a specific version to contract_validate when you need reproducible historical validation.
Security notes
- Workspace, contract and monitor tokens are shown once. Store them in a secret manager.
- Tokens are stored server-side as SHA-256 hashes.
- Raw validation payloads are checked in memory and are not stored by validation operations.
- The Starter subscription enforces 5 contracts and 3 monitors per workspace.
- Do not share a workspace token with untrusted agents; use the narrowest token available for the operation.
See the quickstart for a complete first workflow, or the REST API reference for direct HTTP integration.