Kev (self-hosted): Kev (configured checkpoint)
NewstableKev (configured checkpoint) is available through Everstack's OpenAI-compatible gateway with routing, fallback, retries, and observability.
kev-latestkev
Context
-
tokens
Max output
-
tokens
Input
-
per 1M
Output
-
per 1M
Activity
Daily period usage
Aggregated managed Everstack traffic. Buckets below 5 tenants or 100 requests are withheld.
Providers
ProviderContextInput /MOutput /M
Pricing
| Item | Price | Unit |
|---|---|---|
| Input | - | per 1M tokens |
| Output | - | per 1M tokens |
Performance
Reliability
Compare
Compare usage and performance
Place this model beside up to three other catalog models.
Capabilities
Capabilities
Modalities
Input
Output
Details
- Model ID
- kev-latest
- Family
- kev
- Status
- stable
- Knowledge
- -
- Released
- -
Gateway Config
- API
- default
- Auth
- KEV_API_KEY
- Discovery
- static
- Provider type
- static
Quick Start
index.ts
Endpoint
Base URL
https://api.everstack.ai/v1Chat completions
https://api.everstack.ai/v1/chat/completionsModel
kev-latestAuth env
KEV_API_KEYKev (configured checkpoint) FAQ
What can Kev (configured checkpoint) do?
Kev (configured checkpoint) supports decisions. It accepts text input.
How do I call Kev (configured checkpoint) through Everstack?
Point any OpenAI-compatible SDK at your Everstack gateway and set the model to @kev/kev-latest. Everstack adds retries, provider fallback, caching, per-tenant budgets and OpenTelemetry traces for every request.
