Models & secrets

Models

Premia supports multiple model providers. For each project you can pick the model, and you can bring your own key (BYOK) or use Premia-hosted models.

• BYOK — set your provider key as an org secret (e.g. ANTHROPIC_API_KEY, OPENAI_API_KEY) and Premia routes to your account. You pay the provider directly; Premia doesn't bill for that usage.
• Hosted — use Premia's models; hosted-LLM usage is metered on your invoice (see Billing).

BYOK and model selection are available on every plan, including Free.

Which model writes the code

The code-writing steps — execute, revise and rebase — run through a coding CLI rather than a raw model call, so they only honour your pick when there's a harness for that provider:

Every other step — planning, review, QA, requirements — uses your chosen model directly, whatever the provider. So picking a model without a coding harness still changes most of the pipeline; it just doesn't change who writes the diff.

Secrets

Secrets are encrypted at rest and injected into agent runs. They have a scope hierarchy — environment > repo > org — where more specific overrides less specific.

Manage them in Settings → Secrets, or from the CLI (org scope):

premia secrets list
premia secrets set ANTHROPIC_API_KEY sk-ant-…      # or pipe: echo -n $KEY | premia secrets set ANTHROPIC_API_KEY
premia secrets delete ANTHROPIC_API_KEY

Values are never displayed after they're set — only their names.