Cblindspot and FluidityIQ put AI-native patent research inside the IP workflow

FluidityIQ is the first vendor live on the Cblindspot connector catalog. Its semantic patent engine, already MCP-native and reachable from Claude, Microsoft Copilot and ChatGPT, now reaches IP teams inside the workflow itself, through the Cblindspot connector and Chrome extension.

29 May 2026, Cblindspot and FluidityIQ have signed a technology partnership that connects the FluidityIQ patent research engine into the Cblindspot workflow platform. Enterprise IP teams using Cblindspot can now run a FluidityIQ search from inside a workflow step, a prior art search, for example, without leaving the platform or switching between systems.

The FluidityIQ engine is already MCP-native and exposed to Claude, Microsoft Copilot and ChatGPT. This partnership adds Cblindspot as a new surface: the one built for IP work. The connector reaches FluidityIQ over MCP or over its API depending on the client environment, and a query that starts inside a Cblindspot workflow returns results in context.

Cblindspot also brings connected platforms into the work a team already does. A Chrome extension, paired with Office add-ins that share the same context, surfaces the right capability at the right step inside the browser, so a researcher reaches FluidityIQ without leaving their flow. The same layer measures each step, including time spent and completion, and feeds the Cblindspot operations dashboard.

What this means for the catalog

Cblindspot runs a vendor-neutral connector catalog. At each step of an IP workflow, the platform helps a team decide whether to buy, build or keep a given platform, then lets them plug the chosen one straight in. FluidityIQ is the first vendor in that catalog and anchors the first wave of integrations. The partnership is a working proof that several AI-native vendors can run side by side inside one workflow environment, with the IP team choosing what fits each step.

The agreement is not exclusive. Both companies remain free to work with other partners.

With thanks to Jeff Roy and the FluidityIQ team for going first.