Does LibreChat need a plugin or a fork?

No. A custom endpoint in librechat.yaml with baseURL the router's /v1 and the key. The router is a standard endpoint; the tool is unchanged.

Which model does the tool get?

Whatever it asks for. The name auto lets the router choose per turn under your policy; a model id pins it and still routes among its providers; a workspace alias maps the tool's own default name to either.

What does the router add that the tool does not have?

One endpoint, every provider. Per-tenant budgets for teams. Every message on the trace.

Can I use my own provider keys?

Yes - connect them under Model providers and the router executes on your accounts; model usage is billed by the provider, the platform meters requests.

LibreChat through the router

LibreChat for the whole team, every message routed and governed.

Add OpenSmartRoute as a custom endpoint in librechat.yaml: one key for every model, the model auto in the picker, budgets per workspace and tenant, and a trace per message.

One endpoint, every provider
Per-tenant budgets for teams
Every message on the trace

Create a free account LibreChat docs

LibreChat settingsbash

export OPENAI_BASE_URL=https://api.opensmartroute.ai/v1
export OPENAI_API_KEY=$OSR_API_KEY
# then: A custom endpoint in librechat.yaml with baseURL the router's /v1 and the key.

LibreChat speaks the OpenAI API; the router serves chat completions and the Responses API at /v1 with streaming, tools and structured output passed through.

Verify

The first turn is on the activity page.

Send one message from the tool and read the row: the model that answered, the cost, the confidence and a link to the full trace with the alternatives and the policy decisions.

verify.shbash

# the tool's next turn is on the activity page with its cost, model and trace
curl -s https://api.opensmartroute.ai/api/v1/activity?limit=3 -H "Authorization: Bearer $OSR_API_KEY"

Questions

LibreChat and the router

Does LibreChat need a plugin or a fork?: No. A custom endpoint in librechat.yaml with baseURL the router's /v1 and the key. The router is a standard endpoint; the tool is unchanged.
Which model does the tool get?: Whatever it asks for. The name auto lets the router choose per turn under your policy; a model id pins it and still routes among its providers; a workspace alias maps the tool's own default name to either.
What does the router add that the tool does not have?: One endpoint, every provider. Per-tenant budgets for teams. Every message on the trace.
Can I use my own provider keys?: Yes - connect them under Model providers and the router executes on your accounts; model usage is billed by the provider, the platform meters requests.

Other tools

The same router behind every tool the team runs.

Put LibreChat behind the router today.

A free account, one key, one command. Every turn the tool makes is priced, governed and explained from then on.

Create a free account Migrating application code instead?

Free plan, no card. Fifteen thousand decisions a month with the full trace.