Model profiles
The profile describes the specific model of the provider: OpenAI, OpenAI-compatible API or Anthropic, model ID and API key. The key is stored in a secure storage and not shown back. For Anthropic, you can not override the API address: a fixed address protects the key from sending to a swap host. Each profile can be checked with a button on the card: the panel makes a trial call and shows the result (“Verified”, “Error”). The profile assigned to the role can not be deleted, first remove the appointment. Model calls go through a proxy if it is set: existing, new SOCKS5 or HTTP, or through the Axottle node.rolely
The role is responsible for one piece of work. Each is assigned the main model and, if desired, a backup; the backup cannot match the main one, otherwise the main backup path will not remain. The role can be turned off entirely.
The role of “Observer” stands out: assigning a model to it is a complaint detector switch, there is no separate flag. Unlike other roles, it reads every move of the client, including the operator’s dialogues and the AI mode turned off, and never responds to the client, only retrieves a complaint signal. Details on the page Mass incidents.
Roles “Routing”, “Controler” and “Analytician” can already be assigned, but in the conveyor they are not yet involved: the appointment of the model on them now does not affect anything.
