Reference
The lookup layer of the knowledge base: glossary, credit prices, plan matrix, limits, error codes, shortcuts and release history.
Last updated 2026-08-06
Summary#
Reference is where the exhaustive lists live. Every other category explains something; this one looks something up. If you need the exact price of a tool, the exact wording of an error, the exact ceiling on a limit, or the meaning of a word you just met, the answer is on one of the pages below, complete rather than sampled.
Overview#
These pages are built to be searched, not read end to end. Each is a table or a set of tables, each row is one item, and each is complete for its subject at the time it was last updated. Nothing here samples: a reference page that showed you half the tools or most of the error codes would be worse than none, because you could not tell whether the row you wanted was missing or absent.
Two habits make them useful during a support call or a debugging session:
- Search the page, not the site. Use your browser's find function on the exact string you can see on screen. Error messages and button labels are quoted character for character for this reason.
- Follow the link out for the "why". Reference pages state facts. The article that owns the explanation is always linked from the row or the section.
Money and entitlement#
| Page | Answers |
|---|---|
| Credit cost table | What does this tool cost? Every tool, grouped by price tier, with the tool id used in the API and in exports. |
| Plan capability matrix | What does each plan include, and which of those lines does the platform actually enforce? |
| All limits and quotas | Every numeric ceiling in the product in one place: credits, seats, rate limits, crawl depths, payload sizes, retention. |
Words and messages#
| Page | Answers |
|---|---|
| Glossary | What does this word mean? SEO vocabulary, AI-visibility vocabulary, and Metric Vault's own terms. |
| Error and status codes | What is this code, what caused it, and can I retry? Every machine code and HTTP status the API returns. |
| Badges and status indicators | What does the badge next to a tool name mean? |
| Notification catalog | Which events send an email or raise an in-app alert, and what each one says. |
Using the interface#
| Page | Answers |
|---|---|
| Keyboard shortcuts | Every keyboard shortcut that exists, and the ones people expect but that we do not have. |
| URL parameters | Which parts of the app can be linked to directly, and what each parameter does. |
| Supported languages | Which languages the interface ships in, and what translation covers. |
History and answers#
| Page | Answers |
|---|---|
| Frequently asked questions | The questions asked most often, with short answers and a link to the full article. |
| Release notes | What changed in the product, newest first. |
| Documentation changelog | What changed in this documentation. |
Where to go instead#
Reference does not explain concepts or walk you through a task. If a table has answered "what" and you still need "why" or "how":
- New to the product: start at Quick start: your first result in five minutes and Key concepts and vocabulary.
- Running a tool: How to run a tool and Reading a result.
- Something is broken: Troubleshooting is organized by symptom, not by subsystem.
- Building against the API: API reference.
Note: Numbers on these pages come from the running platform, not from marketing material. Where a figure printed in the interface disagrees with what the platform charges or enforces, the reference page says so and gives you both.
See also
Was this article helpful?
Thanks — feedback noted for the docs team.