LibreChat with 6bee.ai
LibreChat adds OpenAI-compatible services as custom endpoints in librechat.yaml. One block is enough.
Before you start
- LibreChat running, with access to its
librechat.yamland.envfiles. - Create an account with a verified email address, add prepaid balance, then create a key on the console's API keys page. Keep the key secret.
- Model IDs are listed in the console and returned by
GET https://api.6bee.ai/v1/models. Replace<model id>with one of them.
Add the endpoint
Put your key in .env as SIXBEE_API_KEY=<your key>, then add this to librechat.yaml:
endpoints:
custom:
- name: "6bee"
apiKey: "${SIXBEE_API_KEY}"
baseURL: "https://api.6bee.ai/v1"
models:
default: ["<model id>"]
fetch: true
titleConvo: true
titleModel: "<model id>"
modelDisplayLabel: "6bee" baseURLhttps://api.6bee.ai/v1, with/v1.models.fetchtruepulls the list fromGET /v1/models.defaultis used if that fails.titleModel- The model that writes chat titles. Each title is a normal, billed request.
Check that it works
- Restart LibreChat so it reads the file.
- Pick 6bee in the endpoint menu and send a short message.
- The request shows up in the console’s usage log.
Shared instances
- Input tokens
- 1,000,000 uncached tokens per rolling minute. Cache hits don’t count.
- Requests
- 60 per minute.
- Concurrency
- 2 requests at a time.
Everyone who uses your LibreChat shares your key, your balance and these limits. The Terms do not allow reselling access or sharing keys without permission.
Troubleshooting
- HTTP 401
- The key is missing or wrong. Copy it again from the console, without spaces or quotes.
- Model not found
- The model ID does not match. List the valid IDs with
GET /v1/modelsor check the console. - HTTP 429
- You are over a per-account limit (requests, input tokens or concurrency). The
Retry-Afterheader says how long to wait. - HTTP 400 on long sessions
- The request no longer fits the model’s context window. Compact or clear the conversation, or switch to a model with a larger window.
- Request rejected for balance
- Each request first reserves its input plus
max_tokensof output. Top up, or lowermax_tokens.