BIND Playground

Business Insurance Normalized Data

Explore the open data standard for commercial insurance. Browse terminology, build resources, and assemble Bundles — all derived from the published JSON schemas.

Key Concepts

Resources

The building blocks of BIND. Each resource — Submission, Policy, Claim, Insured, Coverage, and more — has a typed schema with a resourceType discriminator, a logical id, and metadata.

Coding & Terminology

Instead of free-text fields, BIND uses coded values from 280+ standardized code systems — lines of business, coverage types, peril codes, and more.

References

Resources don't exist in isolation. A Submission references an Insured, a Policy references its Coverages, a Claim references a Policy. These typed references create a connected graph.

Bundles

A Bundle is the container for exchanging BIND data. It packages related resources into a single payload — a complete submission, a policy snapshot, or any set of related resources.

What this playground does

The Resource Builder lets you create spec-compliant BIND resources by filling out forms that mirror the standard's schemas. As you add resources they accumulate in a Bundle — the same structure a real system would produce when packaging a submission, quoting a risk, or transmitting policy data. You can inspect the resulting JSON, copy it, or download it.

Terminology Browser

Search and browse 280+ insurance code systems from the BIND terminology server. Look up codes for lines of business, coverage forms, peril types, and more.

Browse Codes

Resource Builder

Create BIND resources using forms auto-generated from the standard's JSON schemas. Every field, enum, and nested structure comes straight from the spec.

Build Resources

Bundle Viewer

Inspect the assembled Bundle as JSON. Copy it to your clipboard or download it — the output is a valid BIND Bundle ready for any system that speaks the standard.

View Bundle

Exchange

Sign your bundle with ES256 keys, encrypt it with AES-256-GCM, and send it via the BIND Exchange. Recipients get a passcode and a bindx:// link to retrieve and decrypt.

Sign & Send