API key
The simplest way into the whole platform: one personal API key unlocking all three — the full Darash scripture engine, Junifye for shareable documents and books, and Lexifye for collaborative, beautifully typeset dictionaries that plug into your books as glossaries.
Complete Trio — Yearly
All three tools on one key, billed yearly — 40% below three separate monthly subscriptions.
What's included
- darash-service (read)
- junifye-service (write)
- lexifye-service (write)
Choose your editions — add as many as you like
Complete Trio — Darash + Junifye + Lexifye
₩29,000 /mo
Complete Trio — Yearly
₩260,000 /yr
Instant download after payment. Yours to keep — re-download it any time, on any device, free.
Have an invite code?
Type it here — you and your friend both get a free cycle when you subscribe.
Features
40% below three separate monthly subscriptions
Two discounts stacked: 20% for taking all three, then 25% again for paying yearly — against buying Darash, Junifye and Lexifye separately month to month. One key, one invoice, one renewal a year. Current figures are shown on this page.
MCP-HTTP endpoint + personal API key
Point any MCP client at darash.publifye.pro with your key.
Full Darash scripture engine
Read access to the complete Darash engine — 59 Bible texts, Strong's Hebrew and Greek, morphology, cross-references and thirteen dictionaries.
Junifye included — shareable documents & books
Write shareable documents and full books, you and your AI side by side, and share them by link.
Lexifye included — collaborative dictionaries
Author dictionaries in every script, share them with groups, publish them as PDFs/EPUB/web — and connect them to your Junifye books as Glossary appendices.
Connect any MCP client
Claude, Cursor, your own agent — anything that speaks MCP.
Cancel anytime
It renews once a year. Cancel whenever you like and you keep access to the end of the year you have paid for.
Publishing under the Publifye imprint — priced separately
When a work is ready, publish it with a registered ISBN-13, legal deposit and a permanent landing page under the Publifye imprint. That is a separate, per-book fee — not part of this subscription.
Complete Trio
Can I cancel?
Cancel from your account to stop the next renewal. Access continues through the paid period, and your authored books, dictionaries and exports remain yours.
Is the bundle actually cheaper?
The Trio combines Darash, Junifye and Lexifye in one subscription. Compare the current bundle and individual prices on the store.
What is each of the three for?
Darash supplies Scripture research and its sources. Junifye turns structured chapters into books, and Lexifye holds reusable dictionaries and glossaries.
Do I need all three?
Choose Darash Solo for Scripture study, Junifye Access for writing, or Junifye + Lexifye for writing with reusable terminology. Choose the Trio when you use all three; the store lists each option.
Is it one key or three?
One personal API key can authorize all three services. Configure each service endpoint in your MCP client; clients that support it can also sign in through Publifye OAuth.
Can I try before paying?
Each service offers its own trial without a payment card. See the store for current trial terms and allowances before choosing the bundle.
I’m writing a novel. Can you help me build its context as we write each chapter?
Yes—keep your own dictionary beside the manuscript, with an entry for every character, place, term, invented word, rule and idea, each defined in one place. Ask your AI to use entry_search and dict_get before drafting each chapter, then entry_add and definition_add_source to record new facts afterwards. For a changed fact, it reads the existing definition and revises it with definition_set_source using the current sha256. You get a growing world and term bible that you and your AI can consult throughout the book.
Help me dig into what “grace” means in my book—its senses, sources and how my definition has changed since the first draft.
Give each sense its own definition under “grace”, cite the sources behind it, and use dict_set_field interlink=true to link related entries in digital reading formats. Your AI can keep research in note_set, refine wording with definition_set_source, and optionally use dict_enrich for cited Hebrew or Greek Strong’s roots when Darash enrichment is configured. definition_history, definition_diff and definition_revert let you inspect and restore retained wording: history covers the last 20 saves within seven days. Save dated milestones in private notes for comparisons beyond that window, so you have a record to dwell on as the book develops.
I’m on book three. Can we use one dictionary so it agrees with book one?
Yes—ask your AI to read the same dictionary before drafting any book in the series, then record new facts there as the series grows. Each Junifye book can connect to that same Lexifye dictionary through book_set connected_dict, while choosing which entries belong in its own glossary. The appendices are snapshots refreshed on rendering; book_get shows glossary drift, and book-local definitions take precedence on a name collision. You get one shared reference for continuity and a way to check when each rendered glossary needs refreshing.
Can the context we built while writing become the printed glossary at the back of my book?
Yes—connect the dictionary to your Junifye book and choose the terms used in the text, those terms plus related entries, or the whole dictionary. Junifye snapshots those definitions into its Glossary appendix when it renders, so you can produce the book’s print interior without retyping them. Check the import report for terms kept from the book’s own glossary, and re-render after dictionary changes. Private authoring notes stay out of the exported dictionary content.
I’m inventing a language for my fantasy or sci-fi novel. Can I build its lexicon as I go?
Yes—add each invented word as an entry, its romanization in translit if needed, and its meanings or usage examples as definitions. Keep your invented etymologies and grammar notes with the entries, then export the lexicon for reading beside the manuscript. Use Latin spelling or other characters covered by the 16-script renderer; custom invented glyphs are not guaranteed. Check the characters in an export before relying on a special script, since unsupported letters can fail the glyph gate.
I think by defining things. Can this be the notebook my ideas grow from?
Yes—make every concept an entry, write what you mean as its definition, and add another sense when the idea branches. Turn on interlink to connect words used in definitions to their own entries in the reader, EPUB and screen PDF, and keep unfinished questions in private notes. Your AI can search the definitions, bring related concepts back into the conversation and refine them as your thinking develops. Recent edits can be compared or restored within the 20-save, seven-day history window; private notes stay out of exports.
I teach a course. Can the vocabulary we build each week become a study booklet?
Yes—start a course dictionary and add each week’s key terms, explanations, examples and source references with your AI. Review the entries as the course develops, then get the print-interior PDF for a paper study booklet and the EPUB for students’ reading apps. You can hand out downloaded files; Lexifye’s own reader and download links still require dictionary access.
My grandmother uses words nobody writes down. Can we make a family or local-dialect dictionary?
Yes—give each dialect word an entry and record its meaning, a sentence she uses, and the person or place it came from in the definition. Keep uncertain spellings and research questions in private notes while you and your AI refine the collection. Export the finished definitions as a PDF or EPUB to give the family, or retain the structured JSON for later use.
Our organisation uses the same acronym three different ways. Can we agree on what it means?
Yes—create a dictionary for the company or organisation, add the agreed meaning of each term or acronym, and separate genuinely different senses under the same entry. Invite named guest editors or attach a group so colleagues can work on those definitions together. Ask your AI to read the entries before writing documents and save agreed revisions with the current sha256, which catches conflicting edits.
Our translation team keeps re-deciding the same words. Can my AI keep one glossary we all use?
Yes—make one private dictionary for the translation and record each agreed term and definition there. Your AI can read it before working on the next passage, then save the team’s wording and references as decisions are made. Invite guest editors or attach the translation group so the team can consult and refine the same entries.
Our Bible-study group keeps returning to “grace” and “covenant”. Can we build our own word-study dictionary?
Yes—keep an entry for each word, with your group’s explanations, separate senses and Bible references, then return to those definitions as your study deepens. When Darash enrichment is configured, cite Strong’s numbers and use dict_enrich to add the referenced Hebrew or Greek words with native lemmas, transliterations and composed definitions. Your manually authored entries win term collisions, and the enrichment tool reports what it changed or whether enrichment is unavailable.
How do I connect?
Add https://lexifye.publifye.com/mcp to an OAuth-capable MCP client and sign in with Publifye for the trial. Paid plans use your personal API key as X-API-Key at the same URL; obtain or rotate the key in Purchases and switch the client from trial OAuth when needed.
What is a Lexifye dictionary?
A Lexifye dictionary is a structured collection of your terms and definitions, with source information. Your assistant can add entries, keep terminology consistent and render the dictionary for reading or export.
How can I use Lexifye to build the context of my book while I write?
Say to your AI: “Keep my book context beside the manuscript; read it before every chapter and add what we establish afterwards.” It reads house_style and source_syntax, creates the dictionary with dict_create, then uses entry_search and entry_get or paginated dict_get before drafting; afterwards it uses entry_add and definition_add_source for new characters, places, terms, rules and ideas, or definition_get_source and definition_set_source with the current sha256 for revisions. You end up with an author’s dictionary that grows through this repeated writing workflow.
How can I use Lexifye to dig into what a word means in my book over time?
Say: “Help me dwell on grace: its senses, sources and changes since my saved first-draft milestone.” Your AI finds it with entry_search and entry_get, uses definition_add_source for each sense, definition_set_source with a fresh sha256 to refine wording, note_set for research, dict_set_field interlink=true for connections, and optionally dict_enrich for cited Strong’s roots when configured. It uses definition_history and definition_diff to compare retained saves, or definition_revert with the current sha256 to restore one. You get developed meanings and sources; history keeps the last 20 saves within seven days, so save dated milestones in notes for longer comparisons.
How can I use Lexifye to keep a whole series consistent across books?
Say: “Use one series dictionary before drafting any volume, so book three follows the facts we established in book one.” Your AI consults the same Lexifye dict_id with entry_search and entry_get or paginated dict_get, records new facts there, then uses Junifye book_set connected_dict with that same ID for each connected volume. It checks book_get glossary_import and glossary_drift, including book-local overrides, and refreshes stale print appendices with print_set on already configured books. You get one shared context and separate glossary snapshots; each snapshot changes when its book is rendered.
How can I use Lexifye to turn my book’s context into its printed glossary or appendix?
Say: “Put the context terms readers need into my book’s printed glossary.” Your AI gets the dictionary ID through Lexifye dict_get, connects it with Junifye book_set connected_dict, and sets glossary_scope to used for terms in the text, used_recursive to include related entries, or full for everything. It calls print_set with your chosen printer—or just book_id when configured—then checks book_get glossary_import and glossary_drift for the result and any book-local overrides. You get a Glossary appendix in the book’s print interior; private notes stay out, and later dictionary changes need a new render.
How can I use Lexifye to share my dictionary with an editor or co-author and take access back?
Say: “Give my editor access to this dictionary; remove it when our work is finished.” As owner, your AI uses guest_find_user to find their Lexifye account, confirms the returned user_id, and calls guest_add; later it checks guest_list and uses guest_remove. It also checks attached groups: dict_group_remove removes that group’s grant, while any other guest or group grant still applies. You get shared editing and revocable live access; files someone already downloaded remain with them.
How can I use Lexifye to start from words I already have?
Say: “Turn this pasted list of words and meanings into my dictionary, and ask me about missing definitions.” After house_style and source_syntax, your AI creates a dictionary with dict_create or uses the selected existing one, checks each term through entry_search and entry_get, then uses entry_add and definition_add_source for new entries. For agreed changes to existing definitions it uses definition_get_source and definition_set_source with the current sha256, then dict_get to review the results and get export links. You end up with structured entries from your list through ordinary authoring tools; this walkthrough does not assume a CSV or TBX importer.
Can I find an entry when I only remember part of the word?
Yes—entry_search finds a literal fragment in a headword or transliteration, ignoring case and diacritics, and can search definition bodies with content=true. Your AI reviews the matches and fetches the chosen entry with entry_get or definition_get_source, so it can read the definition before using it.
What if something is deleted by mistake?
Deletes are soft: dictionaries, entries and definitions stay restorable in the trash for 30 days. Use trash_list to find the deleted object and the matching restore tool before that window ends; definition history still has its own retention limits.
Is it a public dictionary site?
No—dictionary content is private and requires credentials and authorised access. Knowing a dictionary ID or artifact link does not grant access, and anonymous readers cannot browse or fetch the content.
Who can see my dictionaries?
You, invited guest editors, members of an attached group and authorized Publifye services can read your dictionaries. Junifye can import a glossary through authorized service-to-service access. Content and downloads require credentials; a dictionary ID or link does not grant public access.
Can other people work on one with me?
Yes. Add a named guest editor, or attach a group; removing them revokes access at once, for reading and writing alike.
Which plan?
Choose Lexifye Access for dictionaries, Junifye + Lexifye when the glossaries feed your books, or the Complete Trio when you also need Darash research. The paid bundle uses one personal API key; see the store for current offers.
Can I try it before paying?
Yes — a free trial with no card, the full product. Trial length and allowance: see the store.
I write books too — is there a bundle?
Choose Lexifye Access for dictionaries, Junifye + Lexifye when the glossaries feed your books, or the Complete Trio when you also need Darash research. The paid bundle uses one personal API key; see the store for current offers.
Can I cancel?
Use the signed-in billing portal to manage or cancel your subscription. Export the dictionary files you want to retain and consult the current account terms for renewal and access conditions.