crossreferences.org valid
CrossReferences.org
An open, freely licensed corpus of phrase-level Bible cross-references, derived from the Treasury of Scripture Knowledge (TSK) and re-anchored to modern translations. Each reference is attached to a specific phrase in the target translation's own wording, and multi-verse references are kept whole rather than flattened into separate verse links.
For agents: Open, freely licensed corpus of phrase-level Bible cross-references derived from the Treasury of Scripture Knowledge, with a Bible reader and connection explore
bible cross-referencestreasury of scripture knowledgebible readeropen datasetscripture
Their llms.txt
The beginning of the file, from our validated copy saved 2026-10-21T21:24:43.311Z. Cached copy · Source on crossreferences.org
# CrossReferences.org
> An open, freely licensed corpus of phrase-level Bible cross-references, derived from the Treasury of Scripture Knowledge (TSK) and re-anchored to modern translations. Each reference is attached to a specific phrase in the target translation's own wording, and multi-verse references are kept whole rather than flattened into separate verse links.
Data first. The web Bible reader and the sandbox are demonstrations of what the corpus supports, not the product. Cross-reference data is CC BY 4.0, commercial use included.
## Who it's for
Anyone building or improving Bible software who needs cross-reference data: Bible reading and study apps, sermon preparation tools, offline and low-bandwidth apps, digital Bible publishing, and research on the text's internal connections. Useful in particular where an app displays a modern translation and wants to highlight the phrase a reference belongs to, or serves French or Afrikaans readers, or must work without a network connection. No API key, no account, no usage limits — download the files and embed them.
## What makes it different
Most free TSK derivatives drop the anchors and flatten the reference groups, leaving a verse-to-verse edge list. The TSK's precision was in its anchors: a reference attaches to a phrase within a verse, not to the whole verse. This dataset keeps that, rebuilt in each translation's own words.
Genesis 1:1, English (BSB) and French (S21):
```
Gen 1 1 beginning Prov 8:22-24|Prov 16:4|Mark 13:19|John 1:1-3|Heb 1:10|1 John 1:1
Gn 1 1 commencement Pr 8:22-24|Pr 16:4|Mc 13:19|Jn 1:1-3|Hé 1:10|1 Jn 1:1
```
There is an anchor column; it is in the target translation's wording, so an app showing a modern translation can highlight it directly; and `Prov 8:22-24` is one reference, not three.
63,668 anchors. About a third of reference groups span more than one verse. No dangling references. The set is also modestly curated — references added, split, merged or removed where it serves a reader, currently well under 1%.
## Translations
| Code | Translation | Language | Text licence |
|---|---|---|---|
| KJV | King James Version | English | Public domain |
| BSB | Berean Standard Bible | English | Public domain |
| S21 | Segond 21 | French | © Société Biblique de Genève |
| AOV | Afrikaanse Ou Vertaling | Afrikaans | Public domain |
**Segond 21:** this dataset does **not** contain the Segond 21 Bible text, and contains no S21 chapter or verse numbering. It carries S21 anchor phrases only — short fragments used to locate a reference within a verse. This is a deliberate licensing boundary. A French reader built on this data needs the S21 text from its rights holder, Société Biblique de Genève.
KJV, BSB and AOV texts are included and are public domain.
## Formats
**TSV** — one file per translation: `book`, `chapter`, `verse`, `anchor`, `references` (separated by `|`).
**JSON** — `bible_books.json`, `bible_verses.json` (the text layer), `cross_references.json` (ancho
…
Related sites
Other listed sites in Documentation and reference. See the whole category →
| Domain | Title | Category | Country | Authority | llms.txt | llms-full.txt | Save |
|---|---|---|---|---|---|---|---|
| ubuntu.com | Ubuntu | documentation Open source projects Infrastructure +1 | GB | 76 | ✓ | ✓ | |
| cpanel.net | cPanel & WHM Documentation | documentation Marketing Documentation and reference +1 | US | 73 | ✓ | ||
| openai.com | OpenAI Developers | interface Education Developer tools +3 | 72 | ✓ | ✓ | ||
| nvidia.com | NVIDIA Corporation | documentation Developer tools AI and machine learning +1 | US | 71 | ✓ | ||
| gravatar.com | Gravatar API Documentation v3.0.0 – LLMS.TXT | interface APIs and SDKs Documentation and reference | US | 70 | ✓ | ||
| readthedocs.io | Your Documentation Infrastructure Layer | documentation Documentation and reference Developer tools | 70 | ✓ | ✓ | ||
| nodejs.org | Node.js Documentation | documentation Developer tools Documentation and reference +1 | 69 | ✓ | |||
| ruby-lang.org | Ruby Programming Language | documentation Developer tools Open source projects +1 | US | 69 | ✓ | ✓ |
Machine-readable: GET /v1/resolve?q=crossreferences.org · GET /v1/domain/crossreferences.org · this page as Accept: application/json or text/markdown · MCP lookup_domain
Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.
Own or manage this website?
If you own or manage crossreferences.org, you can update its listing and review file health, discovery activity and score history.
Manage this listing — optional
What verification unlocks
See how your site is discovered—and control what agents see.
- Control what agents see
Edit your listing description, tags, public contact details and additional llms.txt paths. Publish your terms for automated access, attribution and pricing.
- Make your profile eligible for search
A valid, listed, unblocked, verified profile can appear in our publisher sitemap and become eligible for search-engine visibility. Search engines decide what to index and rank.
- Appear in our llms-full.txt
Eligible verified publishers are listed by name, with their file links and summaries, in the service overview agents can read.
Free. No account registration, backlink or payment required. Public discovery remains available without verification.
Let your coding agent verify it
If your coding agent is authorized to manage this website, paste these instructions into it.
Claim my listing on Agent Web Map for crossreferences.org:
1. POST https://agentwebmap.com/v1/sites/crossreferences.org/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://crossreferences.org/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/crossreferences.org/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/crossreferences.org).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verifyCorrections or removal requests: contact the directory.