Why Pro brings its own model key

An always-on agent calls a model many times. Someone pays for that. Agent host gives you two ways.

Pro: your own key#

On Pro you add your own model key. The app seals it: it is never shown again. Only your provider's model is called with it. The deployment's own keys are never used for a Pro workspace, and no credit is counted. Pro costs the same whether your agent talks a lot or a little, and your model bill goes to your provider.

Premium and Max: credits#

On Premium and Max the built-in AI answers, using the deployment's keys, and a model step costs credits. Premium has 1,000 a month and Max 3,000. A step costs more with a larger model: a small tier costs the least, and the largest costs the most.

What we do not say#

We do not quote the cost per tier. The rates are an assumption that we want to check against the providers' price lists before plans are sold, and quoting them now would be quoting a guess. The plan limits too are current values that may change during early access.

A hard stop#

The tool calls a day are a hard stop, not a bill. An agent that makes too many calls stops for the day. That protects you from a loop more than any alert would.

Which is better#

If you already have a model account and want one agent, Pro is simple and predictable. If you want several agents and do not want to manage a key, Premium or Max is easier, and the credits show you what each run cost in the logs.

What a model provider sees#

Whatever you and the agent say, and what the tools return, is sent to the model that answers. On Pro that is your own provider under your own terms. We say this plainly because it is true of any agent.

See models and keys and credits and usage.