harness.talk
Seek, and ye shall find.
The King James Bible, exact to the letter, at one address for every verse. Open it like a book. Call it like an API. The same words, either way.
A reference opens the verse. A phrase searches all 31,102. A 127.x.x.x address resolves it.
- GET
- https://harness.talk/api/v1/verses/{ref}
- shell
- npx harness-talk
Two ways in
Read it
A measured column, a rubricated margin, nothing between you and the words.
66 books, 31,102 verses. Hebrew and Greek one tap away beside any verse. Every link you share renders as Scripture, not a URL.
Build on it
One command. Every verse on your machine, verified, no key and no account.
A loopback daemon, an MCP server, and typed clients, all read-only and hashed against one Merkle root. Add it to Claude, Cursor or any agent in one step.
Settings → Developer → Edit Config (claude_desktop_config.json)
{
"mcpServers": {
"harness-talk": {
"command": "npx",
"args": [
"-y",
"harness-talk",
"mcp"
]
}
}
}Three layers, one referent
I
LiveCorpus
66 books, 1,189 chapters, 31,102 verses of the King James Version. Every verse carries a SHA-256 leaf; the whole tree resolves to one Merkle root. Provenance is declared for every source, and nothing unverified is served.
root e33985722301b534baa0…Read the text →II
LiveFabric
Linux routes all of 127.0.0.0/8 to the loopback interface. The 66-book canon fits the quartet exactly: 127.book.chapter.verse. A small daemon serves every verse at its own address on port 1611 — so any process on any GNU/Linux host can read scripture over a plain socket.
curl 127.43.3.16:1611See the addressing scheme →III
LiveHarness
Documentation written for agents first. A keyless REST API, an MCP server, typed clients, bulk exports, problem+json errors, and a covenant for honest citation. Nothing is locked; the only ask is provenance.
llms.txt · openapi.json · tools.jsonPick up the harness →Proof, not promise
Every claim on this page is one request away. Resolve a reference, fetch the verse, recompute its hash.
GET /api/v1/verses/jn.3.16Fetching…
Why a fixed text
Machines increasingly coordinate with one another, and each model carries its own private notion of what is true. A shared referent changes that: when two agents cite jn.3.16, they name the same words with the same hash, from a text that has not moved in four centuries. Agreement becomes something you can check rather than something you must trust.
The King James Bible is the most widely printed, quoted, and memorised English text there is, in the public domain everywhere, with a New Testament in the Textus Receptus lineage. It is the right foundation because it is fixed, free, and already woven through the language every model learned from.
harness.talk keeps that text exact, makes it addressable, and hands agents the tools to build on it. Woven into interoperable infrastructure, the Word becomes the fabric — not an application on top of technology but the ground it stands on — so that what is built is more durable, more honest, and better for the world.
In the beginning was the Word, & the Word was with God, and the Word was God.
Thy word is a lampe vnto my feete: and a light vnto my path.
Text: King James Bible, 1611 first edition. Built 2026-09-06.