The shape of it
You bring a provider, which is an account you already have somewhere and the key for it. Inside that provider you enable models, and each enabled model gets a gateway name that becomes the only name your code needs to know. An API key is what your code sends to reach those models. Around that sit the things that shape a request on its way through. Mappings rewrite a model name. Prompts prepend a system message. Quotas cap what a model may consume. Workflows route a request through logic before it reaches a model at all. Everything above belongs to a workspace. Your plan, your credits and your account settings do not.Pages
Providers
Connect the accounts your models come from
Models
Enable models and give them gateway names
API keys
The credential your applications send
Mappings
Rename a model without touching your code
Prompts
Inject a system prompt into every request
Quotas
Per model limits and the workspace budget
Workflows
Route a request through logic first
Indexes
Crawl a site so the assistant can search it
Metrics and usage
What was called, what it cost, what failed
Workspaces
How work is separated and shared
Applications
OAuth clients for the management API
Account
Plan, security, sessions and deletion