Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.openlens.com/llms.txt

Use this file to discover all available pages before exploring further.

OpenLens reads how AI models actually answer real questions about your brand. To do that we send queries through two channels, and which one we use depends on the model.

​
Two channels, one schedule

For ChatGPT, Perplexity, Gemini, Google AI Mode, Google AI Overviews, and Grok, we send queries through the same chat interfaces consumers use. We work with partner infrastructure providers to send those queries, on a schedule. The responses come back the way a consumer would see them, including citations and the actual UI structure. For Claude and DeepSeek the same approach is not viable at this time, so we use their public APIs. That means we get the same model and the same answers a developer would see, plus search context where the API exposes it. No web UI in the loop. Mechanically the two channels differ. The scoring downstream treats them the same.

​
Why this matters

The chat UIs and the APIs are sometimes different products. Citations, formatting, and live search behavior can differ between what a model returns through its API and what the same model returns inside its consumer-facing chat app. When we can use the chat surface we do. That keeps the measurement honest with what your prospects actually see.

​
FAQ

​
What is the difference between web access and API?

When you log on to chatgpt.com you’re using OpenAI’s consumer product, which wraps the model in a UI with live search, citations, ad rules, and other features that aren’t always in the API. The API gives you the raw model. For most of our supported platforms we measure the consumer surface, because that’s where users actually meet your brand.

​
Why can’t you use the chat UI for Claude and DeepSeek?

Different vendors expose their products differently. For Claude and DeepSeek we use their public API plus search, and the answers are representative of what those models say.

​
How often do you run queries?

Daily, weekly, or monthly on a schedule. You pick the cadence and the time of day (UTC) per project in Settings. You can also kick off an on-demand run anytime: the Run queries button at the top of the dashboard, POST /api/prompts/run via the REST API, or the run_prompts tool via MCP. On-demand runs work independently of the schedule.

​
Do you stress the platforms?

No. Queries are spread across the network and rate-limited, well below normal consumer use.

​
Agent measurement (beta)

The two channels above measure what AI models say about you in their chat surfaces. We also have early support for measuring what AI agents do at your actual site. These channels are in beta. Contact us if you want access.

​
Agent traffic (passive)

With CDN-level access to your site, OpenLens identifies agent traffic as it arrives. You see which agents are hitting your site, what they’re doing, and where they bounce off. We don’t change what your site serves. We record what hits. This is your own infrastructure, with your permission. It’s the cleanest legal posture in the product.

​
Agent visibility (active)

We send live agents at your site and record how they interact. Claude Code, Manus, ChatGPT Agent, and others as they appear. The recording captures where they get stuck, what they extract, what they decide to do, and (where the agent exposes it) what they think while they browse. The chat-surface channels measure model answers. This measures agent behavior on your actual web surface. Different surface, same idea: see your brand the way the AI sees it. Both channels are early. Reach out if you want to be on the alpha.