AI models used across the platform
A complete map of which AI model powers which feature, why each was chosen, and what the premium-model entitlement on Agency and above means.
Last updated 2026-09-14
Summary#
Metric Vault runs on four AI providers, and the model is chosen per feature rather than per account. A summarizing widget runs on a small fast model; a long-form article or a strategic synthesis runs on a large one. This page lists every feature and the model behind it, so you can judge for yourself what is producing an answer.
Overview#
Four providers are in use.
| Provider | Used for |
|---|---|
| OpenAI | Most research and analysis tools, the assistant, and the in-app chat |
| Anthropic (Claude) | Long-form writing, strategic synthesis, web-grounded checks, and the responsiveness analyzer |
| Google (Gemini) | One of the assistants measured by the AI visibility tools |
| Perplexity | Fact checking with citations, source discovery, and one of the measured assistants |
Two supporting services also run models: Cloudflare Workers AI translates dynamic text, and an image provider generates blog artwork.
A rule runs through the whole table. Where a tool reports on real data, the model is given that data and asked to explain it, not to supply it. The extension's one-line summary, for example, is written from measured figures with an explicit instruction not to introduce any number that was not in the input. The model is a writer there, not a source. Where a tool measures what AI assistants say, no model is used to produce the answer at all: the assistants themselves are asked and their replies are read.
Model choices change as providers release new versions. This page is verified against the shipped code and re-checked when it moves.
Research and analysis#
| Feature | Model | Notes |
|---|---|---|
| All AI research and content tools that run through the main AI endpoint | gpt-4o | Grounded on real search data first. Structured output |
| Full Article Writer | gpt-4o-mini | Chosen for speed. Long articles on the larger model exceed the platform's request time budget |
| Article length retry pass | gpt-4o-mini | Runs only when a draft falls short of its word floor |
| Analyst AI | gpt-4o | Structured output |
| Daily brief on the dashboard | gpt-4o-mini | Short output. Cached once per account per day so a page reload never re-runs it |
| Growth opportunities | gpt-4o | Returns exactly five ranked opportunities |
| In-app chat assistant | gpt-4o | Reads the last 10 messages only |
| Public API analysis endpoint | gpt-4o | See POST /api/v1/analyze |
| Chrome extension one-line insight | gpt-4o-mini | Written only from the measured figures in the same response |
| AI-visibility prompt generation | gpt-4o-mini | Grounded on the brand's real ranking keywords and news mentions |
Writing, synthesis and checking#
| Feature | Model | Notes |
|---|---|---|
| Growth Actions | claude-opus-4-8 | Synthesises your own saved AI-tool results into a ranked queue. Costs 3 credits |
| Blog Studio article generation | claude-opus-4-8 | Structured output against a fixed schema |
| Blog Studio humanizer | claude-opus-4-8 | Returns the reworked passages plus notes |
| Blog Studio title suggestions | claude-opus-4-8 | |
| Blog Studio originality and web check | claude-opus-4-8 | Uses live web search |
| Blog Studio fact check | claude-opus-4-8 | Uses live web search. Extracts up to 6 checkable claims |
| Blog Studio excerpts | claude-haiku-4-5 | Short output, so the small model is the right tool |
| Blog Studio internal-link suggestions | claude-haiku-4-5 | |
| Blog Studio image alt text | claude-haiku-4-5 | |
| Responsiveness analyzer and its follow-up chat | claude-sonnet-5 | The chat keeps the last 10 messages |
| Fact checking outside Blog Studio | Perplexity sonar | Up to 6 claims, each verified separately, verdict is SUPPORTED, DISPUTED or UNVERIFIED with citations |
| Cited-source discovery | Perplexity sonar | Three fixed queries, aggregated to the top 8 source sites |
The assistants measured by AI visibility#
The AI visibility tools do not use a model to write an answer. They send a real category prompt to each assistant and read what comes back. Every available engine is asked at the same time, and an engine that does not respond is left out of the result rather than estimated.
| Shown as | Provider and model | Notes |
|---|---|---|
| ChatGPT | OpenAI gpt-4o-mini | |
| Gemini | Google gemini-1.5-flash | |
| Perplexity | Perplexity sonar | Returns its own citations |
| Claude | Anthropic claude-haiku-4-5-20251001 | Since 2026-09-14. Before that it was claude-3-5-haiku-20241022, an October 2024 model, so Claude figures from before and after that date are not like for like |
| Google AI Overview | Not a model call. Read from the live Google results page | Google only shows an AI Overview for a subset of queries, so its absence is a real finding |
Each probe is capped at a short response so that comparisons across engines are like for like. See Visibility Overview and Google AI Overview Tracker.
Supporting models#
| Feature | Model | Notes |
|---|---|---|
| Dynamic text translation | Cloudflare Workers AI @cf/meta/m2m100-1.2b | Falls back to DeepL where configured. Every translation is cached permanently, so repeated report phrasing is translated once |
| Blog image generation | nano_banana_pro on the image provider | Default output resolution 2k. There is no second provider: when this one is unavailable, generation stops and asks you to try again in a few minutes |
Translation covers 20 languages in the dynamic path: English, Spanish, French, Portuguese, German, Russian, Italian, Dutch, Japanese, Korean, Chinese, Arabic, Hindi, Turkish, Polish, Swedish, Indonesian, Vietnamese, Thai and Ukrainian. The interface itself ships in six. See Supported languages.
Translation fails open: if every provider errors, the original English text is returned rather than a blank space.
Premium models on Agency and above#
The plan comparison lists Premium AI models (Claude Opus) as included from the Agency plan upward, alongside Enterprise and Custom. It is not included on Free or Pro. See Full plan comparison.
This is enforced. On Agency, Enterprise and Custom, the features listed below run on claude-opus-4-8. On Free, Starter and Pro they run on the standard model instead.
Nothing is blocked or refused. Every feature works on every plan that includes it; only the model behind it changes. You will not see an error, an upgrade prompt or a different screen, because the entitlement is about which model does the work, not about whether you may do it. The plan checked is the one belonging to the site owner, so an author or editor working on someone else's site gets that owner's model, which is also whose credits the run draws.
A small number of shorter passes always use the standard model on every plan, including Agency: post translation, and the keyword-overview entity pass. These are short, structured jobs where the premium model makes no practical difference to the output.
If the plan cannot be determined at the moment of a run, for example during a brief database problem, the standard model is used. That keeps the feature working rather than failing, and it is the reason an Agency account may very occasionally see a run that was not on the premium model.
What else is enforced automatically, and what you will run into first:
| Control | How it works |
|---|---|
| Monthly credit allowance | Every premium run draws from your plan's monthly credits. This is the real ceiling on heavy AI use. See How credits work |
| Get Recommendations | Plan-gated and separately metered, with its own monthly allowance per plan. See Get Recommendations |
| White-label branding | Requires Pro or above |
| API keys and the public API | Require Enterprise. See API keys |
The features that run on claude-opus-4-8 for Agency and above are Growth Actions, and the Blog Studio writing, humanizing, title, category, excerpt, originality, fact-check and image-prompt passes. On lower plans those same features run on the standard model.
Note: Model names here are the provider's own identifiers. They are reference information, not something you select. There is no model picker in the interface, and choosing a different model is not a customer setting.
Frequently asked#
Is my content used to train these models? Metric Vault sends your prompts and the grounding data to the provider to get an answer back. What each provider receives is listed in Subprocessors and data flow.
Why does the Full Article Writer use a smaller model than the other writers? Speed. A long article on the larger model takes long enough that the request would exceed the platform's time budget and fail. A finished article beats a timeout.
Why do the AI visibility probes use small models? Because they are not doing the work, they are being measured. The question is what each assistant says about a brand, and the answer needs to be comparable across engines and cheap enough to run at the volume tracking requires.
What happens if a provider is down? It depends on the feature. The AI visibility tools drop the engine that did not answer and report the ones that did. The content checks try the providers in turn and only report AI as unavailable when all of them fail. Translation returns the original text. A tool that depends on one provider returns its error rather than a fabricated result.
Can an administrator change which model runs a feature? Several of the Claude-backed features read their model from platform configuration, so they can be moved to a different model without a code change. That is an operator action, not an account setting.
See also
Was this article helpful?
Thanks — feedback noted for the docs team.