Legal & Provenance

Compliance-focused Scripture infrastructure with verified public-domain provenance and canonical stability for production systems.

Purpose

This page documents the legal provenance, licensing posture, and stability guarantees of the BibleBridge Scripture API. It is intended to support technical due diligence, procurement review, and compliance assessment for organizations using Scripture data in production systems.

BibleBridge is designed to function as long-term infrastructure. Our goal is to minimize legal ambiguity, schema risk, and operational uncertainty for downstream users.

Textual Provenance

All Bible texts served by the BibleBridge API are sourced from verifiable public-domain editions. No proprietary, licensed, or restricted translations are included in the platform.

• Texts are selected based on established public-domain status
• Original publication dates precede modern copyright thresholds
• No derivative licensing obligations are imposed on API consumers

BibleBridge does not host or distribute copyrighted modern translations.

Canonical Structure

BibleBridge uses a fixed canonical book model with numeric identifiers from 1 to 66. This model is consistent across all supported translations and languages.

• Book IDs are stable and never reassigned
• Chapter and verse numbering follows source editions
• Schema consistency is maintained across versions

This canonical approach enables cross-translation alignment, reliable indexing, and long-lived client integrations without schema drift.

Cross-Translation Alignment

BibleBridge performs verse alignment on the server side using canonical identifiers. When multiple translations are requested, aligned verse objects are returned in a single response.

This eliminates the need for client-side joins, text matching, or heuristic alignment and reduces the risk of data inconsistency in comparison workflows.

Licensing Posture

All Scripture texts served by the BibleBridge API are public domain. Scripture data may be cached, stored, displayed, and redistributed without attribution or usage requirements.

• Cached locally
• Stored in databases
• Displayed in applications
• Used in commercial products

Version identifiers are technical selectors only and do not impose licensing obligations. BibleBridge provides technical infrastructure and does not offer legal advice.

API Stability Commitment

BibleBridge is designed to avoid breaking changes that would disrupt production systems.

• Existing endpoints are not removed without notice
• Response schemas are extended, not modified destructively
• Canonical identifiers remain stable over time

Higher access tiers may include additional stability assurances, cache prioritization, or pinned behavior.

Scope and Limitations

BibleBridge does not guarantee theological interpretation, translation accuracy, or suitability for any particular doctrinal use.

The API provides structured access to historical public-domain texts. Interpretation and application remain the responsibility of the consuming system.