Your own model keys and Mint Guard per connector
Run every model call through your own keys
When every agent and laptop calls models with its own key, nobody can see the spend or control which models are used. The LLM Gateway routes your agents' model calls through your own provider credentials, so prompts and responses stay on infrastructure you control and every call lands in one audit trail.
Set a monthly budget per policy or per user, then track spend against it in a usage dashboard that breaks down by person and model. Reuse the Claude subscription seats you already pay for instead of buying separate API keys, and constrain which models a policy can use. It is in early access; email founders@mintive.com and we will turn it on for your org.
Docs: LLM Gateway, Budgets
Set guardrails per connector, not just per org
One org-wide guardrail setting forces a trade-off: strict enough for risky connectors is too strict for safe ones. Mint Guard enforcement used to be a single setting for the whole organization. Now you can override it per connector from the Mint Guard page, setting request and response handling to Inherit, Off, Monitoring, or Enforcing for each one.
Every connector page shows its effective Mint Guard state, so you can tell at a glance whether a connector is being watched or blocked.
Docs: Mint Guard, Choosing guardrails
Also in this release
Link your Slack account yourself
A new tab in Account Settings lets each person link their Slack identity through a quick OAuth check.
Readable names in SIEM exports
MCP activity exported to your SIEM now carries gateway and endpoint names alongside the existing IDs.