BYOK and private endpoints
Keep provider contracts and credentials while adding MC-1 intelligence and control.
Define which intelligence may run, where data may flow, what requests may cost, who may act, and how every execution is audited.
Security and sovereignty constraints define the eligible route set before cost, quality, or latency optimization begins.
Keep provider contracts and credentials while adding MC-1 intelligence and control.
Constrain models, providers, locations, and data flows to approved boundaries.
Bind agent permissions, trust attributes, and expiration to consequential requests.
Apply project and organization limits while retaining underlying cost visibility.
Record policy, route, usage, evaluation, and escalation evidence.
Scope support, integration, retention, and deployment requirements contractually.
No certification or authorization status is implied; deployment claims are scoped to the contracted environment.