Three ways in — connect your own MCP client, get your own agent on Telegram, or run the engine in-house.
**Most people want Darash Access** — a personal API key that drops the full Scripture engine into Claude, Cursor, Codex, or any MCP client you already use. It is the cheapest option and the fastest to set up. Choose **Hermes Agent** if you would rather just chat with your own assistant on Telegram with zero technical setup, or **Darash Engine** if you need it running on your own infrastructure at organisation scale.
$7/mo
MCP-HTTP access with your own API key — the simplest way into Darash.
$48/mo
Your own AI agent on Telegram — it researches and writes for you.
Custom
Run Darash in-house, on your own infrastructure, for your whole team.
A personal API key for any MCP client (Claude Desktop, Claude Code, Cursor, Codex, or your own agent). Built for pastors, students, and researchers who live inside an AI assistant. You get read access to the **full engine** (see the complete source list below). **PubWrite is included** so you can turn what you find into shareable documents and books. Nothing to install, nothing to host — point your client at your endpoint with your key and ask. Cancel anytime.
A dedicated, always-on agent that lives in **Telegram** and is owner-locked to you. For people who want the power of Darash without ever touching a config file. After purchase, a guided chat walks you through creating a bot (BotFather), pasting one token, and tapping Start — a few minutes, no technical knowledge needed. Your agent then **researches Scripture and writes documents and books for you**, on demand and privately. The complete engine runs behind the friendly chat.
License the **complete engine** for in-house use. For ministries, schools, and companies that need Darash on their own infrastructure — self-hosted, on-prem, or **fully managed by us**. Scales to **40,000 concurrent users**. Bring your own corpus and integrations; the PubWrite authoring server is included. Pricing is per deployment, so it is quote-based: tell us your size, expected load, and hosting preference and we tailor it. Your whole team connects any MCP client to your dedicated endpoint, exactly like Access — at scale.
Every plan gives the same engine. **Text:** 59 Bible translations across 50+ languages. **Hebrew & Greek:** the full Strong's concordance, with the **Abbott-Smith** (Greek), **BDB / Brown-Driver-Briggs** (Hebrew), **LSJ / Liddell-Scott-Jones** (Greek) and **Thayer** lexicons; morphological parsing across 31,166 verses. **References:** 446,544 cross-references. **13 dictionaries:** ISBE, Bullinger, Fausset, Easton, Nave's, Smith, Hitchcock, Torrey, Hawker, Wilson's, ATS, Webster's 1828, Thayer. **Word study:** semantic search, Hebrew pictographs, gematria, etymology trees. **ELS:** Torah-code discovery over the **304,805-letter, SHA256-verified Koren Torah** — the same consonantal text used by the 1994 Witztum–Rips–Rosenberg study in *Statistical Science*. Delivered as MCP tools your AI calls directly.
The lexical tools are deterministic scholarship — the same answer every time. The **ELS layer is a discovery-and-statistics tool, not a magic decoder.** Raw occurrence counts are *not* the signal: a shuffled Torah with identical letter frequencies produces nearly identical counts. What Darash measures is **placement** — where a name lands and what surface word it threads through — scored with p-values against thousands of random words at the same skip and against independently shuffled Torahs. Darash hands you the tools to run those tests yourself and **reproduce every number** against the same verified text everyone else uses. It shows you the evidence; it does not tell you what to believe.