Documentation / integration

Start at an execution path your team controls.

This is an integration planning guide, not a runnable SDK quickstart. Confirm the complete current contract and supported environment with Clariva engineering before implementation.

Architecture

Map the path, including the ways around it.

Your application and tenant contextThe engineering owner controls the request, credentials and rollout.
Authenticated Clariva request boundaryRequest validation, configured policy, input preparation and a recorded decision.
Eligible provider path or rejected / held outcomeConfirm all model calls, retries, fallback and any retrieval or tool paths in scope.

Conceptual architecture. Unrouted calls and unsupported connectors are outside the represented boundary.

Current source surface

Use the complete authenticated request contract.

The inspected controller exposes POST /v1/requests/challenge and POST /v1/requests, with product-feature gating, submission permissions, ingress controls and schema validation. Status and result routes are also present. Public SDK contract-adapter sources exist; deployed interoperability was not tested here.

  1. Confirm the current endpoint, authentication, feature entitlement and tenant/workspace provisioning.
  2. Resolve the policy and exact supported input contract; establish the challenge and proof lifecycle with the current SDK or API contract.
  3. Bind the request to the intended tenant, policy and provider route. Do not substitute client-asserted trust metadata for authenticated context.
  4. Handle structured rejection, review hold, execution failure, result and timeout states. Confirm safe retries and idempotency behavior with the owning implementation.
Conceptual orchestration onlyNot executable · no credentials
establish authenticated tenant context
obtain the current governed-request challenge
prepare the policy-bound request using the full contract
submit through the controlled application path
inspect the structured outcome and scoped evidence
handle reject, hold and unavailable states explicitly

Source review: October 21, 2026; revision 52edd07d06f3. No production endpoint, working credential or runnable SDK example is published here.

Before the integration

Agree the responsibilities and supported scope.

Application owner

Map ingress, direct model calls, fallback, retry and bypasses. Identify who controls credentials and rollout. Confirm the smallest implementation point that can answer the reviewer’s question.

Clariva engineering and security

Confirm the supported request contract, policy and transformation scope, tenant identity, provider eligibility, data flow, evidence retention, access and failure behavior.

Retrieval-policy and tool-interception modules are present in source. Their presence does not establish a productized connector, a deployed end-to-end workflow or autonomous action safety. Include those boundaries only after explicit support and validation.

Validation plan

Exercise behavior in the intended environment.

  • Allow, transform, reject and review-required cases relevant to the requirement.
  • Malformed or missing proof, replay, wrong-tenant and wrong-route cases.
  • Unavailable controls, timeouts, retries, fallback and known bypasses.
  • Independent provider or downstream observations for denied execution claims.
  • Task utility, representative load, latency and support cost.

Use agreed synthetic or safely representative data initially. Product tests and provider transactions were not run for this website rebuild.

Define what the reviewer will inspect