# [Agent visits: the request log](https://rebilder.com/help/console/console-visits)

- **Summary:** Every recorded request, newest first: what each column means, how the filters work, and why Googlebot shows up as a crawler.

Agent visits is the raw log: one row per recorded request, newest first, 50 rows per page (use “Older →” to page back, “← Back to latest” to return). With more than one store, pick the store with the switcher pills at the top.



## The columns

| Column | What it means |
| --- | --- |
| Time (UTC) | When the request happened, in UTC (not your local time zone). |
| Kind | Who asked: `agent` (an AI assistant or its fetcher), `human` (a regular browser), `crawler` (a search engine like Googlebot), or `protocol` (a commerce-protocol client probing endpoints like /mcp). |
| Platform | Which agent platform, when identifiable: chatgpt, claude, claude-code, opencode, perplexity, gemini, googlebot, bingbot, or unknown. |
| Verified | Whether a signed request was verified against a trusted platform key. Configure trusted keys to enable this check; an unverified request has no verified identity. |
| Served | What answered: `markdown` (the gateway served the agent text), `html-variant` (pass-through, meaning your normal HTML page; the “variant” wording anticipates a future feature, and today it simply means your standard page), or `protocol`. |
| URL | The page on your store that was requested (hover for the full URL). |
| Render | How long the gateway spent producing the response, in milliseconds. Markdown rendering is pure computation designed to a sub-50ms budget. |

## Filters

Two chip rows above the table filter the log: Kind (all / agent / human / protocol / crawler) and Platform (all, plus each platform). Filters combine, and “No visits match these filters” offers a one-click “Clear filters”.

## Why Googlebot is a crawler that gets HTML

Search crawlers receive your canonical HTML. The gateway serves your existing information in markdown for matching agent requests.