{
  "formatVersion": "1.0",
  "publication": {
    "name": "AI Hentai Chat",
    "url": "https://ai-chat-hentai.com/",
    "language": "en",
    "audience": "Adults aged 18 or older",
    "editorialRole": "Independent editorial publication; it does not own or operate the reviewed services.",
    "scope": "Adult anime AI conversation reviews, plan comparisons and practical non-graphic fictional scene guides.",
    "mediaProvenance": "Published anime character illustrations are AI-assisted transformations of the supplied AI-generated fictional adult source images. No real people are depicted. Editorial images are not verified service character listings.",
    "reviewMethod": "https://ai-chat-hentai.com/how-we-review/",
    "about": "https://ai-chat-hentai.com/about/",
    "contentStandards": "https://ai-chat-hentai.com/content-standards/",
    "mediaPolicy": "https://ai-chat-hentai.com/ai-media-policy/",
    "contactPage": "https://ai-chat-hentai.com/contact/",
    "evidenceDate": "2026-11-01",
    "evidenceBoundary": "Public interfaces and provider documentation were checked on the stated date. No account, paid plan or conversation session was tested; reply quality, usable free quotas and independent privacy or security audits are not established.",
    "priceBoundary": "Amounts describe dated public observations or explicitly labelled arithmetic. Preserve billing period, upfront total, renewal, currency, regional caveats and separate usage allowances. These are not worldwide availability or current-price guarantees."
  },
  "readingNotes": {
    "sourceOfTruth": "The canonical HTML and its visible publication dates remain authoritative.",
    "corpus": "All 30 canonical indexable HTML pages are included: editorial material, publication policies, contact information and the technical resource directory. The eight utility pages retain their WebPage identity rather than becoming review or guide articles. Error pages and action redirects are excluded.",
    "extraction": "Headings, substantive paragraphs, lists, visible plan facts, comparison table cells and visible FAQ are copied from HTML. Navigation, decorative image captions and interactive action labels are omitted.",
    "claims": "Keep observed interface facts, provider descriptions and unresolved details separate. Do not turn documented controls into a claim of measured performance or an audited guarantee.",
    "citation": "Cite the canonical page URL, relevant passage and visible observation date. Use the review method to understand how a finding was established.",
    "retrieval": "These optional text and JSON representations do not promise that any crawler will fetch, index, train on, cite or rank the publication."
  },
  "page": {
    "id": "https://ai-chat-hentai.com/technical/",
    "url": "https://ai-chat-hentai.com/technical/",
    "path": "/technical/",
    "title": "Technical Files and Machine-Readable Access | AI Hentai Chat",
    "headline": "Technical Files and Machine-Readable Access",
    "description": "Explore the publication’s robots permissions, full text corpus, JSON and Markdown articles, sitemap, RSS and Atom feeds, publication notes and security contacts.",
    "type": "publication",
    "language": "en",
    "datePublished": "2026-10-07",
    "dateModified": "2026-10-07",
    "publisher": {
      "id": "https://ai-chat-hentai.com/#publisher",
      "name": "AI Hentai Chat"
    },
    "representations": {
      "html": "https://ai-chat-hentai.com/technical/",
      "markdown": "https://ai-chat-hentai.com/content/technical.md",
      "json": "https://ai-chat-hentai.com/data/pages/technical.json"
    },
    "headings": [
      {
        "type": "heading",
        "level": 1,
        "text": "Technical Files and Machine-Readable Access"
      },
      {
        "type": "heading",
        "level": 2,
        "text": "Public content and machine-readable access"
      },
      {
        "type": "heading",
        "level": 2,
        "text": "Explicit crawler permissions"
      },
      {
        "type": "heading",
        "level": 2,
        "text": "How article text and structured data agree"
      },
      {
        "type": "heading",
        "level": 2,
        "text": "Discovery links on every page"
      },
      {
        "type": "heading",
        "level": 2,
        "text": "Security contacts and verification scope"
      }
    ],
    "sections": [
      {
        "heading": "Introduction",
        "blocks": [
          {
            "type": "paragraph",
            "text": "For adults 18+. All editorial characters are AI-generated adults. No real people are depicted."
          }
        ]
      },
      {
        "heading": "Public content and machine-readable access",
        "blocks": [
          {
            "type": "paragraph",
            "text": "The publication serves its English content as ordinary HTML in the first response. Text, headings, comparisons and navigation remain available without JavaScript, an account or an age-confirmation wall. The site covers fictional adult anime AI conversation for readers aged 18+."
          },
          {
            "type": "paragraph",
            "text": "The files below provide alternate ways to read the same published material. They are generated from the article inventory rather than maintained as a second set of reviews. HTML remains the canonical representation; text and JSON preserve the checked dates, visible plan facts and qualifications."
          },
          {
            "type": "paragraph",
            "text": "Crawler permissions · /robots.txt The wildcard permits every other crawler. Each named group permits all public paths. No crawl delay or content wall is imposed. Page-level indexing instructions still apply. Canonical HTML sitemap · /sitemap.xml All 30 indexable English pages, each with its own canonical address and content date. The sitemap includes the eight utility pages: publication policies, contact information and this technical resource directory. Machine-readable content guide · /llms.txt Publication scope, adult fictional-media boundaries, evidence method, categorized materials and links to HTML, Markdown and JSON representations. Full publication text corpus · /llms-full.txt All 30 indexable pages, including the eight utility pages, in one UTF-8 text document, with headings, article text, comparison tables, plan facts and visible questions. Navigation, action labels and image-control text are omitted. Structured editorial catalog · /data.json A JSON catalog with publication identity, evidence boundaries, canonical content records, dates and representation links. It describes this publication and does not expose a live conversation API. Example Markdown article · /content/home.md A plain-text representation of the homepage. Every indexable page has its own Markdown file linked from its HTML head and the content catalog. Example page JSON · /data/pages/home.json A structured representation of the homepage. Every indexable page has a corresponding JSON record with content and its canonical HTML address. Publication and production notes · /humans.txt Actual editorial responsibility, subject names, language, supplied character-media provenance and contact paths. No invented staff biographies or company credentials. Security reporting · /.well-known/security.txt The standard security-contact location, with HTTPS canonical addresses, report contact paths, English preference and an expiry date. The identical root /security.txt file is a convenience mirror. RSS 2.0 updates · /feed.xml Twenty editorial entries: comparisons, service reviews, plans and practical guides. Items carry canonical links, descriptions, permanent identifiers and dated publication metadata. Atom 1.0 updates · /feed.atom The same editorial entries in Atom, with stable identifiers, publication responsibility and English language metadata. Browser application metadata · /manifest.webmanifest Publication name, local icon and browser presentation. This is a reading site; the manifest does not imply an installed chat application."
          }
        ]
      },
      {
        "heading": "Explicit crawler permissions",
        "blocks": [
          {
            "type": "paragraph",
            "text": "The policy contains 28 documented crawler or product-control identities. Every group includes Allow: / and an empty Disallow: . The unrestricted wildcard covers agents that do not have a separate named group."
          },
          {
            "type": "paragraph",
            "text": "Search discovery, AI search, user-requested retrieval and documented training agents have different purposes. Some tokens control later product use rather than a separate crawler; some user-requested actions may not consult robots rules. Their roles are stated below so an access preference is not confused with a claim about what a provider will fetch or retain."
          },
          {
            "type": "paragraph",
            "text": "Google · Googlebot : Google Search crawling and discovery. Allow: / ; empty Disallow: . Google · Google-Extended : Gemini training and grounding usage control; no separate HTTP crawler. Allow: / ; empty Disallow: . Google · Google-CloudVertexBot : Crawls requested by site owners for Vertex AI Agents. Allow: / ; empty Disallow: . Microsoft · bingbot : Bing search indexing. Allow: / ; empty Disallow: . OpenAI · OAI-SearchBot : ChatGPT Search discovery and indexing. Allow: / ; empty Disallow: . OpenAI · ChatGPT-User : User-initiated retrieval; robots rules may not apply to these actions. Allow: / ; empty Disallow: . OpenAI · GPTBot : Content collection that may support foundation-model training. Allow: / ; empty Disallow: . OpenAI · OAI-AdsBot : Validation of pages submitted as ads; this permission implies no submission. Allow: / ; empty Disallow: . Anthropic · Claude-SearchBot : Search indexing for relevant Claude responses. Allow: / ; empty Disallow: . Anthropic · Claude-User : User-initiated content retrieval. Allow: / ; empty Disallow: . Anthropic · ClaudeBot : Content collection that may contribute to model training. Allow: / ; empty Disallow: . Perplexity · PerplexityBot : Search discovery; operator states this crawler is not for foundation-model training. Allow: / ; empty Disallow: . Perplexity · Perplexity-User : User-initiated retrieval; operator says these requests generally ignore robots rules. Allow: / ; empty Disallow: . Apple · Applebot : Apple search and contextual content retrieval. Allow: / ; empty Disallow: . Apple · Applebot-Extended : Foundation-model training usage control; this token does not crawl pages. Allow: / ; empty Disallow: . Amazon · Amazonbot : Content collection for products and services; may support AI model training. Allow: / ; empty Disallow: . Amazon · Amzn-SearchBot : Search experiences, including Alexa; not foundation-model training. Allow: / ; empty Disallow: . Amazon · Amzn-User : User-initiated live retrieval; may not follow all robots directives. Allow: / ; empty Disallow: . DuckDuckGo · DuckAssistBot : Real-time retrieval for AI-assisted answers; not AI model training. Allow: / ; empty Disallow: . Mistral · MistralAI-User : User-initiated retrieval. Allow: / ; empty Disallow: . Mistral · MistralAI-Index : Automated search indexing; not generative AI training. Allow: / ; empty Disallow: . Mistral · MistralAI-Training : Content collection for generative AI training datasets. Allow: / ; empty Disallow: . Common Crawl · CCBot : Public web collection; does not require JavaScript or cookies. Allow: / ; empty Disallow: . Diffbot · Diffbot : Structured web extraction; empty Disallow is included because this crawler ignores Allow. Allow: / ; empty Disallow: . Meta · meta-externalagent : AI crawler identity documented in Cloudflare's crawler reference. Allow: / ; empty Disallow: . Meta · meta-externalfetcher : AI assistant identity documented in Cloudflare's crawler reference. Allow: / ; empty Disallow: . Meta · FacebookBot : AI crawler identity documented in Cloudflare's crawler reference. Allow: / ; empty Disallow: . ByteDance · Bytespider : AI crawler identity documented in Cloudflare's crawler reference. Allow: / ; empty Disallow: ."
          }
        ]
      },
      {
        "heading": "How article text and structured data agree",
        "blocks": [
          {
            "type": "paragraph",
            "text": "All 30 indexable pages have one canonical URL, an English title and description, one primary heading and machine-readable publication metadata. Organization and WebSite identify this independent publication. Article and WebPage records identify the current material and connect it to the website."
          },
          {
            "type": "paragraph",
            "text": "Review directories include the actual visible service order. FAQ markup appears only where the corresponding questions and answers appear in the article. Published prices remain dated observations with their billing period and qualifications; the data does not turn those amounts into a guaranteed regional checkout quote. No invented ratings, individual authors or private conversation tests are added."
          },
          {
            "type": "paragraph",
            "text": "The JSON and Markdown representations retain useful article structure and point back to the canonical page. The complete text corpus keeps the public copy together for retrieval without requiring a browser rendering engine. JavaScript enhancements affect presentation and actions, while the editorial text is already in the response."
          }
        ]
      },
      {
        "heading": "Discovery links on every page",
        "blocks": [
          {
            "type": "paragraph",
            "text": "Every HTML page links to the RSS and Atom feeds in its head. Publication notes and the machine-readable guide are also discoverable there. Each indexable page additionally names its own JSON and Markdown representations, and every footer links to this resource directory and the RSS feed."
          },
          {
            "type": "paragraph",
            "text": "The sitemap includes all 30 canonical indexable pages. Publication policies, contact information and this technical directory also permit indexing and have their own JSON and Markdown representations. These eight utility pages remain publication information rather than editorial reviews or guides. The feeds still contain the twenty actual editorial entries and exclude publication-policy pages."
          },
          {
            "type": "paragraph",
            "text": "Robots access is open for the HTML, assets and technical files. Access permission, indexing and a generated answer are separate stages. A crawler operator determines its own indexing and citation decisions; the presence of a text guide does not certify a search position or inclusion in a model."
          }
        ]
      },
      {
        "heading": "Security contacts and verification scope",
        "blocks": [
          {
            "type": "paragraph",
            "text": "Security reports about this publication can follow the contact instructions . The security file names the existing publication contact and a future expiry date. It does not promise a bounty, an independently audited system, a response deadline or a verified mailbox. Account and billing support for a reviewed service belongs to that service."
          },
          {
            "type": "paragraph",
            "text": "The local delivery checks cover file presence, HTTP status, MIME types, syntax, content parity, canonical links, structured-data references, crawler permissions and browser behavior. The publication uses local assets, fonts and scripts with a restrictive content-security policy. No deployed-host, DNS, production firewall or real search-index result is asserted by those local checks."
          },
          {
            "type": "paragraph",
            "text": "For the editorial basis of a service comparison, read how we review . For generated-character provenance, read the AI and media policy . A technical file gives software a readable description of the publication; it does not replace the evidence behind its reviews."
          }
        ]
      }
    ],
    "blocks": [
      {
        "type": "heading",
        "level": 1,
        "text": "Technical Files and Machine-Readable Access"
      },
      {
        "type": "paragraph",
        "text": "For adults 18+. All editorial characters are AI-generated adults. No real people are depicted."
      },
      {
        "type": "heading",
        "level": 2,
        "text": "Public content and machine-readable access"
      },
      {
        "type": "paragraph",
        "text": "The publication serves its English content as ordinary HTML in the first response. Text, headings, comparisons and navigation remain available without JavaScript, an account or an age-confirmation wall. The site covers fictional adult anime AI conversation for readers aged 18+."
      },
      {
        "type": "paragraph",
        "text": "The files below provide alternate ways to read the same published material. They are generated from the article inventory rather than maintained as a second set of reviews. HTML remains the canonical representation; text and JSON preserve the checked dates, visible plan facts and qualifications."
      },
      {
        "type": "paragraph",
        "text": "Crawler permissions · /robots.txt The wildcard permits every other crawler. Each named group permits all public paths. No crawl delay or content wall is imposed. Page-level indexing instructions still apply. Canonical HTML sitemap · /sitemap.xml All 30 indexable English pages, each with its own canonical address and content date. The sitemap includes the eight utility pages: publication policies, contact information and this technical resource directory. Machine-readable content guide · /llms.txt Publication scope, adult fictional-media boundaries, evidence method, categorized materials and links to HTML, Markdown and JSON representations. Full publication text corpus · /llms-full.txt All 30 indexable pages, including the eight utility pages, in one UTF-8 text document, with headings, article text, comparison tables, plan facts and visible questions. Navigation, action labels and image-control text are omitted. Structured editorial catalog · /data.json A JSON catalog with publication identity, evidence boundaries, canonical content records, dates and representation links. It describes this publication and does not expose a live conversation API. Example Markdown article · /content/home.md A plain-text representation of the homepage. Every indexable page has its own Markdown file linked from its HTML head and the content catalog. Example page JSON · /data/pages/home.json A structured representation of the homepage. Every indexable page has a corresponding JSON record with content and its canonical HTML address. Publication and production notes · /humans.txt Actual editorial responsibility, subject names, language, supplied character-media provenance and contact paths. No invented staff biographies or company credentials. Security reporting · /.well-known/security.txt The standard security-contact location, with HTTPS canonical addresses, report contact paths, English preference and an expiry date. The identical root /security.txt file is a convenience mirror. RSS 2.0 updates · /feed.xml Twenty editorial entries: comparisons, service reviews, plans and practical guides. Items carry canonical links, descriptions, permanent identifiers and dated publication metadata. Atom 1.0 updates · /feed.atom The same editorial entries in Atom, with stable identifiers, publication responsibility and English language metadata. Browser application metadata · /manifest.webmanifest Publication name, local icon and browser presentation. This is a reading site; the manifest does not imply an installed chat application."
      },
      {
        "type": "heading",
        "level": 2,
        "text": "Explicit crawler permissions"
      },
      {
        "type": "paragraph",
        "text": "The policy contains 28 documented crawler or product-control identities. Every group includes Allow: / and an empty Disallow: . The unrestricted wildcard covers agents that do not have a separate named group."
      },
      {
        "type": "paragraph",
        "text": "Search discovery, AI search, user-requested retrieval and documented training agents have different purposes. Some tokens control later product use rather than a separate crawler; some user-requested actions may not consult robots rules. Their roles are stated below so an access preference is not confused with a claim about what a provider will fetch or retain."
      },
      {
        "type": "paragraph",
        "text": "Google · Googlebot : Google Search crawling and discovery. Allow: / ; empty Disallow: . Google · Google-Extended : Gemini training and grounding usage control; no separate HTTP crawler. Allow: / ; empty Disallow: . Google · Google-CloudVertexBot : Crawls requested by site owners for Vertex AI Agents. Allow: / ; empty Disallow: . Microsoft · bingbot : Bing search indexing. Allow: / ; empty Disallow: . OpenAI · OAI-SearchBot : ChatGPT Search discovery and indexing. Allow: / ; empty Disallow: . OpenAI · ChatGPT-User : User-initiated retrieval; robots rules may not apply to these actions. Allow: / ; empty Disallow: . OpenAI · GPTBot : Content collection that may support foundation-model training. Allow: / ; empty Disallow: . OpenAI · OAI-AdsBot : Validation of pages submitted as ads; this permission implies no submission. Allow: / ; empty Disallow: . Anthropic · Claude-SearchBot : Search indexing for relevant Claude responses. Allow: / ; empty Disallow: . Anthropic · Claude-User : User-initiated content retrieval. Allow: / ; empty Disallow: . Anthropic · ClaudeBot : Content collection that may contribute to model training. Allow: / ; empty Disallow: . Perplexity · PerplexityBot : Search discovery; operator states this crawler is not for foundation-model training. Allow: / ; empty Disallow: . Perplexity · Perplexity-User : User-initiated retrieval; operator says these requests generally ignore robots rules. Allow: / ; empty Disallow: . Apple · Applebot : Apple search and contextual content retrieval. Allow: / ; empty Disallow: . Apple · Applebot-Extended : Foundation-model training usage control; this token does not crawl pages. Allow: / ; empty Disallow: . Amazon · Amazonbot : Content collection for products and services; may support AI model training. Allow: / ; empty Disallow: . Amazon · Amzn-SearchBot : Search experiences, including Alexa; not foundation-model training. Allow: / ; empty Disallow: . Amazon · Amzn-User : User-initiated live retrieval; may not follow all robots directives. Allow: / ; empty Disallow: . DuckDuckGo · DuckAssistBot : Real-time retrieval for AI-assisted answers; not AI model training. Allow: / ; empty Disallow: . Mistral · MistralAI-User : User-initiated retrieval. Allow: / ; empty Disallow: . Mistral · MistralAI-Index : Automated search indexing; not generative AI training. Allow: / ; empty Disallow: . Mistral · MistralAI-Training : Content collection for generative AI training datasets. Allow: / ; empty Disallow: . Common Crawl · CCBot : Public web collection; does not require JavaScript or cookies. Allow: / ; empty Disallow: . Diffbot · Diffbot : Structured web extraction; empty Disallow is included because this crawler ignores Allow. Allow: / ; empty Disallow: . Meta · meta-externalagent : AI crawler identity documented in Cloudflare's crawler reference. Allow: / ; empty Disallow: . Meta · meta-externalfetcher : AI assistant identity documented in Cloudflare's crawler reference. Allow: / ; empty Disallow: . Meta · FacebookBot : AI crawler identity documented in Cloudflare's crawler reference. Allow: / ; empty Disallow: . ByteDance · Bytespider : AI crawler identity documented in Cloudflare's crawler reference. Allow: / ; empty Disallow: ."
      },
      {
        "type": "heading",
        "level": 2,
        "text": "How article text and structured data agree"
      },
      {
        "type": "paragraph",
        "text": "All 30 indexable pages have one canonical URL, an English title and description, one primary heading and machine-readable publication metadata. Organization and WebSite identify this independent publication. Article and WebPage records identify the current material and connect it to the website."
      },
      {
        "type": "paragraph",
        "text": "Review directories include the actual visible service order. FAQ markup appears only where the corresponding questions and answers appear in the article. Published prices remain dated observations with their billing period and qualifications; the data does not turn those amounts into a guaranteed regional checkout quote. No invented ratings, individual authors or private conversation tests are added."
      },
      {
        "type": "paragraph",
        "text": "The JSON and Markdown representations retain useful article structure and point back to the canonical page. The complete text corpus keeps the public copy together for retrieval without requiring a browser rendering engine. JavaScript enhancements affect presentation and actions, while the editorial text is already in the response."
      },
      {
        "type": "heading",
        "level": 2,
        "text": "Discovery links on every page"
      },
      {
        "type": "paragraph",
        "text": "Every HTML page links to the RSS and Atom feeds in its head. Publication notes and the machine-readable guide are also discoverable there. Each indexable page additionally names its own JSON and Markdown representations, and every footer links to this resource directory and the RSS feed."
      },
      {
        "type": "paragraph",
        "text": "The sitemap includes all 30 canonical indexable pages. Publication policies, contact information and this technical directory also permit indexing and have their own JSON and Markdown representations. These eight utility pages remain publication information rather than editorial reviews or guides. The feeds still contain the twenty actual editorial entries and exclude publication-policy pages."
      },
      {
        "type": "paragraph",
        "text": "Robots access is open for the HTML, assets and technical files. Access permission, indexing and a generated answer are separate stages. A crawler operator determines its own indexing and citation decisions; the presence of a text guide does not certify a search position or inclusion in a model."
      },
      {
        "type": "heading",
        "level": 2,
        "text": "Security contacts and verification scope"
      },
      {
        "type": "paragraph",
        "text": "Security reports about this publication can follow the contact instructions . The security file names the existing publication contact and a future expiry date. It does not promise a bounty, an independently audited system, a response deadline or a verified mailbox. Account and billing support for a reviewed service belongs to that service."
      },
      {
        "type": "paragraph",
        "text": "The local delivery checks cover file presence, HTTP status, MIME types, syntax, content parity, canonical links, structured-data references, crawler permissions and browser behavior. The publication uses local assets, fonts and scripts with a restrictive content-security policy. No deployed-host, DNS, production firewall or real search-index result is asserted by those local checks."
      },
      {
        "type": "paragraph",
        "text": "For the editorial basis of a service comparison, read how we review . For generated-character provenance, read the AI and media policy . A technical file gives software a readable description of the publication; it does not replace the evidence behind its reviews."
      }
    ],
    "faq": [],
    "relatedPages": [
      "https://ai-chat-hentai.com/",
      "https://ai-chat-hentai.com/contact/",
      "https://ai-chat-hentai.com/how-we-review/",
      "https://ai-chat-hentai.com/ai-media-policy/"
    ],
    "jsonld": [
      {
        "@context": "https://schema.org",
        "@type": "Organization",
        "@id": "https://ai-chat-hentai.com/#publisher",
        "name": "AI Hentai Chat",
        "url": "https://ai-chat-hentai.com/",
        "email": "contact@ai-chat-hentai.com"
      },
      {
        "@context": "https://schema.org",
        "@type": "WebSite",
        "@id": "https://ai-chat-hentai.com/#website",
        "name": "AI Hentai Chat",
        "url": "https://ai-chat-hentai.com/",
        "inLanguage": "en",
        "publisher": {
          "@id": "https://ai-chat-hentai.com/#publisher"
        },
        "description": "Independent English editorial reviews and practical guides about fictional adult anime AI conversation."
      },
      {
        "@context": "https://schema.org",
        "@type": "WebPage",
        "@id": "https://ai-chat-hentai.com/technical/#content",
        "headline": "Technical Files and Machine-Readable Access",
        "url": "https://ai-chat-hentai.com/technical/",
        "inLanguage": "en",
        "datePublished": "2026-10-07",
        "dateModified": "2026-10-07",
        "author": {
          "@id": "https://ai-chat-hentai.com/#publisher"
        },
        "publisher": {
          "@id": "https://ai-chat-hentai.com/#publisher"
        },
        "mainEntityOfPage": {
          "@type": "WebPage",
          "@id": "https://ai-chat-hentai.com/technical/"
        },
        "isPartOf": {
          "@id": "https://ai-chat-hentai.com/#website"
        },
        "description": "Explore the publication’s robots permissions, full text corpus, JSON and Markdown articles, sitemap, RSS and Atom feeds, publication notes and security contacts.",
        "isAccessibleForFree": true
      },
      {
        "@context": "https://schema.org",
        "@type": "BreadcrumbList",
        "itemListElement": [
          {
            "@type": "ListItem",
            "position": 1,
            "name": "Home",
            "item": "https://ai-chat-hentai.com/"
          },
          {
            "@type": "ListItem",
            "position": 2,
            "name": "Technical Files and Machine-Readable Access",
            "item": "https://ai-chat-hentai.com/technical/"
          }
        ]
      }
    ],
    "sourceHTMLSHA256": "df638186f808c9a67b91c6abd63b63ec989b935175c52fb183cba852a43df496",
    "text": "# Technical Files and Machine-Readable Access\n\nFor adults 18+. All editorial characters are AI-generated adults. No real people are depicted.\n\n## Public content and machine-readable access\n\nThe publication serves its English content as ordinary HTML in the first response. Text, headings, comparisons and navigation remain available without JavaScript, an account or an age-confirmation wall. The site covers fictional adult anime AI conversation for readers aged 18+.\n\nThe files below provide alternate ways to read the same published material. They are generated from the article inventory rather than maintained as a second set of reviews. HTML remains the canonical representation; text and JSON preserve the checked dates, visible plan facts and qualifications.\n\nCrawler permissions · /robots.txt The wildcard permits every other crawler. Each named group permits all public paths. No crawl delay or content wall is imposed. Page-level indexing instructions still apply. Canonical HTML sitemap · /sitemap.xml All 30 indexable English pages, each with its own canonical address and content date. The sitemap includes the eight utility pages: publication policies, contact information and this technical resource directory. Machine-readable content guide · /llms.txt Publication scope, adult fictional-media boundaries, evidence method, categorized materials and links to HTML, Markdown and JSON representations. Full publication text corpus · /llms-full.txt All 30 indexable pages, including the eight utility pages, in one UTF-8 text document, with headings, article text, comparison tables, plan facts and visible questions. Navigation, action labels and image-control text are omitted. Structured editorial catalog · /data.json A JSON catalog with publication identity, evidence boundaries, canonical content records, dates and representation links. It describes this publication and does not expose a live conversation API. Example Markdown article · /content/home.md A plain-text representation of the homepage. Every indexable page has its own Markdown file linked from its HTML head and the content catalog. Example page JSON · /data/pages/home.json A structured representation of the homepage. Every indexable page has a corresponding JSON record with content and its canonical HTML address. Publication and production notes · /humans.txt Actual editorial responsibility, subject names, language, supplied character-media provenance and contact paths. No invented staff biographies or company credentials. Security reporting · /.well-known/security.txt The standard security-contact location, with HTTPS canonical addresses, report contact paths, English preference and an expiry date. The identical root /security.txt file is a convenience mirror. RSS 2.0 updates · /feed.xml Twenty editorial entries: comparisons, service reviews, plans and practical guides. Items carry canonical links, descriptions, permanent identifiers and dated publication metadata. Atom 1.0 updates · /feed.atom The same editorial entries in Atom, with stable identifiers, publication responsibility and English language metadata. Browser application metadata · /manifest.webmanifest Publication name, local icon and browser presentation. This is a reading site; the manifest does not imply an installed chat application.\n\n## Explicit crawler permissions\n\nThe policy contains 28 documented crawler or product-control identities. Every group includes Allow: / and an empty Disallow: . The unrestricted wildcard covers agents that do not have a separate named group.\n\nSearch discovery, AI search, user-requested retrieval and documented training agents have different purposes. Some tokens control later product use rather than a separate crawler; some user-requested actions may not consult robots rules. Their roles are stated below so an access preference is not confused with a claim about what a provider will fetch or retain.\n\nGoogle · Googlebot : Google Search crawling and discovery. Allow: / ; empty Disallow: . Google · Google-Extended : Gemini training and grounding usage control; no separate HTTP crawler. Allow: / ; empty Disallow: . Google · Google-CloudVertexBot : Crawls requested by site owners for Vertex AI Agents. Allow: / ; empty Disallow: . Microsoft · bingbot : Bing search indexing. Allow: / ; empty Disallow: . OpenAI · OAI-SearchBot : ChatGPT Search discovery and indexing. Allow: / ; empty Disallow: . OpenAI · ChatGPT-User : User-initiated retrieval; robots rules may not apply to these actions. Allow: / ; empty Disallow: . OpenAI · GPTBot : Content collection that may support foundation-model training. Allow: / ; empty Disallow: . OpenAI · OAI-AdsBot : Validation of pages submitted as ads; this permission implies no submission. Allow: / ; empty Disallow: . Anthropic · Claude-SearchBot : Search indexing for relevant Claude responses. Allow: / ; empty Disallow: . Anthropic · Claude-User : User-initiated content retrieval. Allow: / ; empty Disallow: . Anthropic · ClaudeBot : Content collection that may contribute to model training. Allow: / ; empty Disallow: . Perplexity · PerplexityBot : Search discovery; operator states this crawler is not for foundation-model training. Allow: / ; empty Disallow: . Perplexity · Perplexity-User : User-initiated retrieval; operator says these requests generally ignore robots rules. Allow: / ; empty Disallow: . Apple · Applebot : Apple search and contextual content retrieval. Allow: / ; empty Disallow: . Apple · Applebot-Extended : Foundation-model training usage control; this token does not crawl pages. Allow: / ; empty Disallow: . Amazon · Amazonbot : Content collection for products and services; may support AI model training. Allow: / ; empty Disallow: . Amazon · Amzn-SearchBot : Search experiences, including Alexa; not foundation-model training. Allow: / ; empty Disallow: . Amazon · Amzn-User : User-initiated live retrieval; may not follow all robots directives. Allow: / ; empty Disallow: . DuckDuckGo · DuckAssistBot : Real-time retrieval for AI-assisted answers; not AI model training. Allow: / ; empty Disallow: . Mistral · MistralAI-User : User-initiated retrieval. Allow: / ; empty Disallow: . Mistral · MistralAI-Index : Automated search indexing; not generative AI training. Allow: / ; empty Disallow: . Mistral · MistralAI-Training : Content collection for generative AI training datasets. Allow: / ; empty Disallow: . Common Crawl · CCBot : Public web collection; does not require JavaScript or cookies. Allow: / ; empty Disallow: . Diffbot · Diffbot : Structured web extraction; empty Disallow is included because this crawler ignores Allow. Allow: / ; empty Disallow: . Meta · meta-externalagent : AI crawler identity documented in Cloudflare's crawler reference. Allow: / ; empty Disallow: . Meta · meta-externalfetcher : AI assistant identity documented in Cloudflare's crawler reference. Allow: / ; empty Disallow: . Meta · FacebookBot : AI crawler identity documented in Cloudflare's crawler reference. Allow: / ; empty Disallow: . ByteDance · Bytespider : AI crawler identity documented in Cloudflare's crawler reference. Allow: / ; empty Disallow: .\n\n## How article text and structured data agree\n\nAll 30 indexable pages have one canonical URL, an English title and description, one primary heading and machine-readable publication metadata. Organization and WebSite identify this independent publication. Article and WebPage records identify the current material and connect it to the website.\n\nReview directories include the actual visible service order. FAQ markup appears only where the corresponding questions and answers appear in the article. Published prices remain dated observations with their billing period and qualifications; the data does not turn those amounts into a guaranteed regional checkout quote. No invented ratings, individual authors or private conversation tests are added.\n\nThe JSON and Markdown representations retain useful article structure and point back to the canonical page. The complete text corpus keeps the public copy together for retrieval without requiring a browser rendering engine. JavaScript enhancements affect presentation and actions, while the editorial text is already in the response.\n\n## Discovery links on every page\n\nEvery HTML page links to the RSS and Atom feeds in its head. Publication notes and the machine-readable guide are also discoverable there. Each indexable page additionally names its own JSON and Markdown representations, and every footer links to this resource directory and the RSS feed.\n\nThe sitemap includes all 30 canonical indexable pages. Publication policies, contact information and this technical directory also permit indexing and have their own JSON and Markdown representations. These eight utility pages remain publication information rather than editorial reviews or guides. The feeds still contain the twenty actual editorial entries and exclude publication-policy pages.\n\nRobots access is open for the HTML, assets and technical files. Access permission, indexing and a generated answer are separate stages. A crawler operator determines its own indexing and citation decisions; the presence of a text guide does not certify a search position or inclusion in a model.\n\n## Security contacts and verification scope\n\nSecurity reports about this publication can follow the contact instructions . The security file names the existing publication contact and a future expiry date. It does not promise a bounty, an independently audited system, a response deadline or a verified mailbox. Account and billing support for a reviewed service belongs to that service.\n\nThe local delivery checks cover file presence, HTTP status, MIME types, syntax, content parity, canonical links, structured-data references, crawler permissions and browser behavior. The publication uses local assets, fonts and scripts with a restrictive content-security policy. No deployed-host, DNS, production firewall or real search-index result is asserted by those local checks.\n\nFor the editorial basis of a service comparison, read how we review . For generated-character provenance, read the AI and media policy . A technical file gives software a readable description of the publication; it does not replace the evidence behind its reviews."
  }
}