pi.dev is a terminal coding agent with extension support for custom model providers. Use the community pi-routing-run-provider extension to add routing.run, then select any model id that starts withDocumentation Index
Fetch the complete documentation index at: https://docs.routing.run/llms.txt
Use this file to discover all available pages before exploring further.
route/.
Setup
Add your API key
One-shot example
Run a single prompt without opening an interactive session:Connection prompt
Copy this prompt when another assistant or teammate is helping you configure pi.dev.pi.dev - connect to routing.run
Authentication options
The provider can read your key from any of these locations:| Method | Use when |
|---|---|
~/.pi/agent/auth.json | You want the normal persistent local setup. |
--api-key | You want to pass a key for a single run. |
ROUTING_RUN_API_KEY | You prefer environment variables or shell profiles. |
Recommended models
Published model IDs are listed on the models page. Access depends on your plan tier.| Model | Good for |
|---|---|
route/glm-5.1-fp16 | Strong GLM coding sessions |
route/kimi-k2.6 | Agentic and tool-heavy work |
route/glm-5.1-precision | Higher-precision reasoning |
route/qwen3.6-plus | Balanced coding tasks |
route/deepseek-v4-pro | Long-context reasoning |
Troubleshooting
| Problem | Fix |
|---|---|
| Provider is missing | Run pi install git:github.com/monotykamary/pi-routing-run-provider, then pi list. |
| Authentication fails | Check that the key starts with rk_ and is stored under routing-run. |
| Model is missing or stale | Run pi update git:github.com/monotykamary/pi-routing-run-provider. |
| Invalid model error | Use the full model id, for example route/glm-5.1-fp16. |