AI Costs & Routing
+Model pricing, subscriptions, cost scenarios and quality-gated model routing.
-
+
++ +
A Practical API-Cost Scenario: Inputs, FX Date and Limits
A CALCULATED illustrative API scenario shows why request volume, cache share, source rates and dated FX must travel with an estimate. Read the article →
-
+
++ +
Local AI vs Cloud AI: The Break-Even Inputs That Matter
A modelled break-even method covering hardware, power, utilisation, API usage, quality and human handling; no universal winner is claimed. Read the article →
-
+
++ +
Cached Input Is a Separate Usage Field, Not Free Extra Context
Keep provider-reported cached input distinct and check model-specific pricing; there is no universal cache definition or hit rate. Read the article →
-
+
++ +
Cheaper-Model-First Routing Needs a Quality Gate
A method for routing to a lower-cost model only when the same acceptance standard still passes; no routing-savings result is claimed. Read the article →
-
+
++ +
LLM or Deterministic Tool? A Decision Framework for Recurring AI Work
Choose code or a model from the task’s acceptance criteria, uncertainty and verification needs—not novelty or a universal cost claim. Read the article →
-
+
++ +
Subscription vs API: Compare Cost per Verified Job, Not a Token Price Guess
A method for comparing subscription and API costs using the same verified-job window without inventing subscription token rates. Read the article →