Hi HN. I'm the developer (and a pastor). This project was born out of my own frustration.
I'm a $43k-level power-user of Logos Bible Software, but I was still spending 10-20 hours a week on the exegetical work—collating word studies, parsing Greek/Hebrew, and comparing parallels for my sermons. I built the tool I wished I had.
The result is the Anselm Project. It's two parts:
The Engine (Free): A 200M+ token generative database of the entire 66-book Bible. It uses LLMs to generate a full scholarly apparatus (morphology, parallels, and in-progress text-crit) for every verse. You can browse this for free. There's no login needed for this part.
The SaaS (Paid): A report generator on top. It synthesizes all that data into 40-page sermon prep reports or 60-page academic briefs. I'm a solo dev, not a marketer. I'd also love to retire someday. Ministry doesn't pay much.
The tech: The 200M+ token dataset was generated via API calls in a massive batch process. My cost per academic report is about $0.07. I'm a solo dev, not a marketer.
The free generative Bible is open for browsing. I'd love your feedback on the tech, the model's output, and the (likely buggy) UI. Happy to answer any questions about the data generation, costs, or the tech stack.
My friend, I signed up, and looks like the passage validator is too strict on Bible refs, so I can't generate a report. It rejects smart quotes, en dashes, semicolons, and abbreviations, and seems to require full book names, ASCII hyphens, and comma-separated refs in one line. The format examples also seemed inconsistent.
Are they matching against a simple regex?
Inconsistent example format:
```
Enter any Bible reference - single verses, ranges, or entire chapters. Examples: "Matthew 5:3-12", "Psalm 23", "1 Corinthians 13"
Invalid reference format (e.g., John 3, 1 Cor 13:4-7, Gen 1-2). Book name only is not allowed.
Probably too simple, in my estimation. I was originally pulling from the LLM to get individual texts before bible itself was part of it, and when I changed it to using the fully generated APB I probably broke the passage validator.
I'll work immediately on that. Really sorry - but that's the exact thing I needed. Thanks for finding that. I'll try and add a few more credits so you can test more and find more problems.
Also, the Synod "works" but isn't quite ready for primetime... or even an early morning jog.
This should be fixed. I expanded out the input to include pretty much everything that's reasonable, and allow for : or periods. I used Logos pretty heavily so have gotten used to periods for notation.
I also added about 20 credits for you, if you feel up to trying the engine.
Thanks! Really looking forward to seeing the output, but still broken on my side (Chrome browser). The form is rejects multi-reference input and seems to treat the whole line as one ref.
Fails with:
```
Matthew 5:31-32; Matthew 19:3-9; Mark 10:2-12; Luke 16:18; 1 Corinthians 7:10-16; 1 Corinthians 7:39; Romans 7:2-3
Ah - it is only designed to do a report on one continuous passage at a time. It's not designed to handle multiple passages at the same time. I could make that clearer.
It's probably my desire as a expository preacher to only handle a passage in its immediate context when I can help it.
Thinking about it, my "Synod" system (in progress - probably a week out given my work schedule) should easily be able to handle this kind of topical request with multiple verses and topical ideas together. The super-alpha version can be found at the bottom of the "Create Report" page.
Eventually, it will be a back and forth discussion between AIs batting a question around by a mixture of experts system with a summary report provided on theological questions. Topical would obviously be included in that.
Hi HN. I'm the developer (and a pastor). This project was born out of my own frustration.
I'm a $43k-level power-user of Logos Bible Software, but I was still spending 10-20 hours a week on the exegetical work—collating word studies, parsing Greek/Hebrew, and comparing parallels for my sermons. I built the tool I wished I had.
The result is the Anselm Project. It's two parts:
The Engine (Free): A 200M+ token generative database of the entire 66-book Bible. It uses LLMs to generate a full scholarly apparatus (morphology, parallels, and in-progress text-crit) for every verse. You can browse this for free. There's no login needed for this part.
The SaaS (Paid): A report generator on top. It synthesizes all that data into 40-page sermon prep reports or 60-page academic briefs. I'm a solo dev, not a marketer. I'd also love to retire someday. Ministry doesn't pay much.
The tech: The 200M+ token dataset was generated via API calls in a massive batch process. My cost per academic report is about $0.07. I'm a solo dev, not a marketer.
The free generative Bible is open for browsing. I'd love your feedback on the tech, the model's output, and the (likely buggy) UI. Happy to answer any questions about the data generation, costs, or the tech stack.
Thanks.
My friend, I signed up, and looks like the passage validator is too strict on Bible refs, so I can't generate a report. It rejects smart quotes, en dashes, semicolons, and abbreviations, and seems to require full book names, ASCII hyphens, and comma-separated refs in one line. The format examples also seemed inconsistent.
Are they matching against a simple regex?
Inconsistent example format:
```
Enter any Bible reference - single verses, ranges, or entire chapters. Examples: "Matthew 5:3-12", "Psalm 23", "1 Corinthians 13"
Invalid reference format (e.g., John 3, 1 Cor 13:4-7, Gen 1-2). Book name only is not allowed.
```
Probably too simple, in my estimation. I was originally pulling from the LLM to get individual texts before bible itself was part of it, and when I changed it to using the fully generated APB I probably broke the passage validator.
I'll work immediately on that. Really sorry - but that's the exact thing I needed. Thanks for finding that. I'll try and add a few more credits so you can test more and find more problems.
Also, the Synod "works" but isn't quite ready for primetime... or even an early morning jog.
This should be fixed. I expanded out the input to include pretty much everything that's reasonable, and allow for : or periods. I used Logos pretty heavily so have gotten used to periods for notation.
I also added about 20 credits for you, if you feel up to trying the engine.
``` BIBLE_ABBREVIATIONS = { 'Gen': 'Genesis', 'Gn': 'Genesis', 'Exod': 'Exodus', 'Ex': 'Exodus', 'Exo': 'Exodus', 'Lev': 'Leviticus', 'Lv': 'Leviticus', 'Num': 'Numbers', 'Deut': 'Deuteronomy', 'Dt': 'Deuteronomy', 'Josh': 'Joshua', 'Jos': 'Joshua', 'Judg': 'Judges', 'Jdg': 'Judges', '1 Sam': '1 Samuel', '1Sam': '1 Samuel', '1st Sam': '1 Samuel', '1S': '1 Samuel', '1 S': '1 Samuel', '2 Sam': '2 Samuel', '2Sam': '2 Samuel', '2nd Sam': '2 Samuel', '2S': '2 Samuel', '2 S': '2 Samuel', '1 Kgs': '1 Kings', '1Kings': '1 Kings', '1st Kings': '1 Kings', '1K': '1 Kings', '1 K': '1 Kings', '2 Kgs': '2 Kings', '2Kings': '2 Kings', '2nd Kings': '2 Kings', '2K': '2 Kings', '2 K': '2 Kings', '1 Chr': '1 Chronicles', '1Chron': '1 Chronicles', '1st Chronicles': '1 Chronicles', '2 Chr': '2 Chronicles', '2Chron': '2 Chronicles', '2nd Chronicles': '2 Chronicles', 'Neh': 'Nehemiah', 'Esth': 'Esther', 'Est': 'Esther', 'Ps': 'Psalms', 'Psa': 'Psalms', 'Prov': 'Proverbs', 'Pro': 'Proverbs', 'Eccl': 'Ecclesiastes', 'Ecc': 'Ecclesiastes', 'Song': 'Song of Solomon', 'SOS': 'Song of Solomon', 'Cant': 'Song of Solomon', 'Isa': 'Isaiah', 'Jer': 'Jeremiah', 'Lam': 'Lamentations', 'Ezek': 'Ezekiel', 'Eze': 'Ezekiel', 'Dan': 'Daniel', 'Hos': 'Hosea', 'Obad': 'Obadiah', 'Ob': 'Obadiah', 'Mic': 'Micah', 'Nah': 'Nahum', 'Hab': 'Habakkuk', 'Zeph': 'Zephaniah', 'Zep': 'Zephaniah', 'Hag': 'Haggai', 'Zech': 'Zechariah', 'Zec': 'Zechariah', 'Mal': 'Malachi', 'Matt': 'Matthew', 'Mt': 'Matthew', 'Mk': 'Mark', 'Mrk': 'Mark', 'Lk': 'Luke', 'Luk': 'Luke', 'Jn': 'John', 'Jhn': 'John', 'Rom': 'Romans', 'Rm': 'Romans', '1 Cor': '1 Corinthians', '1Cor': '1 Corinthians', '1st Corinthians': '1 Corinthians', '2 Cor': '2 Corinthians', '2Cor': '2 Corinthians', '2nd Corinthians': '2 Corinthians', 'Gal': 'Galatians', 'Eph': 'Ephesians', 'Phil': 'Philippians', 'Php': 'Philippians', 'Col': 'Colossians', '1 Thess': '1 Thessalonians', '1Thess': '1 Thessalonians', '1st Thessalonians': '1 Thessalonians', '2 Thess': '2 Thessalonians', '2Thess': '2 Thessalonians', '2nd Thessalonians': '2 Thessalonians', '1 Tim': '1 Timothy', '1Tim': '1 Timothy', '1st Timothy': '1 Timothy', '2 Tim': '2 Timothy', '2Tim': '2 Timothy', '2nd Timothy': '2 Timothy', 'Phlm': 'Philemon', 'Phm': 'Philemon', 'Heb': 'Hebrews', 'Jas': 'James', 'Jms': 'James', '1 Pet': '1 Peter', '1Pet': '1 Peter', '1st Peter': '1 Peter', '2 Pet': '2 Peter', '2Pet': '2 Peter', '2nd Peter': '2 Peter', '1 Jn': '1 John', '1John': '1 John', '1st John': '1 John', '2 Jn': '2 John', '2John': '2 John', '2nd John': '2 John', '3 Jn': '3 John', '3John': '3 John', '3rd John': '3 John', 'Rev': 'Revelation', 'Rv': 'Revelation' } ```
Thanks! Really looking forward to seeing the output, but still broken on my side (Chrome browser). The form is rejects multi-reference input and seems to treat the whole line as one ref.
Fails with:
```
Matthew 5:31-32; Matthew 19:3-9; Mark 10:2-12; Luke 16:18; 1 Corinthians 7:10-16; 1 Corinthians 7:39; Romans 7:2-3
```
```
"Matthew 5:31–32", "Matthew 19:3–9", "Mark 10:2–12", "Luke 16:18", "1 Corinthians 7:10–16", "1 Corinthians 7:39", "Romans 7:2–3"
```
```
Matt 5:31-32, 19:3-9; Mk 10:2-12; Lk 16:18; 1 Cor 7:10-16, 7:39; Rom 7:2-3
```
```
Matt 5.31-32, 19.3-9; Mk 10.2-12; Lk 16.18; 1 Cor 7.10-16, 7.39; Rom 7.2-3
```
```
Matthew 5:31-32 Matthew 19:3-9 Mark 10:2-12 Luke 16:18 1 Corinthians 7:10-16 1 Corinthians 7:39 Romans 7:2-3
```
Maybe the validator isn't splitting the string on separators before parsing, or choke on leading numerals or spaces, or normalization to ascii?
Ah - it is only designed to do a report on one continuous passage at a time. It's not designed to handle multiple passages at the same time. I could make that clearer.
It's probably my desire as a expository preacher to only handle a passage in its immediate context when I can help it.
I see. I tend to research specific topics at a time.
But it still doesn't seem to work.
I tried `Matthew 19:3–9` and `"Matthew 19:3–9"` and still warns of invalid formatting.
I wanted to let you know I have incorporated a "Topical Report" engine. I'd love your feedback, as a topical user.
Thinking about it, my "Synod" system (in progress - probably a week out given my work schedule) should easily be able to handle this kind of topical request with multiple verses and topical ideas together. The super-alpha version can be found at the bottom of the "Create Report" page.
Eventually, it will be a back and forth discussion between AIs batting a question around by a mixture of experts system with a summary report provided on theological questions. Topical would obviously be included in that.
Got it. Sorry about that. I don't use em and en dashes often. But the system accepts either now.
I will think about what would go into a topical studies engine.
This is a great project. Very cool
Glad you think so. :)