Skip to content

Bookend Platform documentation

Bookend proves that the executed closing package matches the credit approval, then stages boarding and funding for your own maker-checker approval. It runs inside your network, with an evidence packet for every loan.

Bookend sits after document generation and before boarding. It reads the executed commercial loan package, reconciles every variable term against the approval with deterministic rules, verifies signatures, initials and notary blocks, and stages the core boarding record and the wire request for a second person to approve. It is built for Jack Henry banks first, and it never transmits a wire.

Administration

Settings, users and roles, LAR profiles, core field maps, teaching documents, metering, air-gapped operations, upgrades, backup and restore, incidents.

Reconciliation rules

One page per rule: what it checks, how it decides, and the tolerances you control. The same pages the product serves at GET /v1/rules/{id}/doc.

Integrations

The REST API (OpenAPI, versioned per release), the MCP server for assistants and automation, and the core adapters for jXchange and file export.

These docs are published as /llms.txt and /llms-full.txt so an assistant can read them directly. They contain no customer names or loan data.