veriomProvider and private model routing
Govern Luna, Terra, and Sol model assignments across approved LLMGateway routes and encrypted private endpoints.
Veriom separates model choice from evidence access and action authority. A selected route does not expand the evidence a role can retrieve or the actions it can perform.
Workspace choices
Where enabled, workspace Owners and Admins choose from the approved model options available to their workspace. They can set a reasoning budget and decide whether an unavailable private endpoint may fall back to the platform route.
The workspace interface shows the available options and applicable usage information. Model availability does not grant permission to publish a change.
Private endpoints
A private endpoint requires an approved connection and a compatible request format. Follow the workspace setup guidance and API contract for the required configuration. Credentials are write-only and are never returned by the API.
If fallback is disabled, an unavailable or invalid private route fails closed. When fallback is explicitly enabled, the run records that route decision.
Review and history
Routing changes are versioned inside workspace policy. A private route must reference an active endpoint and an allowed model. Endpoint creation, credential rotation, activation changes, and routing-policy updates create audit events.
Every review keeps its evidence scope and human approval requirements. Contact Veriom to discuss model availability, processing terms, or a private-endpoint requirement.
Was this guide useful?
Your response stays in this browser unless you open a GitHub issue.Organizational discovery
Add accountable business context, organize evidence sources, resolve contradictions, and publish a versioned context snapshot.
Reports and remediation
Canonical report JSON, approval, deterministic exports, patch proposals, static rescans, and human-controlled GitHub pull requests.