Security verification gate
The site uses a security verification layer before serving content. That means some visitors may need to pass a browser challenge before reaching the underlying product pages.
AI Dungeon is hosted at aidungeon.io, but access is currently behind a security verification screen. Challenge help covers troubleshooting loops, extensions, JavaScript, browsers, VPNs, and proxies.
AI Dungeon appears to be an online product hosted at `aidungeon.io`, but the collected pages are currently gated behind a security verification screen rather than showing the product itself. Because of that, the available evidence does not confirm the core experience, feature set, or target workflow from the live site pages provided here.
The only directly accessible source text comes from Cloudflare challenge help content, which explains how verification loops can happen and how to troubleshoot them. Based on the evidence in hand, the product page cannot yet be described beyond its domain, the presence of a security check, and the fact that users may need to complete that check before reaching the site.
The site uses a security verification layer before serving content. That means some visitors may need to pass a browser challenge before reaching the underlying product pages.
The challenge help page explains that verification can loop if browser extensions, JavaScript settings, unsupported browsers, VPNs, proxies, or unstable networks interfere.
Cloudflare Turnstile may request a Private Access Token during challenge handling. The help text notes that a 401 on that request can be expected and does not by itself indicate a blocked visitor.
The accessible source does not reveal the product interface, gameplay flow, or creative tools, so no deeper feature claims can be supported from the collected pages.
If a visitor lands on the site and is blocked by a challenge page, the available help text provides a checklist for browser extensions, JavaScript, browser compatibility, and network checks.
If a challenge keeps repeating, the help page identifies likely causes such as unstable networks, unsupported browsers, or browser settings that block challenge scripts.
If a user sees a 401 on a private access token request in developer tools or a HAR file, the help page explains that this can be expected during challenge handling and is not automatically an error.
If someone is evaluating the site from the provided sources, the main useful takeaway is that the product content itself is not currently visible, so deeper product assessment requires a successful pass through the security gate.
The source pages do not expose a normal product or help page because the site is showing a security verification screen. Based on the available evidence, there is not enough information to confirm setup steps, account requirements, or feature-specific help.
The accessible source content does not include plan names, prices, or limits. The pricing URL was also blocked by the same verification page, so no pricing details can be confirmed from the provided evidence.
The available pages do not show supported integrations or connected tools. There is not enough evidence to list third-party services or platform integrations.
The only confirmed behavior in the source is that the site uses a Cloudflare security verification flow and may show challenge loops if browser settings, extensions, JavaScript, or network conditions interfere. That information is about access to the site, not the product itself.