See what AI agents did on your site
Read the Activity tab — what agents looked for, the actions they asked for, where they got stuck, which agents came and from where.
Activity shows what AI agents did on your published site: how much they used it, what they searched for, the actions they asked for, and the calls Flamio refused. Use it to find what agents want from your site and what stops them.
Why it matters
Agents tell you what they came for in their own words. A phrase they search for again and again is a task your site should make easy. A refusal shows where your markup or your sign-in setup gets in the way.
How to read it in the app
Open AI agents and click Activity in the left rail. Select 7 days or 30 days at the top right. Dates are in UTC.
The tab fills once the site is published and its domain verified — until then it reads "No agent activity yet" with Go to Publish. Browser agents see your site's tools on pages with web SDK 0.11.0, which is not released yet; see How AI agents find your site.
The cards
| Card | What it counts |
|---|---|
| Programs | Tasks agents ran on your site in one go, as the Flamio SDK reported them. Needs the agent panel — see below. |
| Calls | Every request agents made to your site's tools: searches, reads and actions. |
| Actions done | Changes agents made through your site's API from a program, and how many of them failed. Needs the agent panel. |
| Refused | Calls Flamio turned down. |
| Signed in | Share of calls made while the visitor was signed in. Shown once your site has a session secret. |
Programs and Actions done come from the Flamio agent panel on your pages, which needs web SDK 0.11.0 and the @flamioai/agent-panel package. Neither is released yet, so both read 0 for now.
Per day draws calls and programs for every day of the period.
What agents look for
Every phrase agents searched or described a task with, however rare, with its kind (Search or Task) and how many times. Emails, phone numbers, long numbers, tokens and people's names are masked.
Where agents got stuck
The calls Flamio refused, by reason and by the place of your site map they were made at:
| Reason | What to check |
|---|---|
| Asked for something the site doesn’t have | Agents expect a page or form you do not tag. Consider tagging it. |
| Sent values the site doesn’t accept | Field names, types or descriptions may be unclear. Add toolparamdescription. |
| Tried to change data with a read | The agent used a read where an action was needed. |
| Only a person may do this | The step is left to the visitor on purpose. |
| The visitor wasn’t signed in | The action needs sign-in. See signed-in pages. |
Actions
Each action agents asked for, at which place, how often it was handed to the agent to run in the visitor's browser, and how often Flamio refused it.
Places, Agents and Countries
Places ranks where agents went on your site, Agents which agents they were, and Countries where they called from.
Related
Keep signed-in pages for signed-in visitors
Generate a session secret so agents get the screens and actions that need sign-in only for a visitor who is signed in to your site.
Flamio Scout
Scout opens your site in a real browser, walks it like a visitor and reports the problems it meets — no testers and no traffic needed.