Junifye Access

Yes. Your AI reads house_style and source_syntax, organises your supplied manuscript into chapters, and writes source text with chapter_set_source or structured block tools. book_get supplies the web reader, reading PDFs and EPUB links from that same book. For a physical edition, configure print_set for your printer and inspect the resulting interior and cover report; you send the files to the printer.

Yes. If your assistant passes a translation code instead of typing the text, Junifye fetches the verse text from Darash itself. References, Hebrew and Greek spans and Strong's numbers are first-class content in the book, not formatting.

Yes. Choose a supported printer preset or custom trim to produce an interior PDF and its print report. A full-wrap cover is available when spine geometry is supplied by the preset or your printer; inspect warnings and confirm the printer’s requirements before upload.

Yes. Your assistant can open a browser editor link (protected by a 4-digit PIN) for a human, or add another Junifye user as a guest editor who can change content but not publish, delete or re-brand. Every change is versioned.

Saved versions can be restored while retained. Each chapter keeps its version history; your assistant can show the diff and revert, and the revert is recorded as a new version so the trail stays complete.

Yes. Each edition is its own book linked to the original, and readers switch between them. Right-to-left languages (Hebrew, Arabic, Farsi) get the right fonts and page layout.

Yes. book_epub_check inspects the actual built EPUB and reports missing metadata, ISBN identification and cover presence. It distinguishes EPUB 3 metadata completeness from Apple metadata readiness; it does not promise final store acceptance or deliver the book.

Yes. Connect a readable Lexifye dictionary and Junifye can compile its terms into the book’s glossary appendix. The book keeps a snapshot, so dictionary changes need a new render; drift information tells your assistant when the appendix may be stale.

Say: “Turn my manuscript into a book I can read, send as an ebook and print.” Your AI reads house_style and source_syntax, creates the book with book_create, then uses chapter_create and chapter_set_source for your chapters, or structured block tools where needed. It calls book_get for the reader, reading PDF and EPUB links. For a paperback it uses print_get, then print_set for your chosen printer and checks the report. You get reading and print artifacts from one book source; you review the content and send the files to the printer or store.

Say: “Make a four-week booklet from my sermon notes, quoting these passages.” Your AI reads house_style and source_syntax, creates the book and chapters, and writes your notes using chapter_set_source. It calls block_add_bible_quote with your translation code and no supplied text so Junifye retrieves the passage from Darash. It uses book_get for reading links and print_set if you want a print interior. You get your notes and retrieved quotations in one structured booklet, with references preserved; your own claims remain distinct from the quoted text.

Say: “Prepare this book for my chosen printer and show me any problems.” Your AI uses print_get for the preset menu and current configuration, then print_set with your chosen preset or custom geometry. A full-wrap cover needs preset spine geometry, your printer’s formula, or its stated spine_mm with spine_mm_for_pages. It checks print_get and the report for page count, fonts, images, bleed and spine warnings. You get the interior PDF and an eligible wrap cover to review against your printer’s requirements; Junifye does not print or ship the book.

Say: “Give my editor this chapter, then show me what changed.” Your AI uses edit_session_create and shares the editor URL and PIN separately. For an editor with a Junifye account it can instead confirm the user through guest_find_user and use guest_add. Afterwards it reads chapter_history and chapter_diff, and uses chapter_revert only for the version you want restored. You get shared content editing and a reviewable history; reverting creates a new version. Guest content access does not include publishing, deleting the book or changing its branding.

Say: “Make an English edition and link it to my Norwegian original.” Your AI reads the original chapters with chapter_get_source, creates a separate book with book_create and the intended language, and writes the reviewed translation with chapter_create and chapter_set_source. It preserves reference and original-language macros, links the edition with book_set_translation_of and checks book_get editions. You get separate texts under a reader language picker; supported right-to-left languages use their own layout. Translation still needs your review, and a separate edition does not update itself when the original changes.

Say: “Use this dictionary as my book’s glossary and check it after revisions.” Your AI uses book_set connected_dict with the readable Lexifye dictionary ID, then glossary_scope as used, used_recursive or full. It calls print_set for the chosen printer, or with just book_id when configured, then checks book_get glossary_import and glossary_drift, including local overrides. You get a rendered glossary appendix. Later dictionary edits need a new render; if Lexifye is unreachable, the AI reports unknown freshness rather than claiming the snapshot is current.

Where enabled, a paid plan can assign a real ISBN-13 to a substantially complete eligible digital book, naming Publifye as its publisher. Your author profile and the book must pass the stated checks, and you must personally accept the publisher terms before allocation; your assistant cannot accept for you. A print ISBN is always your own.

Not unless you choose. New books are unlisted; the private PDF link works as an access token for anyone you give it to, so treat it like a key. Listing in the public library is a separate, reversible setting.

Yes. book_export_begin gives a one-time download URL for an editable book bundle. After your offline edits, book_import_begin gives an upload URL; only changed chapters are applied, and newer server edits are reported as conflicts. You keep a portable copy and choose how to reconcile any conflict.

No. Junifye is an MCP server your assistant drives, and there is a browser editor when you would rather type. Connect by adding https://junifye.publifye.com/mcp as a custom connector in any OAuth-capable MCP client.

Yes — a free trial with no card, the full product from first use. Trial length, daily allowance and plan prices: see the store.

Choose Junifye Access for writing, Junifye + Lexifye for writing with a reusable dictionary, or the Complete Trio to add Darash Scripture research. Each service still has its own MCP endpoint; the store shows the current bundle terms and prices.

Cancel from your account at any time to stop the next renewal. Access continues through the paid period, and your books remain yours and exportable.

Yes, a trial without a payment card lets you use the authoring product. Check the store for current trial duration, allowance and the plan to continue with.

You can author chapter-structured books and documents through MCP or the browser editor. The same structured source becomes typeset PDFs, an HTML reader and an EPUB; use print_set when you need printer-specific files.

It is organised around books, chapters and structured content rather than freely placing objects on a page. One source renders into several reading formats with consistent typesetting.

No, the browser editor is available when you want to type. An MCP assistant can also author directly into the same book and create an editor link for a human.

Lexifye holds a reusable dictionary, and Junifye can compile a connected dictionary into a glossary appendix. Dictionary edits reach the appendix after a new render; Junifye + Lexifye is the combined plan on the store.

Cancel from your account to stop the next renewal. Access continues through the paid period, and your books remain yours, readable and exportable.