Namespaces
A Namespace is a routing container — a named scope that groups a set of deployed model endpoints under a single logical boundary. Every API key is scoped to one namespace, which means the set of models a caller can reach is determined entirely by what has been deployed into that key's namespace.
Namespaces let you build clear separation between environments (development, staging, production), between teams, or between customer tenants — all within a single CleverThis workspace. A production namespace can expose a curated set of models with strict rate limits and cost caps, while a dev namespace gives developers access to a broader set of models with looser constraints.
What's in this section
- Creating a Namespace — step-by-step guide to creating your first namespace
- Managing Endpoints — adding, removing, and configuring the model endpoints within a namespace
Key concepts
Namespace slug — a short, URL-safe identifier (e.g. prod, team-alpha, customer-acme). The slug appears in usage reports and in API logs.
Endpoint — a deployed model or Actor within a namespace. Each endpoint has a model ID (the string callers pass as "model") and optional configuration like rate limits, system prompt overrides, and cost caps.
API key scoping — when you create an API key, you select which namespace it is scoped to. Keys cannot access models from outside their namespace. A single namespace can have many keys; a key belongs to exactly one namespace.
Multi-namespace key support (allowing a single key to span multiple namespaces) is on the roadmap.