Proto

Models

Choose a model account

Select the account that powers your tasks, test a provider connection, and understand where usage is billed.

For Users and administrators. Based on Proto 0.2.122.

Open Settings → Models. Under Plan, the Account control offers three choices: Proto Managed, Your own API keys, and Codex (ChatGPT).

Proto Managed

This is the default way to start. Proto supplies a managed model, so you do not need to create a separate provider key before your first task. Use the usage information in the app to review your account’s activity.

An ERP.AI connection and the model account have different purposes. The model reasons about the task; your ERP.AI account determines which business apps and records it can access.

Your own API keys

Choose Your own API keys when you want model requests to use your provider account. That provider bills the associated usage.

  1. Obtain a key through the provider account your team has approved.
  2. Enter it in the matching provider field in Models. The API Keys section includes OpenRouter and Fireworks; More providers contains additional provider settings.
  3. Use the connection-test control beside the key. Resolve a missing key, invalid key, or connection error before starting a long task.
  4. Select an available model and try a small task with a result you can check.

For providers that expose a Base URL field, use the address supplied by that provider or your administrator. A URL for a different provider, an extra path segment, or a copied space can break the connection.

Keep keys in the designated settings fields. A support request or ordinary chat message does not need the key itself. If a key is exposed, replace it through the provider and update Proto’s settings.

Codex account option

Choose Codex (ChatGPT), then use Sign in in the ChatGPT account section. Complete the account flow shown by Proto. This is a separate account connection from entering a provider API key.

Choose by task, then verify

A model that writes a good summary may behave differently on a long workflow or a task with images and several tools. Test the actual work: the same input, expected output, and review criteria that you plan to use day to day.

If you change models during evaluation, compare the result and recorded actions as well as speed. Model choice does not change your permission settings or grant access to connected systems.

Understand the data path

Proto stores local files, sessions, and memory on your computer, but the chosen model receives the task content it needs. Using your own key changes the provider account used for those calls; it does not make the task offline. Work involving ERP.AI is also saved to the selected app’s conversation history.

The standard release does not expose local-model setup. Instructions written for development builds can show options that are absent from your installed version.

Need help applying this to your work?Get support