Skip to main content
Baseten is a production inference platform with two ways in, and they need different values in Bolna:
  • Model APIs: a supported set of popular open models that Baseten runs for you, called by model slug at one shared URL. Nothing to deploy.
  • Dedicated deployments: you deploy any model, including fine-tunes, to GPUs reserved for you with a short config.yaml and the Truss CLI. Each deployment gets its own URL.
Choose Model APIs to get running in minutes. Choose a dedicated deployment when you need a model Model APIs doesn’t offer, your own weights, or capacity nobody else shares.

Get a Baseten API key

Create a key on the API keys page of your Baseten workspace settings. Bolna sends it as Authorization: Bearer <key>, which is how Baseten’s OpenAI-compatible endpoints authenticate.

Option A: Model APIs

1

Pick a model slug

Open Baseten’s Model APIs list and copy the slug, for example zai-org/GLM-5.3. Some models also have a Fast variant: the same weights with dedicated capacity for higher sustained throughput, under a separate slug with its own pricing and rate limits.
2

Choose Baseten in Bolna

Open Settings → Integrations → LLM → Custom LLM → Add model, or choose + Add custom LLM from the LLM Provider dropdown on an agent. Select Baseten.
Bolna Add custom model dialog with Baseten selected and inference.baseten.co/v1 shown as the endpoint placeholder

Baseten selected: Model APIs endpoint as placeholder, hint for dedicated deployments

3

Register the model

  • Model name: the slug, for example zai-org/GLM-5.3
  • Endpoint URL: https://inference.baseten.co/v1
  • API key: your Baseten API key
  • Family: for example glm
Add custom model dialog with Baseten selected, model zai-org/GLM-5.3, endpoint inference.baseten.co/v1, masked key and family glm

Baseten Model APIs, filled in

Baseten’s context and output limits for a Model API can be lower than the model’s advertised maximum. Check the limits in the Model APIs table before writing a very long system prompt.

Option B: A dedicated deployment

1

Install Truss and sign in

2

Write a config.yaml

Follow Baseten’s Deploy your first model guide. The config names the Hugging Face checkpoint (checkpoint_repository), the GPU and the inference engine. With the TensorRT-LLM engine, no Python code is needed.
3

Deploy

Truss prints a model ID and a deployment ID. Wait until the deployment shows Active in the Baseten dashboard.
4

Register the deployment in Bolna

Choose Baseten in the Add custom model dialog and replace the placeholder with your deployment’s OpenAI-compatible URL:
Use the model name from the deployment’s example request in the Baseten dashboard, and your Baseten API key.
Because the URL points at the production environment, you can promote a new deployment to production in Baseten and your Bolna agents switch to it without a change.

Finish on the agent

On the agent’s Intelligence tab choose custom, pick the Baseten model, save and place a test call.

Troubleshooting

Paste a key from Settings → API keys in the same Baseten workspace that owns the model or deployment.
Use the slug exactly as listed, including the organisation prefix. A Fast variant has its own slug.
The deployment scaled down and is cold-starting. Set a minimum replica count of at least 1 in the deployment’s autoscaling settings for live agents.