Skip to content
Injoys

Data

Machine-friendly format access paths for AI systems, search engines, developers and researchers.

Injoys is a content data platform. Every published article is a data package, and you can fetch it in the format you need via the paths below.

Data provision

Access paths by format

Format Path Purpose
HTML /{lang}/articles/{slug} Human-readable article page
TXT /data/{content-id}/{lang}/content.txt Plain text for AI training/collection
Markdown /data/{content-id}/{lang}/content.md LLM-friendly Markdown with front matter
JSON /data/{content-id}/{lang}/content.json Structured content data (body, summary, FAQ, images, tags)
JSON-LD /data/{content-id}/{lang}/schema.jsonld schema.org structured data
Images /data/{content-id}/images.json Image metadata (alt, caption, license, generation source)
RSS /feed/rss, /feed/rss-{lang} Update feed (all / per language)
Atom /feed/atom Atom alternative feed
Sitemap /sitemap.xml URL discovery with hreflang
llms.txt /llms.txt, /llms-full.txt AI guidance file and full content index

Languages

Articles are provided in Korean and English by default, plus Japanese and Spanish. Use ko, en, ja or es for {lang}; only languages with an actual translation appear in the sitemap hreflang. Additionally, Indonesian (id), Portuguese (pt), Traditional Chinese (zh-hant) and German (de) are available as machine-translated data files only, labeled translation_status: machine, and are excluded from HTML pages and the sitemap until reviewed.

Language Value (lang) Tier Web pages Data files Audio (TTS) Embeddings
한국어 ko Tier 1
English en Tier 1
日本語 ja Tier 1
Español es Tier 1
Indonesian id Tier 2 - - -
Portuguese pt Tier 2 - - -
Chinese (Traditional) zh-hant Tier 2 - - -
Deutsch de Tier 2 - - -
  • Tier 1 - Editor-reviewed languages. Everything is provided: human-readable web pages, search exposure (sitemap and hreflang), AI audio (TTS) and embeddings.
  • Tier 2 - Machine-translated, data-only languages. Served through data files and the API only - no web pages, no search exposure, no audio (TTS) and no embeddings. Every file carries a translation_status: machine label to mark that it has not been reviewed.

Data usage

No API key or authentication is required to use the public content. Simply fetch the files you need from the paths above.

Crawler policy

Search engines and AI crawlers (GPTBot, OAI-SearchBot, ClaudeBot, Google-Extended, PerplexityBot, CCBot and others) are allowed in robots.txt. People and machines get the same content - no cloaking.

Structured API & embeddings

For real-time lookups, filters, and search, use the content API. Semantic search and raw embedding vectors are also available via the API (when the embedding API is on). View the content API

Datasets (training and RAG, paid API)

For cases that need many records at once - model training, fine-tuning, RAG indexing - the paid API serves the same content normalized into training-ready schemas. It supports pagination (page, per_page), filters (category, tag) and incremental sync (updated_since), and can return JSONL.

  • corpus - Corpus with body, summary, key points, tags, license and translation status
  • qa - Instruction data expanding FAQs into user/assistant message pairs
  • parallel - Parallel corpus aligning one article across languages in a single record
  • embeddings - Embedding vectors bundled per article (pro only)

The dataset API does not replace free data access. The per-article paths in the table above remain free and unauthenticated exactly as they are today. About the dataset API

Every data file provides the same content as its human-readable HTML page (content consistency principle).

Reuse / AI training policy: License