Also AI & Machine Learning
dolaai.pro
AI agent that edits Unreal Engine 5.7 Blueprints, C++ and levels in the open editor

Unofficial community guide to Claude, Claude Code and the Claude API for developers
Claude AI Dev is an unofficial community guide for Claude, Claude Code and the Claude API. The site states that it is not affiliated with Anthropic and that it turns official documentation and tested development patterns into practical installation guides, model selection advice, agent workflows and migration checklists. It is aimed at developers working with Claude. The input does not give a price for the guide and names its maintainer only as Claude Dev.
“Claude AI Dev is an unofficial community guide to Claude, Claude Code and the Claude API, with installation tutorials, model selection advice, agent workflows and migration notes. The site states that it is not affiliated with Anthropic.”
Simulated from the response GoodForBotsBot received on , not a live answer from any AI assistant.
It gives model facts as text: Opus 5.5 has a 1M-token context window and 128K maximum output, Sonnet 5.5 is priced at $2 and $10 per million tokens, and Haiku 4.5 and Fable 5.1 are described by use case. Contact details are not in the text; the Contact page is only linked. The FAQ states the site is unofficial and links to Anthropic's status page and documentation. The llms.txt file lists the same guides as titled links with short descriptions, adding a section of core topics and official references. The JSON-LD adds an Organization, a WebSite, a last-modified date of 2026-09-30 and three FAQ answers that repeat the homepage's main points.
A model reading this input cannot find the price of Opus 5.5 or any other Claude model, since only Sonnet 5.5 has a stated price. It cannot find the contact address or business details, which sit on a page it did not read. It does not know who the maintainer is beyond the name Claude Dev, whether the guides are free, or how much of the site is written as full articles rather than summaries of linked pages.
Good for Bots report
robots.txt is present and valid. robots.txt is valid, with 1 user-agent group.
Sitemap is present and parses. Sitemap declared in robots.txt, listing 77 URLs.
Describes itself to machines with schema.org JSON-LD. 2 of 4 pages read pass; 1 partly. The homepage carries structured data that no consumer can read: its JSON was escaped into HTML entities by the template, which no consumer decodes. +4.4 with its prompt in Pro.
Content is marked up so a reader can find it. 3 of 4 pages read pass; 1 partly. The page at /blog is partly structured: The outline jumps from h1 to h3, which the standard forbids.
Navigation links expose usable destinations. 18 of 18 assessed homepage navigation links expose usable destinations.
Links and buttons have accessible names. 53 of 53 assessed homepage links and buttons have a nonempty accessible name.
Controls expose roles, states and relationships. 55 of 55 assessed homepage controls and role declarations meet the static role, state and relationship checks.
Each page declares one usable canonical URL. All 4 pages read pass. The homepage declares itself as its canonical URL.
Section links reach an element on the page. All 4 pages read pass. The homepage has 1 section link, and every one reaches an element on the page.
llms.txt is present and well formed. /llms.txt is well formed: 17 links across 3 sections.
llms.txt is descriptive, not a bare link list. /llms.txt is partly descriptive: only 35% of links carry a description. +3.8 with its prompt in Pro.
Serves markdown at its own URL. No /llms-full.txt and no markdown versions linked from llms.txt. +12.5 with its prompt.
Serves markdown when asked for it. None of the 4 pages read pass. Asking the homepage for markdown still returns text/html. +10 with its prompt.
States a position on AI crawlers. robots.txt names no AI crawlers, so every operator has to guess. +5 with its prompt.
Declares AI usage preferences. No usage declaration found in robots.txt or the final successful homepage response header. +2.5 with its prompt in Pro.
Advertises machine-readable resources with typed links. None of the 4 pages read pass. The homepage's links are all ordinary page furniture; none point an agent anywhere. +1.3 with its prompt in Pro.
Earned
46 of the 50 base points above the line, 15 of the 50 agent-layer points below it.
3 prompts away
Still open
Behind the checks below, with prompts in Pro.
For the owner of claudeai.dev
They are in the owner view, ready to paste into Claude Code, Cursor or Codex, beside the badge and rescans.
Select a check to see what we found and how it is graded.
Readable base
45.6 / 50
3.5 of 3.5 points.
robots.txt is valid, with 1 user-agent group.
8.8 of 8.8 points.
Sitemap declared in robots.txt, listing 77 URLs.
4.4 of 8.8 points.
2 of 4 pages read pass; 1 partly. The homepage carries structured data that no consumer can read: its JSON was escaped into HTML entities by the template, which no consumer decodes.
10.5 of 10.5 points.
3 of 4 pages read pass; 1 partly. The page at /blog is partly structured: The outline jumps from h1 to h3, which the standard forbids.
4.4 of 4.4 points.
53 of 53 assessed homepage links and buttons have a nonempty accessible name.
0 of 0 points.
No applicable form fields were observed in the homepage HTML.
2.6 of 2.6 points.
55 of 55 assessed homepage controls and role declarations meet the static role, state and relationship checks.
1.8 of 1.8 points.
All 4 pages read pass. The homepage declares itself as its canonical URL.
0.9 of 0.9 points.
All 4 pages read pass. The homepage has 1 section link, and every one reaches an element on the page.
Agent layer
15 / 50
11.3 of 11.3 points.
/llms.txt is well formed: 17 links across 3 sections.
3.8 of 7.5 points.
/llms.txt is partly descriptive: only 35% of links carry a description.
0 of 12.5 points.
No /llms-full.txt and no markdown versions linked from llms.txt.
0 of 10 points.
None of the 4 pages read pass. Asking the homepage for markdown still returns text/html.
0 of 5 points.
robots.txt names no AI crawlers, so every operator has to guess.
0 of 2.5 points.
No usage declaration found in robots.txt or the final successful homepage response header.
0 of 1.3 points.
None of the 4 pages read pass. The homepage's links are all ordinary page furniture; none point an agent anywhere.
Penalties
− 0
Penalty: 0 of 15 points.
Our crawler reaches the page without being challenged.
Penalty: 0 of 20 points.
Nothing on the homepage tells a crawler to skip it or to withhold its snippet.
Penalty: 0 of 25 points.
The captured homepage HTML contains 515 content words; completeness is not assessed.
Penalty: 0 of 25 points.
robots.txt allows every known search and user-fetch crawler to reach the homepage.
Penalty: 0 of 10 points.
The homepage is served over HTTPS and returns HTTP 200.
Penalty: 0 of 3 points.
The homepage provides both a non-empty title and meta description.
Penalty: 0 of 3 points.
The homepage is reached in 0 redirects.
Penalty: 0 of 3 points.
The homepage reached a plain crawler in 348 ms.
Agent capabilities
0 of 11 · no points
Each one found adds +1 to the badge.
Adds +1 to the badge when found.
No API catalog published.
Adds +1 to the badge when found.
No /auth.md published.
Adds +1 to the badge when found.
No AI Catalog published, so no MCP server card can be discovered.
Adds +1 to the badge when found.
No A2A Agent Card at /.well-known/agent-card.json, and none listed in an AI Catalog.
Adds +1 to the badge when found.
No usable Agent Skills index was found at either well-known path or in the AI Catalog.
Adds +1 to the badge when found.
No WebMCP declarations were found in the collected HTML or inline scripts. External scripts were not inspected.
Adds +1 to the badge when found.
No Web Bot Auth key directory at /.well-known/http-message-signatures-directory.
Adds +1 to the badge when found.
No HTTP 402 payment challenge on the homepage or robots.txt, and no manifest at /.well-known/x402.
Adds +1 to the badge when found.
No ACP discovery declaration established at /.well-known/acp.json.
Adds +1 to the badge when found.
No UCP discovery declaration established at /.well-known/ucp.
Adds +1 to the badge when found.
No public AMP discovery declaration established. Private or hidden agents may not advertise one to our crawler.
It decides which conditional checks apply. “Not established” means no proof in what we read, not proof of absence.
Access & usage policy
GoodForBotsBot received HTTP 200 via a direct request. No indexing restriction was observed in the supported homepage directives.
Sampled URL: https://claudeai.dev/
No matching refusal for this URL was found for the listed identities.
Declared allow · Scan admission
The recorded robots admission decision allowed our crawler to proceed.
GoodForBotsBot admission along the homepage request chain
https://claudeai.dev/
Declared allow · robots.txt
No matching refusal for this URL in the applicable robots group. This is a declaration, not an access test.
Acquisition of https://claudeai.dev/
https://claudeai.dev/robots.txt
User-agent: * allow: /
robots.txt is present and validStates a position on AI crawlersAllows search and user-fetch crawlers
GoodForBotsBot received HTTP 200 via a direct request.
Observed · Direct request
Our request received HTTP 200. A status alone does not identify a WAF.
Our recorded direct transport attempt; intermediate attempt URLs are not retained
https://claudeai.dev
HTTP 200
Observed · Final homepage response
GoodForBotsBot received HTTP 200 via a direct request.
homepage response
https://claudeai.dev/
HTTP 200 Transport: direct
Serves the homepage over HTTPS with HTTP 200Serves our crawler without a challenge
No indexing restriction was observed in the supported homepage directives.
Not observed · Homepage directives
No indexing restriction was observed in the supported homepage directives.
homepage response
https://claudeai.dev/
No snippet restriction was observed in the supported homepage directives.
Not observed · Homepage directives
No snippet restriction was observed in the supported homepage directives.
homepage response
https://claudeai.dev/
No applicable preference for this use was established.
Unstated · AIPREF Content-Usage
No applicable AIPREF preference was established for this purpose.
Purpose: search; applicable robots group/path and this response's header
https://claudeai.dev/
No applicable preference for this use was established.
Unstated · AIPREF Content-Usage
No applicable AIPREF preference was established for this purpose.
Purpose: ai-use; applicable robots group/path and this response's header
https://claudeai.dev/
No applicable preference for this use was established.
Unstated · AIPREF Content-Usage
No applicable AIPREF preference was established for this purpose.
Purpose: train-ai; applicable robots group/path and this response's header
https://claudeai.dev/
In its category
Category average 57. The percentile appears once the catalogue holds a few hundred sites.
Every scan is kept. Pro draws the history as a chart →
The homepage and up to three pages from the sitemap and homepage links. Structured data, page structure, Markdown negotiation and typed links check each page read and take the median page; other checks read the homepage.
More like Claude AI Dev:DocumentationAI & Machine LearningDevelopers
Also AI & Machine Learning
dolaai.pro
AI agent that edits Unreal Engine 5.7 Blueprints, C++ and levels in the open editor
Also Developers
volanea.com
Transactional email, campaigns, and automation API with AI agent support
Also AI & Machine Learning
interviewace.online
Real-time AI answer suggestions for job candidates during live video interviews
Also Developers
saascubes.com
Curated SaaS directory offering permanent do-follow backlinks for modern software products
Also Fair
submityourstartup.now
Free weekly launch directory where early-stage founders list startups and are ranked by votes
Also Fair
talhabashir.com
Free online calculators and tools for US taxes, mortgages, business and personal finance
Do you run claudeai.dev? Open the owner view → Removing the listing is free. Remove →