The routes, side by side
| Included/platform model | Eligible connected account or key | |
|---|---|---|
| What it is | A platform-provided model route | A supported provider account or developer key |
| Billing shape | Yasmine credits and pricing | Paid directly to the selected provider; no Yasmine token markup |
| Eligibility | Available according to the plan/catalog | Only on eligible plans and supported routes |
| Setup | Select an available model | Connect the supported account or store the key encrypted |
| Processing terms | Yasmine's selected platform provider terms apply | The connected provider and account terms apply |
When a connected account fits
On an eligible plan, a supported connected account can use capacity you already purchase from that provider. Provider limits, billing, availability, and terms still apply, so this is not a promise of zero cost or unlimited usage.
When API keys make more sense
Volume: a metered key may suit usage beyond a subscription's limits; provider rate limits and quotas still apply.
Model mixing: keys let you run different models in different channels — Gemini in #research, Claude in #eng.
Cost tracking: a dedicated key gives finance a clean, per-token line item.
What changes by route
- Billing. Included/platform routes use Yasmine credits and pricing; eligible connected routes are paid directly to the provider with no Yasmine token markup.
- Terms. The selected provider processes request content and necessary credentials under its terms.
- Storage. Connected credentials are encrypted and tenant-scoped, then presented only as needed to the selected provider or tool.
Choose an available route in your plan. Free 7-day trial, no card.
TY
The Yasmine Team
Yasmine