Your docs are killing AI agents.
We show you where.
Your customers point Claude Code, Cursor and Codex at your docs. Those agents get lost, invent endpoints and give up — and you never hear about it. We send 6 in and film every failure.
We read your site first and show you the squad before you pay. $7 per Gauntlet, one time.
A checker tells you llms.txt is missing.
We show you the agent that died on page 3.
Meet your first Casualty.
A Dummy with one job — make a first successful API call — works through a real docs site until it can't. The screen stamps the exact URL where it gave up.
Sample run shown above. Real Dummy, real docs page — yours will point somewhere else.
It already happened to these.
Some we ran ourselves on docs everyone knows, the rest published by their owners.
This is what $7 hands you.
Not a score. A brief written for your coding agent, quoted below exactly as it shipped on a real run against docs.stripe.com.
## Your role You are a documentation engineer with write access to this site's docs and its agent-facing files. Work on the real repository. Make the changes yourself; do not hand back a plan. ## Why this exists AI coding agents are now a first-class audience for these docs. A developer points Claude Code, Cursor or Codex at docs.stripe.com and asks it to integrate the product. The agent has no nav intuition, no login, no JavaScript and no patience. We sent 6 such agents in, each with one concrete mission and nothing but the public site. 1 of 6 could not finish. Everything below is a real observation from that run, with the artefact that caused it.
#### 1.1 SIGNUP — mission: go from nothing to an API key - What happened: API key retrieval requires account creation on dashboard.stripe.com, which is outside the documentation domain and unreachable from the docs entry point. - Artefact: `https://docs.stripe.com/get-started/account` - Detail: The documentation site directs users to create accounts and retrieve API keys via dashboard.stripe.com, but that dashboard domain is not part of the docs site and no agent can access it from the documentation entry point. A first-time developer following the obvious path hits a wall: the docs explain accounts but cannot provide or display API keys. - Change to make: Add a page to the docs that explains how to retrieve test API keys from the dashboard after signup, or provide a way for agents to access or simulate key retrieval within the documentation domain itself.
Excerpt. The full brief runs 1175 words and carries every casualty, an acceptance test per stage, and a definition of done.
# Stripe Documentation > Documentation map for AI agents and LLM-based tools. > Generated by 404-not-found from a live read of docs.stripe.com. > Review every line before publishing: descriptions are inferred from page titles. ## Pages - [Stripe Documentation](https://docs.stripe.com/) - [Get started Stripe Documentation](https://docs.stripe.com/get-started) - [Common use cases Stripe Documentation](https://docs.stripe.com/get-started/use-cases) - [Accept simple payments for a startup Stripe Documentation](https://docs.stripe.com/get-started/use-cases/startup)
# Agent instructions for Stripe Documentation This file tells an AI agent how to work with docs.stripe.com without guessing. Generated by 404-not-found. The TODO lines are the gaps that killed real agents — fill them in with the true values; we will not invent them for you. ## The product Stripe Documentation — TODO: one sentence on what this product does. ## Base URL
{
"product": "404-not-found",
"host": "docs.stripe.com",
"site": "Stripe Documentation",
"missions": [
{
"callsign": "SPEC-HUNTER",
"stage": "RECON",
"mission": "find and load a machine-readable spec",
"survived": true,
"cause_of_death": null,
"artefact": "https://docs.stripe.com/api/authentication",Generated for you, ready to commit. Where only your team knows a value, the file says TODO: and names what belongs there — we never invent one.
Quoted from the public report on docs.stripe.com — 5 of 6 survived.
Check it against the source reportYou wrote your docs for humans, and they work for humans. Then half your readers turned into agents nobody tested for. An agent that gets lost does not file an issue. It tells your customer your API does not do that.
One purchase. The whole gauntlet.
No dashboard to configure. No score to interpret. You pay, the agents run, you watch.
Fund the run
$7, paid before anything moves. Hosted Stripe checkout, NanoCorp as merchant of record. Every run is funded — nothing runs on the house.
Release the Dummies
6 real agents, 6 jobs your customers actually ask theirs to do: make a first API call, answer a support question, sign up, find your spec.
Watch the Casualty
The first Dummy dies inside 30 seconds. A Cause of Death names the page, the status code, or the parameter it hallucinated.
Take the prompt
You leave with the fix, not a grade: the agent-facing files plus one long prompt for Claude Code, Cursor or Codex. Paste, ship, run it again.
Questions before you run one
The opposite. We do not touch your site or change anything on it. We send agents in to find where they fail, so the ones your customers send can get through.
An agent is reading your docs right now.
It will not tell you how that went.
$7 buys 6 Dummies, the page that breaks them, and the prompt that fixes it.
We read your site first and show you the squad before you pay.