Guides

SillyTavern

Chat with any MiniRouter model in SillyTavern.

SillyTavern is a self-hosted chat frontend for characters and roleplay. Its Custom (OpenAI-compatible) source runs on any chat model in the catalog, or the curated roleplay list, from one balance. See Roleplay for data handling and accountless keys.

Quick start

Step 1 of 5

Get your MiniRouter key

Open the key page in another tab. No account is required.

Key page

https://minirouter.sh/key
Get a key

1 / 5

Switch models

Connect loads the catalog into Model ID. You can also type any ID, even one missing from the list.

Model IDAnswers with
minirouter/auto:roleplayA long-context, low-input-cost model Auto picks.
@preset/your-slugYour saved preset, with up to three models as fallbacks.

Save connection profiles

A profile stores the API type, server URL, key and model. Save one per model, then switch with a slash command.

CommandDoes
/profile-create GLMSaves the current connection as GLM.
/profile GLMSwitches to it.
/profile-listLists your profiles.

Size each turn

These settings shape every turn:

SettingDoes
Context (tokens)Most SillyTavern sends as the prompt. Lower it to cut input cost.
Response (tokens)Most the model writes back.
StreamingShows the reply as it arrives. See Streaming.

Keep Context below the window on the model's page in Models. A prompt over the window fails with context_too_long.

Keep spend in check

Every swipe and regenerate is a new, billed request.

Troubleshooting

Connect succeeds but the model list is empty

Check that the endpoint is exactly https://api.minirouter.sh/v1. Remove any /chat/completions suffix.

404, HTML, or a parse error on every request

Almost always the base URL. Use https://api.minirouter.sh/v1 — the bare host without /v1 also works, but never append /chat/completions to the base URL field; the client adds that path itself.

Error: 400 invalid_request.

401 on every request

Wrong or rotated key. Keys start with mr-live-; after a rotation the old key keeps working for 24 hours, then dies.

Error: 401 invalid_api_key.

Response stops mid-sentence with a credits message

Balance hit $0 mid-stream. The stream ends with a terminal error naming the exact charge for tokens delivered — never a silent close.

Error: 402 insufficient_credits.

Every error code, with its fix: Errors.

Next steps