Run your own container next to your agent
October 26, 2026 · release
@voicethere/cli 0.18.0
Some agents need something that does not fit in the agent bundle: an MCP tool server, a small API, a database wrapper. A project service runs a container image you provide next to your agent. Only your agent can reach it, and nothing is open to the internet. Set it up in the dashboard under Services, or from the CLI.
You give the service an image (a tag or an @sha256 digest), 1 to 4 ports, a health check, and the environment values and secrets it may see. It gets none of your project's values unless you choose them. A private image works too: add a registry credential with the host, a username and a password or token. The password is stored encrypted and is never shown again.
What it costs
A running service uses 45 credits per hour for each unit, where a unit is one vCPU or one GiB, whichever the service uses more of. A half vCPU with 512 MiB takes 23 credits per hour. Billing is per started minute, so a service that runs 61 seconds is billed 2 minutes. An on-demand service is billed only while it is up. The full numbers are in resources and pricing.
When credits run out
A service runs on the same credits as your sessions.
- Free plan: the service stops when the credits run out.
- Paid plan with overage: it keeps running on overage and stops when the organization or project budget limit is reached.
- Paid plan without overage: it stops when the credits run out, like Free.
The check runs at least every 5 minutes, so a service can run a few minutes past the limit before it stops. An always-on service comes back by itself once credits are back, and an on-demand service starts again at the next call from a session. See credits and limits.
On demand or always on
On demand starts the service on the first call from your agent and stops it after it has been idle for the idle stop time (5 to 120 minutes). Always on keeps it running and is part of the paid plans.
From the CLI
CLI 0.18.0 adds commands for services and registry credentials. The registry password is read from stdin.
echo "$REGISTRY_TOKEN" | voicethere projects registry-credentials set acme \
--host ghcr.io --username acme-bot --password-stdin
voicethere projects registry-credentials list
voicethere projects services set tools --image ghcr.io/acme/tools:1.2.0 --registry-credential acme --port mcp:8080 --health http:/health:8080
voicethere projects services list
voicethere projects services show tools
voicethere projects services rotate-token tools
voicethere projects services delete tools
# build for linux/amd64 with local buildx, push, and point the service at it
voicethere services build tools --push ghcr.io/acme/tools:1.2.0
The project service guide covers every field, and the CLI reference lists the other commands. Your agent can call the service's tools from the LLM tab, as described in LLM voice agents.