Key concepts
These are the terms that come up again and again in the dashboard. They are worth reading once: almost every billing question and every metric that looks confusing is answered here.
The life of a page#
Every page in the system always moves through the same sequence of states:
Scraping#
The crawler visits the page and stores its content as text. It is a mechanical operation: no language model is involved and it spends neither optimizations nor tokens. A scraped page is ready to be optimized, but it does not serve any content to agents yet.
Optimization#
A language model rewrites the scraped page: it produces clean Markdown, a summary for llms.txt, a meta description and JSON-LD structured data. Each optimization spends one unit of your plan's monthly package.
Scraped is not the same as optimized. A site can show 289 total pages and only 45 optimized ones: the remaining 244 are scraped and waiting. AI agents only ever receive content from optimized pages.
The two currencies#
AgentFi splits usage into two separate counters, both visible at the bottom of the sidebar. Knowing which one each action spends is what keeps the invoice predictable.
| Optimizations | Tokens | |
|---|---|---|
| What it measures | AI rewrites of a page. | Every piece of LLM work that is not a page rewrite. |
| What spends it | Optimize All, optimizing a single page, re-optimizing with feedback, and every page auto-optimization processes. | Each visibility query × each configured engine; each fire of a recurring schedule; reputation deep-dive follow-ups; and auto-optimization once the package is used up. |
| When it runs out | Manual optimization pauses. Auto-optimization keeps going, but starts spending tokens. | Further spending is billed as Extra usage at your plan's per-token rate. On the Free plan there is no extra usage: scheduled runs pause until the next period. |
The per-plan breakdown is in Plans, tokens and optimizations.
Site metrics#
Visibility queries#
A query is a natural-language question AgentFi sends to AI engines to check whether your site shows up in the answer. There are four kinds:
| Kind | What it is | How it is created |
|---|---|---|
| Brand | Questions that name your brand explicitly. They measure whether the model knows who you are. | Generated automatically from your content. |
| Discovery | Category questions that do not name your brand. They measure whether the model recommends you to someone who does not know you yet. | Generated automatically from your content. |
| Custom | Questions you write by hand for a specific case. | The Add query button. |
| Reputation | Follow-up questions the reputation analysis generates while studying how your brand is perceived. | Reputation analysis. |
High brand visibility (the model knows you when asked by name) combined with low discovery visibility is completely normal. Discovery is the one to push up: it is the one that brings new customers.
Test outcomes#
Infrastructure#
Proxy#
The layer that sits in front of your site and decides what to serve based on who is calling. An AI bot gets the optimized HTML; a person gets the original page from your site. It can run as a Cloudflare Worker (managed by AgentFi) or be self-hosted in your own Nginx or Apache.
Discovery files#
The files an AI crawler uses to work out what is on your site:
llms.txtllms-full.txtrobots.txtsitemap.xml/okf/.Referral#
A visit from a real person who reaches your site from a conversation with an AI. It is detected through the Referer header or the /agentfi/pages/ redirect. Not to be confused with bot visits, which are measured separately in Bot traffic.