Ink Reader platform
Build books and sources that stay portable.
Learn the Dotbook format, create streamable books, or connect a content source through Ink Reader's normalized HTTP addon API.
Dotbook
A portable book container designed for clean chapters, rich nodes, streaming, conversion, and long-term ownership.
02 / APIProvider addons
A stable, read-only HTTP contract that lets users install sources without running third-party code inside the app.
One reading model
Ink Reader treats a packaged EPUB, a local .book, and a remote provider as different ways to obtain the same normalized book. The reader should not need source-specific UI or parsing rules.
Books and reading state can move without being locked to one app or service.
Metadata, chapter indexes, chapters, and assets can be fetched independently.
Provider servers return normalized data; the mobile app never executes addon scripts.
Choose your starting point
Use Dotbook when you own or produce the book data. Use the provider API when adapting an existing catalogue or website. A provider may expose its books as streamable Dotbook resources, which lets both models meet at the same boundary.
Keep an explicit version in manifests and clients. Ink Reader will preserve backwards compatibility as these contracts mature.