The model is one of the six parts of each task’s kit. Kit chooses it at assembly: based on what needs to be done, not on habit. The category explains which models take part in the work and how we track their cost.
Which models take part
- Engine models — Claude and other models on which Forma’s nodes run. Most of the work goes to them.
- Light model — for purely mechanical steps that repeat down a list: faster and cheaper than the main one.
- External model — for tasks of “text in, text out” where no live access to the environment is needed. Connected through the bridge to any provider with a compatible API, for example DeepSeek or OpenRouter.
How a model is chosen
The more mechanical the task, the lighter the model. A mechanical pass down a list goes to the light or external model, text work without environment access goes to external, everything else goes to the main one. The choice is recorded in the task’s kit, so it is visible and can be checked.
How cost is tracked
Each call’s spend is recorded in the card’s history: tokens, cache reads, time. For an external model the price of the call in dollars and the model name are added. A dollar budget is not set in advance: spend is a statistic by which Core reads the trend.
Access keys to providers are stored only in the project’s environment file and do not get into cards or documentation either.
Leave a Reply