3 min read
Choose a model
Read the catalogue and choose a model for the job you actually need.
In this guide
A catalogue, not a running job
BRAND’s model catalogue draws on OpenRouter’s public model data. It can include models from OpenAI, Anthropic, Google, and xAI, subject to what the provider lists. Names, model IDs, context limits, and pricing can change; use the catalogue’s source and status when reviewing a choice.
A model selection is required to launch your brand. The choice is stored in the brief; it does not buy credits or execute a generation. The AI worker is deferred; adding a provider credential alone does not activate recurring work.
Match the model to the task
| Question | What to look for |
|---|---|
| What must it produce? | Match the model’s supported inputs and outputs to the work. Text support alone does not establish image generation support. |
| How much context does it need? | Allow room for the brief, approved references, and the response. More context is not automatically a better result. |
| How often will it run? | Compare quality and cost over the expected workload, including retries and revisions. |
| Can you evaluate the result? | Use a small representative task and a clear review standard before allowing repeated paid runs. |
There is no universal best model for every brand. A detailed collection plan and a short product description may need different trade-offs. Treat provider descriptions as information to test, not a guarantee of quality.
Plan for the whole output
Image creation, image editing, mockup rendering, and print-file preparation can involve separate services and charges. A planning model should not be presented as a complete production pipeline simply because it can describe a product.
A model’s published rate is one ingredient in a cost estimate. Input size, generated output, tool calls, retries, and provider rules affect the final charge. The future studio must reserve an estimated maximum before a job and reconcile it with the recorded cost afterward.