Editorial Policy
LLMScout.tech publishes calculators and articles about what AI APIs actually cost. Those articles carry numbers people use to plan real budgets, so this page explains exactly how they are made: how we choose what to write about, how the figures are verified, where AI assistance fits into the process, how often we publish, and how to tell us when something is wrong.
How we choose topics
Every article starts from a question we have had to answer ourselves, or one that readers keep asking: how much it costs to summarize a long PDF, which model is cheaper for a high-volume classification job, how much text actually fits in a given context window. If a topic cannot be tied to a concrete decision a developer or founder has to make, we do not write it.
Each article also has to add something the provider's own documentation does not: a worked example, a side-by-side comparison, a cost breakdown at realistic volumes. We would rather publish one piece that answers a question completely than three that restate a pricing page.
How the numbers are verified
Prices come from two places. The site fetches live per-token rates through our own pricing endpoint, which reads from OpenRouter; behind it sits a reviewed price table in the repository covering 12 models, a catalog last verified in July 2026. Every entry in that table carries its own last-updated date, and the table is the fallback whenever the live feed is unavailable.
That table is not written from memory. Each rate is checked by web research against the provider's official pricing page before it is committed, and rechecked when a provider announces a change. Token counts, context windows and currency conversion follow the same rules the calculators use, documented in full in our pricing methodology.
How we use AI, and where humans come in
We are direct about this: our articles are produced with AI assistance. Drafting, structuring and translation between English and Portuguese are done with LLM tooling — which is fitting for a site about LLM costs, and not something we see any reason to hide.
What AI does not do is decide what ships. Every article is reviewed by a human at LW Forge before publication. In that review, each price, token count and calculation in the text is checked against the provider's official pricing page and against the site's own calculators; anything that cannot be confirmed is cut rather than softened. Nothing is published without that review.
Publishing cadence
We publish two articles per week, and never more than two in a single day. That ceiling is deliberate. A high volume of thin pages is exactly what search engines treat as scaled content abuse, and it is not how a reference site earns trust — a fixed calendar with human review behind each piece matters more than raw output.
So far we have published 12 articles, each one as a matched English and Portuguese pair, with a minimum of 800 words per language. We do not ship a piece in one language and leave the other waiting.
Automated checks before publishing
Before anything goes live, an automated content audit runs over the whole site. It checks word count per page and per language, looks for duplicated text between pages, verifies that every article has both its English and Portuguese counterpart, and detects broken internal links. Failures block publication until they are fixed. The audit does not replace the human review — it catches the mechanical problems so the review can concentrate on whether the content is accurate and genuinely useful.
Authorship
Articles are published under the LW Forge byline, the software studio that builds and maintains this site. There are no ghost authors and no invented personas. You can read who we are and what we work on in About LLMScout.tech.
Corrections and how to report an error
Pricing corrections are the highest-priority fix on this site. If a rate, a calculation or a claim in an article looks wrong, email contato@lwforge.com with the page, the model and the value you expected. We check the report against the provider's official documentation and correct the page once it is confirmed — usually within a couple of days.
When a correction changes a figure a reader may have relied on, we update the article rather than quietly removing it, and we treat provider price changes as a reason to revisit already published pieces, not only to write new ones.