The two options, side by side
| Your Claude account | Your API keys | |
|---|---|---|
| What it is | The Claude subscription you log into | Metered developer keys (OpenAI, Gemini, Claude) |
| Billing shape | Flat monthly, usage limits that reset | Pay per token, no ceiling |
| Setup in Yasmine | Connect your account — no code | Paste a key — no code |
| Best for | Teams already paying for Claude | Heavy or spiky usage, model mixing |
| Model choice | Claude models | OpenAI, Gemini, or Claude — per channel |
| Whose terms cover your data | Anthropic's — your account | Your provider's — your account |
If you already pay for Claude, start there
Connecting your existing Claude subscription means zero new AI spend: Yasmine works inside the plan you already have, and your usage limits reset on your provider's schedule like always. If your team's limits mostly go unused each week, this is free capacity you're already paying for — put it to work.
When API keys make more sense
Volume: heavy daily use can outgrow a subscription's limits; metered keys never queue.
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.
Either way, three things stay true
- No resale. We never mark up tokens or sit in your billing path — you pay your provider directly.
- Your data, your terms. Conversations flow to your account, covered by your provider's terms. We never access it.
- Switchable. Start on your Claude account today, add keys later — or the reverse. Two-minute change either way.
Connect whichever you have — you're live in 2 minutes. Free 7-day trial, no card.
TY
The Yasmine Team
Yasmine
