Connect your model
Protocols and requests
Supported Chat Completions, Responses, and Messages requests and their boundaries.
Route supported model requests through the base URL supplied by your Integrity deployment. Keep the intended provider, model, and provider authentication configured for that connection.
Supported model protocols#
| Endpoint | Request contract |
|---|---|
| POST /v1/chat/completions | Explicit message history, one response choice, supported function tools, and a positive output-token limit. |
| POST /v1/responses | Explicit supported input history and output-token limit; function and supported custom-tool proposals. |
| POST /v1/messages | Explicit Messages history, tool IDs, and max_tokens for the configured Anthropic-compatible connection. |
Protocol compatibility does not mean every provider feature is supported. Send supported explicit history. Remote Responses history, background requests, opaque referenced items, media evidence, multiple choices, server-executed tools, and legacy function-call syntax are outside the current adapter contract.
Required on every request#
| Header | Purpose |
|---|---|
| x-triage-api-key | Select and authorize the Integrity deployment. |
| x-triage-session-id | Keep the whole task in one persisted session. |
| Idempotency-Key | Identify the distinct request before dispatch. |
Changing only the base URL is insufficient. Your client or harness must attach all three headers, retain identity across reconnects, send explicit limits, and handle holds. See authentication and client configuration.
Review before release#
Your harness executes tools and manages the task. In Enforce mode, the current Base connection verifies the session’s initial compiled input contract before customer inference, then reviews supported action proposals and final outputs before release. It does not rewrite each request or quarantine tool results before inference. Unsupported requests and unavailable required checks hold; the gateway does not silently switch providers or credentials.
For SSE in Enforce mode, content is buffered until release checks finish. Observe relays admitted provider bytes without waiting for review; its later recorded verdict is not an enforced decision. See streaming. For external actions, implement executor authorization.
Operate the connection#
Readiness
Start from the connected deployment and its current state.
Performance
Measure review latency, holds, and known usage.
Security
Keep credentials, workspace access, and action authority scoped.
Limits
Check the supported protocol and capability boundaries.
Versioning
Identify the connection and governing revisions used by a session.