> Keiro Labs API documentation - Models
> Page: https://docs.keirolabs.ai/models.html
> Markdown: https://docs.keirolabs.ai/models.md
> Agent index: https://docs.keirolabs.ai/llms.txt
> API base URL: https://api.keirolabs.ai/v1
> Auth: send "Authorization: Bearer <api-key>" with a key created in the
> Keiro console (https://console.keirolabs.ai/api-keys). Use credentials saved by
> `keiro setup`, or resolve the key from a secret manager or an owner-only
> secret file and pass it to the client explicitly. Never read another
> provider's variable, and never put raw key material in environment
> variables, code, docs, or logs.

# Models

Keiro currently exposes four public paid-beta eb1 model IDs. If you are unsure
which to use, start with `eb1-preview` and change only after measuring your
workload.

## Public models

| Model | Choose it for | Tradeoff |
|---|---|---|
| `eb1-preview` | General reasoning, coding, and application work | Recommended balanced default |
| `eb1-frontier-preview` | The hardest reasoning and synthesis workloads | Prioritizes capability over latency and spend |
| `eb1-fast-preview` | Interactive and latency-sensitive requests | Prioritizes speed over maximum quality |
| `eb1-efficient-preview` | Repeated routine work and cost-aware throughput | Prioritizes efficiency and predictable spend |

These strings are executable API identifiers, not descriptions of private
serving routes. Do not derive or invent other model names from them.

## List available models

Model availability is account- and key-scoped:

```bash
printf 'Keiro API key: '
IFS= read -rs KEIRO_BEARER
printf '\n'

curl -sS https://api.keirolabs.ai/v1/models \
  -H @- <<<"Authorization: Bearer $KEIRO_BEARER" | python3 -m json.tool
```

Use only IDs returned for the key. Authenticated OpenAI-style model entries can
include `rate_limits`; those are configured Keiro limits for the requesting
account and API key, not upstream provider quotas or live route capacity.

## Select by measurement

Evaluate the same representative prompts against the public models you are
considering.
Compare output quality, end-to-end latency, token usage, and billable amount in
the console. Keep safety checks and tool/image workflows in the evaluation;
text-only prompts do not prove capability parity for an agentic application.

Pin the chosen public ID in production configuration. A silent fallback to a
different ID hides access and compatibility errors.

## Missing access or capability

If an expected model is missing, check the selected console organization and
the key's restrictions, then contact support. If an image or tool request
fails with a capability error, select another account-enabled public model or
ask support to confirm the contract. Do not remove required input silently.

## Related pages

- [Quickstart](quickstart.md)
- [Tool calling](tool-calling.md)
- [Images and vision](images-vision.md)
- [Rate and spend limits](rate-and-spend-limits.md)