Why documentation is provisioned, not public.
Bridge deployments are configured per customer environment. The API endpoints, the active context modules, the audit-policy schema, and the SDK versions all vary by deployment. Public documentation for a generic Bridge product would not be accurate for any specific deployment.
Each customer environment ships with its own documentation portal. The portal contains the API reference resolved against that deployment's configuration, integration guides for the customer's exact stack, and operational runbooks tied to the deployment's SLA tier.
Sales scopes documentation access at deployment kickoff. Engineering teams receive credentials before the integration call. The portal is maintained continuously and reflects the live deployment configuration.
Three documentation surfaces per deployment.
Getting started
Integration-first guide for engineering teams onboarding a new Bridge deployment. Scoped to the deployment's stack and identity provider.
- →Quickstart for the deployment's SDK
- →SSO and identity-provider setup
- →First behavioral routing call
- →Audit trail integration
API reference
Full API reference resolved against the deployment's configuration. Endpoints, schemas, error codes, and rate limits.
- →REST and gRPC endpoint catalog
- →Schema reference per Bridge product
- →Error codes and retry policy
- →Rate limits and SLA tier details
Integration guides
Patterns and tutorials for common integration shapes: EHR-side, banking-platform, multi-model routing, single-tenant deployment.
- →EHR integration patterns (Epic, Cerner, Meditech)
- →Banking and credit-union deployment patterns
- →Multi-model provider routing
- →Single-tenant and air-gapped deployment
Documentation access.
Documentation is provisioned with deployment kickoff. Engineering teams receive credentials before the integration call. Scope a deployment to receive access.
Talk to sales →