Ground my Sunday sermon in what the passage actually says.
Yes. Your assistant uses verse_study for the passage, its tagged words, parsing and cross-references, then strongs_in_verse to verify the word it wants to discuss. word_study returns the available lexicon entries, usage and provenance for that Strong’s number. You get sources to inspect before making a sermon point; the assistant must distinguish retrieved lexical data from its interpretation.
Check the Greek before I build a sermon point on it.
Yes. strongs_in_verse lists the tagged original-language words with their Strong’s numbers in each verse. Your assistant can show which number occurs at each place and open its lexicon entries before comparing meanings, rather than inferring the Greek from an English translation or memory.
Help me prepare a Greek parsing class from this passage.
Yes. Darash supplies parsing and lexicon data verse by verse, and your assistant lays it out as a student worksheet and answer key. Use get_morphology for each verse and word_study for the key words; the worksheet itself is assembled by your assistant.
Compare what these translations say in the same verse.
Yes. Start with list_bibles to see the translations and identifiers available on the connected service, including Norwegian, Persian and Latin texts where held. compare_verses returns the named translations side by side, so your assistant quotes the text it retrieved.
Help me research a theme for the book I am writing.
Yes. Text search finds matching verses, get_cross_refs retrieves their stored cross-references, and multi_dict_lookup brings back topical entries from the dictionaries. Your assistant can organise the returned evidence into research notes and identify each source; a search page is not a promise that every passage on a theme has been found.
Make my personal Bible-study agent check its sources.
Yes. A personal MCP-capable study agent can call Darash for the verse, verify its tagged words with strongs_in_verse, and use word_study for named lexical sources. Keep edition and known gaps with quotations. Providing Darash or its outputs to your own users through an app, bot or service requires the appropriate separate licence; personal access does not authorize that use.
Help me follow a Hebrew or Greek word beyond its gloss.
word_study brings together named lexicon entries, frequency, sample verses and etymology. Use search_strongs for occurrence passages and etymology_tree for recorded derivation links; get_synonyms, co_occurrence and hapax_list support further comparisons. Your assistant should separate observed usage and sources from its interpretation, and follow result limits before calling a search exhaustive.
How can I use Darash to research a sermon from the original words?
Say: “Show me what this passage says before I build my sermon point.” Your AI starts with get_health and list_bibles, uses verse_study for each verse, then strongs_in_verse to verify the word in question. It calls word_study for that Strong’s number and names the retrieved lexicons and editions. You get passage text, tagged Hebrew or Greek words, parsing, cross-references and lexical sources; your interpretation remains distinct from the retrieved material.
How can I use Darash to test whether two verses use the same word?
Say: “Do these verses really use the same Greek word?” Your AI calls strongs_in_verse for each reference and compares the returned Strong’s numbers, lemmas and locations. It opens get_strongs or word_study for the relevant numbers and uses get_synonyms when comparing related words. You get the tagged words actually present in each verse and named lexical entries, rather than a claim inferred from English wording. A shared word or synonym relationship does not by itself settle the passage’s meaning.
How can I use Darash to build a parsing worksheet for my class?
Say: “Prepare a worksheet on the verbs in Philippians 2:5–8.” Your AI retrieves the text with get_verse, calls get_morphology verse by verse, and uses word_study for key vocabulary. It arranges the returned lemmas, morphology codes and descriptions into student questions and a separate answer key, with references and sources attached. You get a worksheet assembled by your AI from retrieved parsing data; Darash supplies the data, and you review the teaching material.
How can I use Darash to compare Bible translations?
Say: “Compare this verse in Norwegian, English and Persian.” Your AI calls list_bibles to find the translations actually available and their identifiers, confirms your choices, then uses compare_verses for each reference. It labels every quotation with its translation and reference, and uses strongs_in_verse and word_study for any original-language claim it adds. You get retrieved texts side by side, with the AI’s explanation kept distinct; translation availability does not grant unlimited republication rights.
How can I use Darash to collect sources for a theme in my book?
Say: “Collect wilderness passages and the dictionary articles behind them.” Your AI calls search for matching verse text, follows returned pagination, and uses get_cross_refs for selected verses. It checks list_dicts and calls multi_dict_lookup or lookup_dictionary for relevant topics. You get verses, stored cross-references and named articles for your research notes, with edition, provenance and known gaps retained. It describes the scope searched and does not call a limited result page every passage on the theme.
How can I use Darash to study a word’s senses and usage?
Say: “Help me study this Hebrew or Greek word beyond its short gloss.” Your AI verifies the word in the starting verse with strongs_in_verse, then calls word_study for its Strong’s number. It follows search_strongs into occurrence passages, etymology_tree into recorded derivations and get_synonyms for related vocabulary. It checks the lexicon edition and provenance before quoting. You get lexical senses beside usage examples and source references; the AI does not assume every listed sense applies to the starting verse.
Do I need a special app?
Use an MCP client you already have and add https://darash-api.publifye.com/mcp. Sign in through Publifye where the client supports OAuth, or configure your personal key in a supported client; Darash supplies the research tools to that assistant.
Is this a Bible reader or a commentary?
Neither. It returns text, parsing, lexicon entries, dictionary articles and cross-references with their sources attached. It does not hand you a doctrinal verdict; you and your assistant work through the evidence.
Which dictionary editions are these, really?
Every dictionary carries a provenance block: work, author, edition, source, method, licence and known gaps. The Thayer is the 1889 Corrected Edition, transcribed from the page images; Webster's edition is not yet pinned, and Darash says so rather than guessing.
Can I try it first?
Yes — there is a free trial with no card; you sign in with a Publifye account through OAuth and get the full engine, not a demo corpus. The trial length and daily allowance are shown on the store.
What can I buy after the trial?
Darash Solo (the research engine on your own key), the Complete Trio (Darash + Junifye writing + Lexifye dictionaries on one key), or Darash for Organizations by quote. Current prices in your currency: see the store.
Can our church or seminary run it ourselves?
Yes, with Darash for Organizations: self-hosted on your own servers or managed by us, licensed per deployment and not metered per call when self-hosted. What leaves a self-hosted instance is the licence check and an aggregate call count — never a query, reference or result.
Can I cancel?
Any time, from your account. Cancelling stops the next charge; your key works to the end of the period you paid for.
Do our Scripture queries leave a self-hosted installation?
On a self-hosted Engine deployment, licence checks and aggregate call counts leave the instance, but query text, references and results do not. Hosted Solo and managed deployments run on Publifye’s infrastructure; the self-hosted statement does not describe those arrangements.