For developers & AI agents

YOKAI.JP — Machine-readable resources

YOKAI.JP does not offer a public REST or GraphQL API. We do, however, publish the resources below so that the site's structure, yokai catalog, and page metadata can be consumed programmatically — by search engines, AI agents, and research tools.

llms.txt — site overview for LLM agents

Markdown documents following the llms.txt convention. Each file describes the site structure, key page URLs, the full yokai-catalog slug list, and cross-language links. Provided per language.

  • /llms.txtJapanese — 全サイト構造、主要ページ、妖怪一覧、多言語リンクを Markdown で。
  • /llms-en.txtEnglish version of the site map for LLM agents.
  • /llms-zh-CN.txt简体中文 ─ 站点结构 / 主要页面 / 妖怪列表 (Markdown)。
  • /llms-ko.txt한국어 ─ 사이트 구조 안내 (LLM 에이전트용).
  • /llms-fr.txtFrançais ─ structure du site pour agents LLM.
  • /llms-es.txtEspañol ─ estructura del sitio para agentes LLM.

Sitemaps — XML entries

Standard sitemaps.org schema, split by language and by content type. Crawlers should start at /sitemap-index.xml — it lists every sub-sitemap.

JSON-LD structured data

schema.org-compliant JSON-LD is embedded in every page via <script type="application/ld+json">. AI agents and search engines can read page identity and key attributes programmatically.

  • WebSiteHome page (/) — site identity
  • OrganizationHome page (/) — Glory Lab identifier
  • WebApplicationHome page (/) — feature list + price (free) + supported languages
  • QuizHome page + diagnosis pages
  • Article/blog/{slug} — author / datePublished / image
  • TechArticle/developers (this page)
  • BreadcrumbListDeep pages (/yokai/{slug}, /yokai/{slug}/cards, etc.)

Other metadata surfaces

  • OpenGraph + Twitter Card meta — Provided on every page (og:title, og:description, og:image, og:url, twitter:card).
  • hreflang alternate links Multi-language pages emit <link rel="alternate" hreflang="...">. Six languages (ja / en / zh-CN / ko / fr / es).
  • canonical linkEvery page emits <link rel="canonical">.

About a public API

YOKAI.JP does not currently expose a third-party-facing REST or GraphQL API. The internal /api/* endpoints (chat, yokai voting, shrine, etc.) are session-gated and CORS-restricted because they exist to power the web app itself.

If you need public content (yokai catalog data, blog posts, …), the recommended path is to crawl HTML starting from the sitemap and parse the embedded JSON-LD and OpenGraph meta on each page. The full list of yokai slugs is enumerated in /llms.txt.

If you'd like a public API or want to discuss a business use case, please reach out via Contact.

This page is intended as guidance for AI agents, bots, crawlers, and research tools. Questions or suggestions are welcome via the Contact page.

← Back to home