bridge.axiomlens.com
AXIOM Bridge
A governed chat workbench for AXIOM API users. Bridge lets a team test prompts, choose a model lane, inspect the provider handoff, and read the axiom_governance verdict before wiring the same call into production.
Bridge Workbench
Judgment lane · governed response
oracle:judgmentModel substrate
vercel/openai/gpt-5.4Governance
warn · grounding · quality
Public host
bridge.axiomlens.comThe branded control surface for governed model choice.
Runtime authority
api.axiomlens.comThe kernel still owns governance, auth, refusals, and output metadata.
Model handoff
vercel/<provider>/<model>AXIOM strips the bridge prefix before forwarding through Vercel AI Gateway.
Governed lanes
Lanes are AXIOM-native handles. They map to model substrates behind the kernel, and can change without forcing callers to rewrite their application code.
Fast
oracle:throughput
vercel/anthropic/claude-sonnet-4.6Low-latency generation with governance still attached.
Judgment
oracle:judgment
vercel/openai/gpt-5.4Higher-reasoning calls where output quality matters more than cost.
Validation
validator:judgment
vercel/anthropic/claude-opus-4.6Second-pass checks, refusal review, and higher-stakes verification.
Boundary
Bridge is not a raw model proxy. It is a policy surface over kernel-governed requests.
App request -> AXIOM operator/tier/domain headers -> AXIOM Kernel governance -> Vercel AI Gateway substrate -> AXIOM output governance -> axiom_governance returned