Changelog

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

Run your agents on Mintive

Connect your agents, tools and models through one gateway, and see every call in the log.

No sales call needed!