> For the complete documentation index, see [llms.txt](https://docs.tatakai.me/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tatakai.me/extensions/extension-capabilities/manga-capability.md). # Manga capability Manga chapters and pages are provided through extension bundles. The primary transport is the in-app extension API host over HTTP—the same host that serves anime sources—so manga works for any sideloaded extension whose manifest declares `capabilities: ["manga"]`. Multiple extensions respond concurrently, and results are merged by chapter number. ## Capability Declaration ```json { "capabilities": ["manga", "chapters"], "apiServer": { "namespace": "mangadex", "contract": "streaming-sources-v3", "routes": ["manga/chapters", "manga/pages"], "healthPath": "/health" } } ``` **Routes:** Ungated and always reachable. They return `501` if the method is absent. * `GET /api/v3//manga/chapters` — Flat chapter rows * `GET /api/v3//manga/pages` — Page images for a chapter ## Bundle Methods ```ts // Required for manga support getMangaChapters(params: MangaChapterParams): Promise // Optional: debug variant with per-sub-provider diagnostics debugMangaChapters(params: MangaChapterParams): Promise<{ results: MangaChapterEntry[]; diagnostics: ProviderDiagnostic[]; }> // Required for reading getMangaPages(params: MangaPagesParams): Promise ``` ## Request Parameters ### MangaChapterParams ```ts interface MangaChapterParams { anilistId?: number; // AniList media ID malId?: number; // MyAnimeList ID title?: string; // Single title titles?: string[]; // Multiple titles (for fuzzy search) } ``` No AniList pre-fetch occurs here—the bundle's internal `enrichMangaParams` handles that once. ### MangaPagesParams ```ts interface MangaPagesParams { chapterKey: string; // Composite key from chapter row providerChapterId?: string; // Provider-specific chapter ID } ``` ## Response Shapes ### MangaChapterEntry Bundle-to-host response shape: ```ts interface MangaChapterEntry { number: number; // Chapter number title?: string | null; // Chapter title volume?: number | null; // Volume number sources: MangaChapterSource[]; // One per sub-provider } ``` ### MangaChapterSource ```ts interface MangaChapterSource { provider: string; // SUB-PROVIDER name (e.g. "mangadex", "allmanga") providerName?: string; // Display name chapterKey: string; // Composite key for pages request providerChapterId: string; // Provider's chapter ID language?: string | null; // BCP-47 scanlator?: string | null; // Scanlation group releaseDate?: string | null; // ISO 8601 } ``` ### Flattened Chapter Row The host flattens nested entries into one row per chapter and sub-provider: ```ts interface MappedMangaChapter { number: number; title?: string | null; volume?: number | null; provider: string; // SUB-PROVIDER name providerName?: string; chapterKey: string; // Round-trips through reader URL providerChapterId: string; language?: string | null; scanlator?: string | null; releaseDate?: string | null; } ``` **Sub-provider to namespace mapping:** The renderer maps `provider` (the sub-provider name) to its owning namespace through a lazy map populated during chapter fetches. ### MangaPageResult ```ts interface MangaPageResult { pages: MangaPageImage[]; } interface MangaPageImage { pageNumber: number; imageUrl: string; headers?: Record; // Referer/Origin for CDN width?: number; height?: number; } ``` {% hint style="info" %} Each page image is registered with the local proxy so CDN `Referer` and `Origin` headers are replayed during load. The proxy returns `proxiedImageUrl` for the renderer. Pages are never cached because proxy tokens expire in approximately 15 minutes. {% endhint %} ## Host Responses ### `GET /api/v3//manga/chapters` ```json { "namespace": "mangadex", "provider": "mangadex", "count": 150, "chapters": [ { "number": 1, "title": "Chapter 1", "volume": 1, "provider": "mangadex", "providerName": "MangaDex", "chapterKey": "mangadex:ch-123", "providerChapterId": "ch-123", "language": "en", "scanlator": "Official", "releaseDate": "2024-01-15T00:00:00Z" } ], "providerStatus": [ { "provider": "mangadex", "status": "ok", "resultCount": 150, "durationMs": 1200 } ], "cached": false, "fetchedAt": "2024-01-20T12:00:00Z" } ``` ### `GET /api/v3//manga/pages` ```json { "namespace": "mangadex", "count": 20, "pages": [ { "pageNumber": 1, "imageUrl": "https://proxy.local/token/abc123", "proxiedImageUrl": "https://proxy.local/token/abc123", "headers": { "Referer": "https://mangadex.org/" }, "width": 800, "height": 1200 } ], "cached": false, "fetchedAt": "2024-01-20T12:00:00Z" } ``` ## Renderer Bridge Primary transport is HTTP to the extension API host. IPC through `invokeExtension` is used as a fallback for an early-launch race. ```ts // Fan out to ALL manga-capable namespaces concurrently const namespaces = mangaNamespaces(base.namespaces || []); // Merge results by chapter number const byNumber = new Map(); for (const ns of namespaces) { const res = await fetch(`${baseUrl}/api/v3/${ns.namespace}/manga/chapters?...`); for (const row of res.chapters) { mergeRow(byNumber, row, ns.namespace); } } ``` **Merge logic:** One row is retained per `(number, provider)`. The sub-provider name maps to the namespace for page requests. ## Caching | Endpoint | TTL | Cache Key | | ---------------- | ------ | ------------------------------------------------------- | | `manga/chapters` | 30 min | `manga-chapters:namespace:anilistId:malId:title:titles` | | `manga/pages` | Never | N/A (proxy tokens expire) | **Bypass:** `?refresh=1` or `?nocache=1` ## Testing Checklist * [ ] `getMangaChapters` returns `MangaChapterEntry[]` with `sources` array * [ ] Each source has `provider` (sub-provider name), `chapterKey`, `providerChapterId` * [ ] `language` set (BCP-47) * [ ] `scanlator` and `releaseDate` when available * [ ] `getMangaPages` returns pages with `imageUrl` and `headers` * [ ] `debugMangaChapters` implemented for per-provider diagnostics * [ ] Handles missing `anilistId`/`malId` (falls back to `title`/`titles`) * [ ] Chapter numbers are numeric, positive * [ ] Volume numbers when applicable ## Related * [Extension Overview](/extensions/extension-overview.md) * [Anime Sources](/extensions/extension-capabilities/sources.md) * [Novel Capability](/extensions/extension-capabilities/novel-capability.md) * [Custom Source](/extensions/extension-capabilities/custom-sources.md) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.tatakai.me/extensions/extension-capabilities/manga-capability.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.