Story metadata API · early access

Know a story's shape before you read a single chapter.

Fabledex keeps the structure a series does not ship with: its arcs, its volumes and seasons, and its chapter titles. Readers contribute and correct it, and one API serves it to any app.

stories
361
story arcs
3,818
chapters and episodes
58,596

The shape of a story

Live from the data: one block per arc, as wide as its chapters.

The data every story app rebuilds from scratch

Catalogues know a book's title, author and page count. None of them know that chapters 1 to 5 are the beginning arc, that the training arc starts at chapter 6, or that episode 13 is a tournament episode. Every reading tracker, recap tool, recommendation engine and fan project that needs that works it out alone, and keeps it to itself.

One reliable source, maintained by its readers

Fabledex collects that structure once, as community-contributed metadata with revision history and contributor counts, and makes it available to every developer through the same endpoints. Built by a developer for personal own projects first, so the API is shaped around actually consuming it.

What Fabledex keeps

Story arcs

Named spans over chapters or episodes: beginning, training, tournament, war, aftermath. Nested arcs for long series.

Episode types

What each chapter or episode is: setup, training, battle, filler, flashback, recap. Tagged per unit, queryable as a whole.

Community metadata

Anything readers find worth recording: characters introduced per chapter, point-of-view shifts, timelines, content notes.

Provenance

Every record carries where it came from, who has confirmed or disputed it, and a confidence score, with the full change history one call away, so your app can decide what to trust.

How it works

  1. 1

    Readers contribute

    A reader marks where an arc begins and ends, or tags an episode's type. Others confirm or correct it. Nothing is final; everything is versioned.

  2. 2

    Fabledex consolidates

    Contributions are merged into one canonical record per story with agreement counts and confidence, keyed by stable story identifiers.

  3. 3

    Your service pulls it

    One request returns the whole chapter-to-chapter structure. Show a reader which arc they are in, skip filler, or build on top of it.

What a response looks like

A real response, abridged. The read API is live for the first seeded story, in both its editions: the manga counted in chapters and the anime counted in episodes. It is free: create an account, make a key on your API keys page, and send it as Authorization: Bearer fdx_…. Address a story by its Fabledex slug or by an id or title slug from MyAnimeList or AniList, and the edition that id belongs to is the one you get: mal:100035, anilist:98263, mal:Tongari_Boushi_no_Atelier.

GET https://fabledex.com/api/v1/stories/witch-hat-atelier/arcs  -H "Authorization: Bearer fdx_…"
{
  "story": "witch-hat-atelier",
  "edition": "manga",
  "unit": "chapter",
  "arcs": [
    { "position": 1, "title": "Introduction Arc",          "from": 1,  "to": 2,  "ongoing": false,
      "description": "Coco is an unknowing girl with a huge admiration for magic, ...",
      "source": "https://witch-hat-atelier.fandom.com/wiki/Story_Arcs",
      "id": "01a11211-1337-7af9-...",
      "provenance": { "confidence": 0.6, "origin": "user", "contributors": 1,
                      "confirmations": 0, "disputes": 0 } },
    { "position": 2, "title": "First Pentagram Test Arc",  "from": 3,  "to": 4,  "ongoing": false, ... },
    { "position": 3, "title": "Draconic Labyrinth Arc",    "from": 5,  "to": 7,  "ongoing": false, ... },
    ...
    { "position": 8, "title": "Second Pentagram Test Arc", "from": 18, "to": 29, "ongoing": false, ... },
    ...
    { "position": 14, "title": "Dragonpass Isles Arc",     "from": 94, "to": 99, "ongoing": true,  ... }
  ]
}

GET https://fabledex.com/api/v1/stories/mal:51553/arcs        (the anime, counted in episodes)
{ "story": "witch-hat-atelier", "edition": "anime-season-1", "unit": "episode", "arcs": [ ... ] }

GET https://fabledex.com/api/v1/stories/witch-hat-atelier?lang=ko   (also ja, zh-Hans, es; or an Accept-Language header)
{ "story": { "title": "...", "language": "ko", ... }, ... }   (text with no translation yet stays English, "language": "en")

Chapters 1 and 2 introduce Coco, 18 to 29 are the Second Pentagram Test, and the current arc is still running. Your app knew that before the reader did. Ask for one chapter with /api/v1/stories/witch-hat-atelier/arcs/at/23.

Built for other developers

Fabledex exists because its author needed this data for personal projects and could not find a dependable source. The goal is a service other developers can rely on the same way: stable identifiers, plain JSON, versioned responses, and an open contribution model so the data keeps improving without anyone having to maintain a private copy.

  • Plain JSON over HTTPS, free key per account
  • Stable story and chapter identifiers
  • Confidence and contributor counts on every field
  • Contribute back from your own app

Early access

The service is being built in the open. Create a free account to contribute data and to make a free API key; every key's usage is counted so you can see how much your app relies on it.