AI INTEGRATIONS
Keep your AI stack. Connect it to one operating layer.
Use Clyvel around supported SDK, automation and agent-framework traffic so model requests share one layer for observability, cost, reliability and governance.
OPENAI SDK INTEGRATION
OpenAI SDK
Connect OpenAI-compatible SDK traffic to Clyvel for request observability, model routing, provider isolation, latency, token and cost visibility.
Open integration guideN8N INTEGRATION
n8n
Connect n8n AI workflows to Clyvel to observe model requests, latency, token usage, cost, errors and provider activity from one operating layer.
Open integration guideMAKE INTEGRATION
Make
Route supported Make AI requests through Clyvel for LLM observability, cost attribution, latency, error and provider visibility across automations.
Open integration guideLANGCHAIN INTEGRATION
LangChain
Operate LangChain model traffic with Clyvel request observability, latency, token and cost evidence, provider visibility and production controls.
Open integration guideLANGGRAPH INTEGRATION
LangGraph
Observe model traffic generated by LangGraph agents with Clyvel provider, model, latency, token, cost and reliability evidence.
Open integration guideCREWAI INTEGRATION
CrewAI
Connect supported CrewAI model traffic to Clyvel for agent request monitoring, provider visibility, latency, tokens, cost and production reliability evidence.
Open integration guideTHE INTEGRATION MODEL
Connect the model request, not the entire application.
Your workflow tool or framework keeps owning orchestration. Clyvel sits on the supported AI request path so provider, model, latency, tokens, cost and status can be operated consistently across the stack.
01 · Route
02 · Observe
03 · Control
Start with one real request.
Use Guided Connection or the Quickstart, verify that the request appears with trustworthy telemetry, then expand the rollout.