Overview
Ottili Spire 1.2* is the reserved flagship model of the Ottili AI Platform. It is built for the heaviest, deepest reasoning and agentic work of the future — but it is currently reserved* and not yet available*. It deliberately has no public backing model* and is only served once launched*.
Spire is part of a clearly tiered, public model lineup:
- Ottili Vale* — efficient, everyday, cost-effective (Live/GA).
- Ottili Cairn* — the premium tier for demanding engineering and analysis work (Live/GA).
- Ottili Auto* — the adaptive router that picks Vale or Cairn per request (Live/GA).
- Ottili Spire* — the reserved flagship tier; currently reserved, not yet available*.
This article explains what Spire is, why it is reserved, how it is presented publicly, how it compares across the lineup, and how billing through AI credits works once it is published.
What Ottili Spire is
Ottili Spire (public name: Ottili Spire 1.2*) is the flagship tier* of the Ottili AI Platform. The public positioning reads: *"Reserved flagship — planned for a later release."*
Spire is not* the efficient tier (that is Vale) and not* the premium tier (that is Cairn). It is the future-reserved top tier. While it is reserved, Spire deliberately:
- Has no public backing model* — Spire has no published carrier model.
- Has no published technical specs* — context window, output lengths or capabilities are not specified until the model is live.
- Is not on the public OpenAI-compatible surface* — Spire does not appear in the public model list.
- Is not purchasable, not billable* — while Spire is reserved, it is never billed through credits.
Status and availability
Spire carries the public model status reserved*. That means it is earmarked for a later release, but is not yet generally available, not supported, and not intended for real workflows.
The models of the public lineup differ clearly in status:
- Vale, Cairn, Auto* carry the status
active(Live/GA). - Spire* carries the status
reserved.
Spire is deliberately not* an entry with the maturity status Live* in the canonical product-status registry (config/product_truth/feature_status.yaml). It also does not fall under Concept, Planned, In Development, Private Beta, Beta, Rolling Out, Deprecated or Disabled — as a model it is reserved*. How Ottili ONE labels maturity publicly is described in [Understand feature status labels](/docs/understand-feature-status-labels).
Why Spire is reserved
Spire is reserved so that no premature availability, price or carrier model is ever claimed:
- Fail-closed routing* — a request to a reserved model is never silently downgraded to a carrier provider; it fails closed.
- No public backing* — Spire has no configured, purchasable backing model and is only served once launched.
- Honest presentation* — Spire is shown publicly only as "reserved / Coming soon", never as an available model.
Spire compared
| Model | Tier | Status | Role |
|---|---|---|---|
| Ottili Vale 1.2 | efficient | Live / GA | everyday, baseline, cost-effective |
| Ottili Cairn 1.2 | premium | Live / GA | demanding engineering and analysis work |
| Ottili Auto | automatic | Live / GA | picks Vale or Cairn per request |
| Ottili Spire 1.2 | flagship | reserved | not yet available |
Vale is the efficient baseline tier, Cairn the premium tier for serious software and analysis work, and Auto is not its own model but a router. Spire is the future-reserved top tier and deliberately has no public backing model.
How Spire is presented
Spire is shown honestly and consistently at every public surface:
- Public Ottili AI Platform* — as a reserved flagship with the "Coming soon" label and its own flagship marker.
- Operator / console catalog* — Spire appears there as "coming soon" so operators can see the full catalog state.
- Public API* — Spire is excluded from the public OpenAI-compatible model list; a request to Spire fails closed and is not served.
Cost and credits (once published)
While Spire is reserved, there are no* costs and nothing* is billed through credits. Once Spire is published, it uses the same credit system as Vale and Cairn:
- Prepaid via company credits*: Ottili AI is prefunded through a shared, company-scoped credit wallet.
- Reserved and deducted per request*: the cost of a request is reserved and deducted from the wallet on execution.
- Cost control*: per API key and per company, model limits, budget limits and rate limits are enforced.
How credits and plans relate is described in [Understand plans and credits](/docs/understand-plans-and-credits).
Related articles
- [Ottili AI Overview](/docs/ottili-ai)
- [The Ottili Cairn model](/docs/ottili-cairn-model)
- [Dynamic Workforce Engine](/docs/dynamic-workforce-engine)
- [Understand feature status labels](/docs/understand-feature-status-labels)
- [Understand plans and credits](/docs/understand-plans-and-credits)
- [AI credits and usage](/docs/ai-credits-and-usage)
Was this article helpful?
