The agent experience check is the quickest way to see how AI agents get on with your product. Enter a domain at forgeintel.co/agent-experience and Forge visits it the way agents do: it requests your pages as Claude, ChatGPT and Perplexity, reads your agent files, finds your docs, API and MCP server, and calls your API without a key. No account is needed, and every report has its own link at forgeintel.co/r/<your-domain>.

The report

  • Your score, out of 100, with how much it moved since the last check.
  • What stops agents: one line for each stage, with what Forge found.
  • Agent traffic that can’t get through: an estimate, when the check found agents turned away or pages they can’t find (see below).
  • The fixes, biggest gain first. Improve your score opens a free Forge account with your domain, where you get one prompt that applies every fix and can re-check with real agents.

The five stages

Each stage is worth 20 points. Use and Pay only count when they apply. A site with no API or MCP server skips Use, and a product with nothing for agents to pay for skips Pay. Skipped stages show as a dash and are left out of the score, so it’s always measured against what your product actually offers.

How the score works

Each problem Forge finds costs points from its stage, never more than the stage’s 20.
  • The score is the points kept across the stages that apply, out of 100.
  • Overlapping problems are capped. No sitemap, pages agents can’t find and no llms.txt share one cause: agents aren’t told what pages exist. Together they cost at most 18 points, shared out in proportion.
  • Standards you’ve adopted add 2 points each: OpenAPI, MCP, SKILL.md, x402, MPP, UCP, WebMCP, an API catalog, OAuth discovery and Content Signals in robots.txt. Bonus points never lift a product with an open fix to 100.

Agent traffic that can’t get through

When the check finds agents turned away or pages they can’t find, the report estimates the share of agent traffic that doesn’t get through. It combines the share of agents Forge sent that were turned away with, for the rest, the share of pages they can’t find. Hidden pages only count once the check has found at least five pages, so a small site isn’t judged on one page. It’s an estimate from the check, not your traffic. To see your real agent sessions, connect the SDK.

Discovery in the app

Inside Forge, Discovery shows the same score for each product you add, with the full fix prompt to copy, re-scans when you ask, and the paths agents take to your paid routes.