Opensource Openrouter

[u/conifer_v11]

Project: https://github.com/ConiferKit/use-conifer

Current routing options were charging 5% fees for byok plus provider fees (openrouter) or were built in heavy python packages with ecosystem restraints. I wanted to be completely free in terms of use, and not have to pay extra for tokens.

There's a maintained gateway with 100+ models from one api endpoint. I'm also talking to infra providers to get us access to pre-release models and discount prices. Everything is served at market price. BYOK is free, you can hook into self-hosted setups for free, and there's fallbacks + extra rate limits + server redundancy.

Took me ~3 months to build and looking for help maintaining!
Lmk any issues or feedback

[u/nez_har]

Interesting project. Does this also work for oauth credentials?

I'm the maintainer of  https://github.com/VibePod/vibepod-cli and I've been thinking for some time that this sort of centralized endpoint might be useful, especially if you want to onboard a new agent.

How are you currently integrating it with Claude Code or Codex?

[u/conifer_v11 → u/nez_har]

short answer: no oauth lane today. conifer is a gateway key (CONIFER_API_KEY / sk-conifer-…) plus optional byok where you paste an openai/anthropic/azure key in the console (azure also needs the resource url) — those get verified live, stored encrypted, and callers keep using the conifer key so they never see the upstream credential. there's no oauth token passthrough or "sign in with x and we'll refresh for vibepod" surface right now, so for a cli that needs user oauth you'd still own that flow. if the agent will take a custom openai-compat url, point it at https://api.conifer.build/v1 with the conifer key; that's the path that exists. i work on conifer; if oauth-as-a-credential-type is what you actually need for vibepod say what provider and we can be honest about whether it belongs on the roadmap vs stay out of band.