Models
Organize API addresses, keys, and model IDs, test the connection, then use the model in your tools.
What the four fields mean
| Field | Purpose | Examples and notes |
|---|---|---|
| Name | Helps you recognize a configuration | For example, “Everyday writing” or “Backup coding”; it need not match the model ID |
| Endpoint address | The API endpoint actually provided by the service | Distinguish OpenAI-compatible, Anthropic-compatible, and regional endpoints |
| API Key | A credential for calling the service | Obtain it from the provider; it is not your website sign-in password |
| Model ID | The model identifier accepted by the service | Prefer the model list returned by that service rather than guessing from a product nickname |
Add and verify a model
- Open Models and choose a service from the provider or relay directory, or enter your own service through the available form.
- Check its region, plan, and protocol version. A company’s subscription endpoint and general API endpoint are not necessarily interchangeable.
- Enter the real address and key. Services that support model discovery can return candidate IDs; for other services, use the IDs in their actual documentation.
- Choose a recognizable name and save. Click Test Latency at the top of Config view to check the endpoint’s connection status and latency.
- Then select a supported tool in App Desktop and apply the configuration, or add it to a Smart Routes scheme. Send a request in the real tool or AI Assistant to verify the model’s reply.
Connection tests, replies, and usage answer different questions
Test Latency at the top of Config view checks an endpoint’s connection and latency. It is not a chat test, and cannot on its own confirm that the API Key, model ID, or reply content works correctly. To verify a model, send a request in a real tool or AI Assistant. Usage view queries the balance or quota information exposed by the service.
Actual model requests may be billed under the provider’s rules. A model that replies does not necessarily expose a balance API. Some usage queries need additional settings or authorization, and a failed query does not by itself prove the model is unusable.
Edit, reorder, and delete
Put your usual configurations first and use clear names to distinguish work, everyday, and backup sources. After editing, verify that the address, model ID, and credentials still match, then confirm that the target tool uses the configuration you intended.
Deleting a local entry does not delete the provider account or remotely revoke its API Key. Replace or revoke a key with the provider, then update the configurations that need it in EchoBird.
A common misunderstanding: saving did not change the tool
Models is a configuration library. Saving creates the entry; it does not automatically switch every external client to that model. Next, select the tool in App Desktop and apply the configuration, or reference it in Smart Routes and connect the tool to that scheme.
Compatible endpoints do not imply identical capabilities. Tool calling, image input, context length, and model parameters still require support from the tool, model, and integration adapter.