BibleBridge — Production-Grade Bible API

Powered by the Canonical Reference Resolution Engine — a deterministic system that converts complex Scripture input into validated canonical identifiers.

A deterministic Bible API with public-domain KJV access, stable schemas, and OSIS-compatible canonical identifiers.

Designed for production applications that require licensing clarity, canonical stability, and predictable Scripture access.

Licensing-Safe Verified public-domain Scripture with no attribution or link-back requirements. Suitable for commercial, institutional, and ministry use. Legal & Provenance
Example API request
curl --get https://holybible.dev/api/scripture \
  --data bookID=43 \
  --data chapter=3 \
  --data range=16-16 \
  --data version=DRA \
  --data compare=WEB
{
  "type": "comparison_range",
  "primary_version": "DRA",
  "compare_version": "WEB",
  "book": {
    "id": 43,
    "name": "John"
  },
  "chapter": 3,
  "range": "16-16",
  "data": [
    {
      "verse": 16,
      "DRA": "For God so loved the world, as to give his only begotten Son...",
      "WEB": "For God so loved the world, that he gave his one and only Son..."
    }
  ]
}
Response truncated for brevity. Some metadata fields have been omitted.
Canonical identifiers and response shape are stable by design.
Canonical Reference Resolution Engine
curl --get https://holybible.dev/api/resolve \
  --data-urlencode "reference=rom 8:1-4, 28; 12:1-2"
{
  "type": "collection",
  "valid": true,
  "confidence": 0.98,
  "osis_id": "Rom.8.1-4,Rom.8.28,Rom.12.1-2",
  "references": [
    {
      "book_id": 45,
      "chapter": 8,
      "verses": [ 1, 2, 3, 4 ]
    },
    {
      "book_id": 45,
      "chapter": 8,
      "verses": [ 28 ]
    },
    {
      "book_id": 45,
      "chapter": 12,
      "verses": [ 1, 2 ]
    }
  ]
}
Messy human input becomes deterministic canonical coordinates — with optional OSIS interoperability.
Designed for production systems that require structural validation and immutable reference structure.

Translation-agnostic by design.
The Resolution Engine separates reference logic from text storage. Natural-language input is converted into canonical coordinates and standards-compliant OSIS identifiers. These outputs integrate directly with any structured Bible dataset — including proprietary translations licensed by your organization — without changing application logic.