Mintive Raises $7M for Enterprise AI Agent Governance

Changing an AI model leaves an enterprise with a continuing set of responsibilities: who may reach its systems, what the software can do there, and which team answers for the result. Mintive is selling infrastructure around those responsibilities, giving IT and security a common place to manage tools, model access and agent identities as the applications above them change.

The San Francisco Bay Area company, formerly MintMCP, announced a $7M round led by Cowboy Ventures on October 29, 2026, taking cumulative funding to $11M. Operator Collective and Burst Capital joined as new investors, while Coatue, Hustle Fund and Maven Ventures participated again. The financing puts capital behind an administrative problem that becomes more consequential as agents receive access to working business systems.

Mintive's approach also creates a purchasing question. An enterprise adopting several agents needs a way to keep its permissions, ownership and spending decisions coherent across them. Buying that common infrastructure means deciding how much authority a separate supplier should hold over the connections carrying useful work.

What Mintive's $7M financing supports

Mintive's current platform combines an MCP gateway, an LLM gateway, agent identities, monitoring and coworker agents. The company describes the broader ambition as infrastructure for enterprises using agents, with governance outside the individual model. TechCrunch described the financing as a seed round.

The founder roster is broader than a CEO and CTO. Mintive's official media kit names CEO Jiquan Ngiam, Vijay Vasudevan, Bozhi See and Phillip Bensaid as co-founders. Vasudevan identifies himself as CTO on his own profile, a role also listed by Cowboy Ventures. Together, they are building a business whose product sits close to the access decisions an enterprise has to maintain after a pilot becomes routine work.

The official announcement reports the latest round and cumulative capital separately. It does not disclose a valuation or itemized spending plan, and the primary materials use dollar amounts without explicitly stating the denomination. Mintive's hiring page currently lists founding sales and growth marketing roles, giving a concrete indication of the commercial organization taking shape around the product. Selling shared infrastructure requires understanding the people who approve access as well as the people eager to use it.

The permission decision travels beyond the model

Mintive's Agent Identities product assigns an agent a distinct identity while delegating connections from the requesting user, a team credential or a provisioned service account. Administrators can restrict individual tools and revoke an agent's access. The company also describes shared administration and ownership transfer, allowing an agent to continue operating when the employee who configured it changes roles or leaves.

That design makes the organizational chart relevant to agent operations. An employee's departure should trigger a deliberate decision about the work an agent continues to perform, the credentials it uses and the person responsible for supervising it. Putting those decisions in a managed identity gives IT an administrative object it can change, rather than leaving ownership embedded in somebody's original setup.

The MCP gateway centralizes approved servers and groups tools by role. Mintive's LLM gateway covers another part of the assignment: which models a team may call, how much it may spend and where its usage appears. These are product descriptions, rather than an independent assessment of security effectiveness. Their commercial logic is understandable: the enterprise wants room to change models while keeping a recognizable policy for the work passing through them.

Customer evidence puts the controls to work

Modern Treasury offers a useful account of how those connections become operational. In its July 24 engineering article, the payments company describes a bank-operations agent built using MintMCP Coworker agents and governed tool access. The agent investigates questions across documentation, code, production data and error information before people decide how to respond.

A support specialist facing a bank-integration question needs evidence from systems that describe different parts of reality. Documentation can explain intended behavior; code and production data can show what has actually shipped. Giving software access to those sources creates value only when its assignment respects those differences and leaves a person responsible for the outward answer.

Modern Treasury reports saving technical account managers 30 minutes to 4 hours per case. Those are customer-reported results from a specific workflow, with human approval retained for customer-facing actions. Mintive's separately published customer account describes deployment in under 3 weeks, a vendor-published implementation detail rather than a universal deployment promise.

Mintive itself reports more than 50 paying customers and over 2.5M agent calls daily. The figures describe the company's stated operating scale; they do not disclose revenue or retention. The stronger buying evidence is the specificity of the work: multiple information sources, a defined support assignment and an explicit person who remains responsible for what reaches the customer.

An infrastructure sale with an expanding assignment

Mintive's pricing page describes custom quotes, per-user licensing and platform fees that scale with usage and team size. That structure links the commercial relationship to the spread of agent work inside a customer. The buyer has to evaluate both the usefulness of the work and the administrative effort required to keep access current as more teams participate.

For Mintive, each additional connector can deepen the relationship with IT while adding another system whose permissions and behavior must be understood. The same position that makes a gateway convenient gives its supplier a demanding place in the customer's operations. Model flexibility, credential management and customer support become parts of one continuing service relationship.

Cowboy Ventures and the participating investors are financing that assignment at a company already describing live customer deployments. As Mintive's founders build the sales organization, the conversation will move through the people who own budgets, approve tools and inherit agents from colleagues. Those people will keep making access decisions long after the first successful answer appears on a screen.