Direct API / SDK
Best for teams building an AI feature or gateway into their own product.
Integrations
Connect Clariva before your application calls an AI provider.
Clariva connects at the point where your application would otherwise call an AI provider directly. Choose the path that matches your workflow source.
Starter Paths
Choose the closest connection model.
Use these starter paths to scope how Clariva connects to a workflow source. This is not a connector marketplace; evaluation defines the entry point, policy template, provider route, audit scope, deployment model, authentication approach, and production-readiness requirements for one workflow.
Application entry points
Signed webhook
Best for routing structured workflow events through the deployed Clariva control layer for controlled evaluation.
Workflow systems
CRM workflow
Best for scoping account notes, customer summaries, sales context, and CRM-based AI use. Named-platform connector readiness is confirmed during integration review.
Support workflow
Best for scoping tickets, conversations, summaries, routing, and support quality review. Named-platform connector readiness is confirmed during integration review.
Internal assistant workflow
Best for scoping employee prompts, internal documents, customer context, or assistant requests before provider execution.
Embedded SaaS workflow
Best for product teams adding AI features where tenant, workspace, or user-generated content needs request-path control.
Custom application workflow
Best for internal tools, queues, webhooks, API gateways, or enterprise data paths that need workflow-specific review.
Control requirements
Model route control
Best for teams that need a central place to decide which provider route is allowed.
Stricter review path
Best for custom policy, deployment-model review, SSO, or expanded audit requirements.
Integration Review
What the intake captures.
A focused intake helps determine whether the workflow fits a standard path or requires additional enterprise planning.
Source system
Where the request starts and how the deployed control layer receives it.
Data classes
The types of sensitive text the workflow may contain.
Provider route
The model provider or provider family the workflow expects to use.
Review level
The security, privacy, compliance, or procurement review required before production.
Connection Path
Start with the integration closest to your workflow.
The demo form helps route your request to API/SDK, CRM, support, webhook, or Enterprise Control.
For technical integration details, see the Technical Overview →