One endpoint
Route model calls through one OpenAI-compatible API surface instead of wiring every provider separately.

Dench API gives teams a unified AI API for applications, agents, internal tools, and automation. Instead of managing separate provider SDKs, keys, billing flows, and request formats, developers can send model calls through a single endpoint built for production usage.
import requests
response = requests.post(
"https://www.dench.com/api/v1/chat/threads",
headers={"Authorization": "Bearer YOUR_API_KEY"},
json={
"model": "gpt-5.4",
"prompt": "Summarize stale deals and draft next steps."
}
)
print(response.json())Route model calls through one OpenAI-compatible API surface instead of wiring every provider separately.
Use the same request shape while moving workloads across supported frontier models as needs change.
Centralize auth, usage tracking, billing, and rate-limit management for production AI applications.
Built for AI applications
Dench API is for teams building chatbots, code generation tools, content automation systems, internal copilots, and autonomous AI agents. The API is designed to sit between your application and the model layer, so provider decisions can change without forcing every product surface to be rewritten.
The practical benefit is operational simplicity. Your team gets one API key pattern, one place to manage access, one billing surface, and one model gateway for production usage. Developers can ship the first request quickly, while operators still get the controls they need when usage moves from prototype to real customers.
Use Dench API when you want OpenAI, Anthropic, and other frontier models available behind one authenticated endpoint. It is a fit for teams that want model flexibility, cleaner infrastructure, and less vendor-specific glue code in the application layer.
Getting started
Sign in to Dench, open workspace settings, and generate an API key from the API keys tab. Keys are scoped to your organization and can be rotated at any time.
POST to the chat endpoint with your key as a Bearer token. The request shape is consistent across every supported model, so the quickstart above works unchanged whichever provider you choose.
Change the model parameter to move a workload between OpenAI, Anthropic, and other frontier models — no new SDK, no separate billing account, no rewritten integration.
Track spend, request volume, and rate limits from your Dench dashboard instead of reconciling invoices across multiple provider consoles.
Dench API supports frontier models from OpenAI, Anthropic, and other leading providers through a single unified endpoint. New models become available without any integration changes on your side.
Create an API key in your Dench workspace settings, then pass it as a Bearer token in the Authorization header for each request.
Yes. Requests use one consistent shape regardless of provider, so moving a workload from one model to another is a one-line change to the model parameter — no new SDK, keys, or billing setup.
Teams use Dench API for chatbots, code generation, content automation, internal copilots, and autonomous AI agents — anywhere an application needs authenticated access to frontier models with centralized usage tracking and rate-limit management.