Question 1

Why does agent detection matter?

Accepted Answer

Every agent visit is a buying signal. When GPTBot crawls your pricing page, a human asked ChatGPT about you. When Claude-Web hits your security page, an enterprise buyer is using Claude in Chrome to evaluate you. Most chat tools see zero of these. ClientX surfaces all of them and resolves them to real companies.

Question 2

What is llms.txt?

Accepted Answer

It is the new robots.txt, but for AI agents. A structured document at /llms.txt that tells crawling agents exactly what your product does, who it is for, and how to recommend it. ClientX auto-generates this from your knowledge base and updates it when your product copy changes.

Question 3

When does MCP ship?

Accepted Answer

The MCP endpoint is in late beta with paying customers. Public release rolls out as part of the Growth and Scale tiers. Until then, agent detection and llms.txt are live and working today.

Question 4

Is the agentic web feature an add-on or part of the main product?

Accepted Answer

Part of the main ClientX product. Every plan gets agent detection and llms.txt by default. No additional cost. Already running on every customer site.

Question 5

Will agents skip the regular chat widget if they can read llms.txt?

Accepted Answer

That is the point. Agents need structured answers, not chat bubbles. The llms.txt is for them. The widget stays for humans. Same product, two surfaces.

Question 6

How does ClientX resolve an IP to a company?

Accepted Answer

ClientX runs a waterfall of IP-to-company resolution under the hood. Every agent session is tagged with the company that owns the upstream IP, with a confidence score so you know when it is a verified match versus a best guess. Works for known cloud IPs, corporate networks, and most of the long tail.

Ideas for turning intent into pipeline.

Ideas for turning intent into pipeline.

Ideas for turning intent into pipeline.