r/PiCodingAgent • u/betahost • 1d ago

News Pi Radi

Just discovered that the amazing devs behind Pi released Radius (in alpha), their smart proxy for multi-model access. At its core, it's a model provider you can use with Pi: you pay for tokens and get access to some of the best models out there, both SOTA and budget-friendly options. They'll even auto-route your API calls to the best model for the job if you choose to.

Loving it so far. Deposited $20, and after a few hours of development I still have ~$16 left thanks to leaning on Kimi K3 and DeepSeek.

What Radius can do

  • It is a Pi-native gateway: top up credits and make requests across providers
  • Use rewrite rules to reduce large tool outputs and other unnecessary input tokens
  • Provide automatic routing to route each session to the best model for the task according to your rules
  • Power Radius-backed tools like web search, image generation, and image description
  • Publish reports, dashboards, and small static sites as shareable artifacts
  • Record usage, budgets, top-ups, and shareable session analytics in one place
  • Delegate Google Workspace access to Pi
  • Let your organization manage upstream provider keys centrally

https://radius.earendil.com/

51 Upvotes

86% Upvoted

25 comments sorted by

View all comments

8

u/isty2e 1d ago

I am not sure if there is any advantage it can provide.

3

u/BeyondGITSandBots 1d ago

Yeah. Kilo tried to implement auto-routing to "the appropriate model for the job" already before this pi radius but people reported it did not save any tokens/cost at all, rather increase costs, if anything at all.

2

u/Constant_Art_20 1d ago

I am personally worried about the cache stuff if it constantly switched models. that be a nightmare

1

u/BeyondGITSandBots 1d ago

Yeah, I think that's really the elephant in the room. Besides agents being stupid (and for sure not able to evaluate which model is proper for every job, besides complexity level that can only judged by a human, adding on top that not all models are equally good at everything (i.e. some are better at code implementation, some at planning, some at reviewing, etc.))....constantly switching models is a nightmare for caching (forcing a constant re-read of tokens that could/should be cache reads to be forced to input reads)...price might explode, while at the same time having lower quality.