dario in Docker, on Kubernetes, on a Pi in a closet
Kubernetes · a Pi in a closet. Two base URLs, one key. Anthropic-shaped clients talk to http://localhost:3456; OpenAI-shaped clients — chat/completions and, since 6.3, the Responses API — talk to http://localhost:3456/v1. The key is dario (any value works until you set DARIO_API_KEY, which then has to match).
Docker
docker volume create dario-config
docker run --rm -it -v dario-config:/home/dario/.dario ghcr.io/askalf/dario:latest login --manual
docker run -d --name dario -p 3456:3456 -v dario-config:/home/dario/.dario \
-e DARIO_API_KEY="$(openssl rand -hex 32)" ghcr.io/askalf/dario:latestThe image binds 0.0.0.0, so a key is mandatory; without one dario refuses to start rather than become an open relay for your subscription. No console at all? Start empty with DARIO_ADMIN=1 and provision the first account over HTTP with the admin API. Two replicas sharing accounts need the refresh lock. Docker guide.
Install dario, log in, leave it running
Three commands, once. The proxy binds 127.0.0.1:3456 and holds your login; every tool on the machine shares it. Add a ChatGPT plan with dario add altman and the two fail over to each other.
$ npm install -g @askalf/dario $ dario login # your Claude plan: Pro, Max 5x or Max 20x Login successful. $ dario proxy # leave it running dario · http://localhost:3456 Your Claude subscription is now an API.
Same URL, same key
Something not listed? If it reads ANTHROPIC_BASE_URL or OPENAI_BASE_URL, or has a "Base URL" field, it works. The compatibility matrix says which tools are exercised end-to-end, which are inferred from a shared code path, and which are untested — one honest cell per tool.