Method
The pilot starts with installing the Qommis agent at the entrance of your website. The agent itself sees what AI agents ask for and what they receive.
How it works
You sign the data processing agreement
Before installation: the agent sees your visitors’ IP addresses go by.
The Qommis agent is installed at the entrance of your website
At the CDN, as a reverse proxy or as a middleware in your application, depending on your stack.
It recognises every agent
Each agent request is tied to its assistant and checked against the addresses published by its operator; refusals and fake agents are set apart.
You receive the cross-section report
What the agent saw at the entrance of your website; every exchange remains a dated line, and it belongs to you.
Where to install it
- At the CDN
- A Cloudflare Worker, or its equivalent on your CDN: Akamai or another.
- As a reverse proxy
- In front of your servers, whatever your hosting.
- In your application
- A middleware in your e-commerce application, depending on your stack.
To attach: the sitemap of your product pages, to measure the share of the catalogue that agents read.
The cross-section report
A written report, without any visitor address, in eight parts:
- What the agent saw
- Agents, by assistant
- Agents refused by the site
- Product pages most read by agents
- Probable impersonation
- Humans referred by an AI
- The two signals
- What this report does not say
The Qommis agent
In closed beta. Placed at the entrance of your website, it recognises and verifies every AI shopping agent, answers it with your real data, sends it to the right product page, the right API or the basket, and records every exchange, in Piano or GA4 too.
What do AI agents find at the entrance of your website?
To join the pilot: hello@qommis.com