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.
This is an integration planning guide, not a runnable SDK quickstart. Confirm the complete current contract and supported environment with Clariva engineering before implementation.
Conceptual architecture. Unrouted calls and unsupported connectors are outside the represented boundary.
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.
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 explicitlySource review: October 21, 2026; revision 52edd07d06f3. No production endpoint, working credential or runnable SDK example is published here.
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.
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.
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