Bring your own API key (or don’t): how we priced AI testing without weird lock-in

Credits vs BYOA — Gemini, Claude, Grok, Groq, OpenRouter, Ollama — and which path fits Free vs Pro teams.

Clean desk with a hardware key metaphor beside a laptop and a BYOA sticky note.

AI features in SaaS often come with two bad options:

  1. Metered mystery usage you can’t predict
  2. “Enterprise only” if you want any control

We tried to avoid both in TestCaseMate.

Platform credits (simple path)

Rough rule: 1 credit ≈ 1 AI-generated test case (image analysis can use credits too when you use platform keys).

Credits reset monthly. They don’t roll over. That sounds strict until you realize rollover encourages hoarding and panic-generating on day 28.

BYOA (Bring Your Own API Key)

On Pro, you can plug in your own keys — Gemini, Anthropic, Grok, Groq, OpenRouter, or even Ollama locally.

BYOA generations don’t burn platform credits. You pay your provider; we stay out of the middle of that meter.

This matters if:

Which should you pick?

Situation Path
Trying the product Platform credits on Free
Steady team usage, hate managing keys Platform credits on Pro
Heavy generation, existing vendor keys BYOA
Strict data policies Ollama / approved provider via BYOA

What we won’t pretend

Model output still needs review. Switching models changes style. Local models can be weaker on long messy stories. You’re buying control and cost shape — not a free lunch.

If that tradeoff feels adult, you’re our kind of user.

Compare Free vs Pro — credits or BYOA, your call.

Open TestCaseMate →