Some teams want the layer without the workspace around it.
Not every Bridge customer wants a control plane, an audit UI, and audience profiles. Some teams have all of that already. What they want is the routing engine — exposed cleanly, with the audit trail intact, with the SLA written down.
Bridge API is that surface. Same engine as Workspace. Same audit primitives. Same compliance posture. Different shape: one endpoint, one schema, one billing line.
The Affinity Federal Credit Union deployment is documented as a Bridge API case study. Ninety days in production, zero unsanctioned outputs, regulator-accepted audit trail at day 60.
Three steps from prompt to decision.
Single endpoint
Your application calls one Bridge API endpoint. Bridge handles model selection, context loading, and behavioral policy. Your application receives the routed response and the audit reference.
Per-call policy
Audit policy, context profile, and escalation rules pass per call. Defaults are configured per API key. The policy is enforced at routing, not by your application.
Audit reference returned
Every call returns an audit reference. Your application stores the reference. The full audit record lives in Bridge's audit storage and is queryable via the audit API.
Where Bridge API lives in production.
Product engineering teams
Teams that want the routing primitive without the surrounding workspace. They have their own application surface and their own access control.
Used by a fintech's risk-modeling team routing model calls from their proprietary application.
API-native deployments
Customers whose AI usage is programmatic and doesn't pass through a UI Brevor would build for them.
Used by a logistics company's dispatch system routing model calls 200K times daily.
Multi-product enterprises
Customers using Bridge API behind multiple applications in their organization, each calling the same Bridge deployment.
Used by an insurance carrier with API integration across claims, underwriting, and member-services systems.
Existing-stack augmentation
Customers who already have model governance, model serving, and policy documentation, and want Bridge as the runtime enforcement layer.
Used by a regional bank already running an AI policy framework and adding Bridge as the enforcement primitive.
What ships in every deployment.
One endpoint between your application and any model.
curl https://api.brevortech.com/v1/route \
-H "Authorization: Bearer $BREVOR_KEY" \
-H "Content-Type: application/json" \
-d '{
"prompt": "Generate a compliance summary for transaction #92447.",
"context_profile": "naic_finserv_v3",
"audit_policy": "ny_dfs_strict"
}'