C.W.K.
Stream
Lesson 01 of 10 · published

Why Providers Differ — Beyond the Marketing

~14 min · providers, comparison

Level 0Apprentice
0 XP0/100 lessons0/14 achievements
0/120 XP to next level120 XP to go0% complete

Same task, different shapes

Different providers are not just different models behind the same API. They differ in: tokenizer, role naming, structured-output mechanics, tool-call format, system-prompt semantics, refusal calibration, reasoning configuration, multimodal capabilities, pricing, rate limits, and SDK conventions. The differences add up; a prompt tuned for one rarely lands cleanly on another.

The four families to know in 2026

  • Anthropic — Claude family. Strong on long context, XML-tagged prompts, extended thinking, tool use.
  • OpenAI — GPT-5.5 / o-series. Strong on structured outputs (strict JSON schema), reasoning, multimodal.
  • Google — Gemini 2.5 Pro / Flash. Strong on long context, multimodal, native search grounding.
  • Open-source — Llama 4, Qwen 3, Mistral, etc. Run anywhere; quality varies; no provider lock-in.

Why this matters

You will move between providers — for cost, for outage hedging, for regional compliance, for capability. Plan for it. The prompt-engineering work is portable; the wiring isn't.

Code

The differences in one table (mental model)·plaintext
                  Claude         OpenAI         Gemini         OSS
roles             system+user    system+dev+u   system+user    varies
XML tag culture   strong         weak           moderate       varies
strict JSON       via tools      json_schema    response_schema partial
reasoning         extended       o-series       thinking        partial
tool_choice       any/specific   required/named auto/any        varies
token counter     server         tiktoken       SDK            varies

External links

Exercise

Pick one prompt and port it from your primary provider to a secondary one. Note every change you had to make: roles, parameters, output handling, tool format. That list is the porting cost.

Progress

Progress is local-only — sign in to sync across devices.
Spotted a bug or have feedback on this page?Report an Issue

Comments 0

🔔 Reply notifications (sign in)
Sign inPlease sign in to comment.

No comments yet — be the first.