Platform

  • Overview
  • AI Gateway
  • Observability
  • FinOps
  • Reliability

Solutions

  • Optimization
  • Governance
  • Clyvel AI
  • Pricing
  • Enterprise

Resources

  • Documentation
  • Blog
  • Resources
  • Start free

Company

  • Home
  • For businesses
  • Contact
  • Sign in

Legal & security

  • Privacy policy
  • Terms of use
  • Security
  • Refund policy
  • Cookies
  • Data processing
Clyvel

© 2026 Clyvel

Operate

AI GatewayRoute and control every model request.ObservabilitySee every request, token, error and latency signal.ReliabilityIncidents, provider health, latency and failures.

Analyze

Costs & FinOpsUnderstand spend, budgets and cost allocation.OptimizationFind measurable savings across models and routing.

Control

GovernancePolicies, roles, approvals and audit controls.Clyvel AIAsk what changed, why it happened and what to do next.

One platform for production AI operations.

View all products
EngineeringDebug production AI traffic from one operational layer.Platform teamsStandardize routing, providers and reliability controls.FinOps & FinanceControl AI spend, budgets and optimization outcomes.Security & GovernanceApply access, policy and audit controls at scale.
Pricing

QUICKSTART

Send your first request through Clyvel.

Keep your existing provider account. Route one OpenAI-compatible request through Clyvel and confirm that telemetry appears in the platform.

01

Create or select a Clyvel API key

Use the key generated for the environment or workspace that will own this traffic.

02

Point your OpenAI-compatible client at the Clyvel Gateway

Your model-provider account remains separate. Clyvel becomes the operational route for the request.

import OpenAI from "openai";

const client = new OpenAI({
  apiKey: process.env.CLYVEL_API_KEY,
  baseURL: "https://api.clyvel.com/v1",
});

const response = await client.chat.completions.create({
  model: "gpt-5-mini",
  messages: [
    { role: "user", content: "Hello from Clyvel" }
  ],
});
03

Confirm the request in Clyvel

Open Requests and verify model, provider, latency, tokens, cost and status.

Request captured
Cost measured
Latency recorded
04

Add operational controls

Once traffic is visible, configure budgets, alerts, routing and governance according to the workload.

Open API ReferenceBrowse Guides