
I Watched an AI Agent Make 30+ Failed Requests Trying to Find My API Docs
We run CryptoDataAPI , a market data API for crypto trading bots and AI agents. We had great documentation — a full /llms.txt file, OpenAPI spec, custom docs page. We thought we were set. Then we watched a Claude-based AI agent try to use our API for the first time. It made 30+ HTTP requests before finding a single working endpoint. The Request Log (All 404s) Here's what the agent actually tried, in order: GET /api/v1 → 404 GET /docs → 404 GET /redoc → 404 GET /api/v1/docs → 404 GET /api/v1/openapi.json → 404 GET /openapi.json → 404 GET /documentation → 404 GET /swagger → 404 GET /api-docs → 404 GET /schema → 404 GET /endpoints → 404 After exhausting standard paths, it started brute-force guessing: GET /api/v1/derivatives → 404 GET /api/v1/binance/ticker → 404 GET /api/v1/funding-rates → 404 # ...15 more 404s It then web-searched "cryptodataapi.com API documentation" — no useful results. Eventually it found working endpoints through pure trial and error. The irony? Our /llms.txt file —
Continue reading on Dev.to Webdev
Opens in a new tab

