The Opine Knowledge Base is now an open platform

With this release, your internal sales wiki evolves from a static document store, to a constantly evolving knowledge layer for your entire GTM team

The Opine Knowledge Base is now live and it’s where playbooks, messaging, and competitive intel live. Storing knowledge isn’t the hard part - getting the right version into a live deal is. Today, we’re turning the KB into an open product knowledge layer for your GTM stack with a daily auto-refresh for web sources, support for bringing your own MCP server, and a public REST API.

Why product knowledge base matters to sales teams

For sales teams, a knowledge base is useful only when product knowledge and sales process knowledge come together in the workflows they already run every day: status of deal, meeting prep, follow-ups, and handoff documents. A great product knowledge base should do three things for GTM and CX:

• Make knowledge trustworthy: Content is synced from the real system of record, auto-refreshed, and easy to maintain. That builds internal confidence and reduces shadow documentation.
• Make knowledge fast to find: Search needs to work from wherever work actually happens - CRM, email, IDE, agent, or chat, without context switching.
• Make knowledge reusable: APIs and MCP integration mean you can start embedding product knowledge into workflows: guided discovery, AI-assisted call prep, auto-generated follow-ups, and consistent messaging across channels.

Why product knowledge bases fail (and why that matters)

Strong product knowledge is directly tied to higher win rates, faster onboarding, and more confident customer conversations. The cost of a weak product knowledge base is significant: deals stall because an SE can’t find the right answer, AEs share outdated pricing, and marketing’s carefully crafted positioning never makes it into live conversations. In reality, most KBs break in a few ways:

1. Content goes stale or missing: Competitive tear-downs live in a Confluence space only PMM remembers. SEs create personal playbooks and then search there instead of in the system everyone is supposed to use. Pricing and packaging get updated in Notion but never make it into your sales enablement tool.
2. The KB is trapped in one UI: Even when content is current, it’s only available if you’re willing to stop what you’re doing, open the vendor’s app, and run a search. If you live in Claude Desktop, Cursor, your IDE, or a custom agent, that might as well be a brick wall.
3. Information has to be retrieved: Users have to remember where the information that they need exists and track it down, delaying responses and potentially missing important context.

The end result: reps rely on memory, screenshots, and Slack DMs. Product knowledge exists but is not a real, trustworthy system.

How Opine’s new release overcomes that problem

We’ve been building toward a different model: your product knowledge base as an API-first, agent-friendly layer that everything else can plug into.

Opine’s Knowledge Base integrates with other AI-forward features - information to customers when they need it immediately and summarizes in a way that helps them pitch the particular product/feature to the customer and auto-populates product knowledge into meeting prep and summaries. 

Not just that, it helps customers enrich AI-powered interactions. Web-sourced KB articles now auto-refresh on a daily cycle. Opine revisits the source URL, detects whether the content has changed, and re-embeds the page if it has. Your pricing page, integration docs, and competitor positioning stay current without anyone manually re-importing them.

1. Public REST API for the KB

The new public API exposes  endpoints that cover: item CRUD, hybrid semantic + keyword search, file upload, and label management. Authentication uses scoped API keys (read or write) That means RevOps, sales engineering, or a technically inclined PMM can now:

• Script nightly or hourly syncs from Notion, Confluence, or any internal system.
• Keep product docs, objection-handling docs, competitive battlecards, and pricing pages in lockstep with the source of truth, instead of manually copy-pasting.
• Pipe content into Opine from internal tools you don’t want to give sellers direct access to, while still making the knowledge available in-context.

2. Auto-refresh for web-based content

For KB items that come from URLs (product docs, pricing docs, competitor pages), Opine now revisits the source daily. If the page has changed, we re-ingest and re-embed it automatically.

So when PMM updates the pricing page or adds a new Why we win vs X section to your docs, your sellers see the latest version in Opine without anyone remembering to re-import it. Your product knowledge base stays live and self-corrects instead of drifting out of date.

3. New MCP tools for agents and IDEs

To augment this release we’ve added new MCP tools: Combined with the API, these make your KB fully reachable from Claude Desktop, Cursor, or any agent that speaks MCP.

In practice, this looks like:

• Teams can chat using MCP tools or the in-app chat features and create new knowledge base features or documents.
• An SE types a natural-language question in their IDE or Claude: “Which recently released features are prospects finding the most compelling? What should I know about each of these features?”
• The agent calls Opine’s MCP tools, pulls back the relevant playbook sections, and surfaces an answer without forcing the SE to switch to another application. 

Your product knowledge base stops being “yet another tab” and becomes something every tool can query. 

Opine’s Knowledge Base started as a place to store playbooks. With this release, it becomes a product knowledge platform your tools, agents, and humans can all tap into.

If you want to go deeper into the API details, the docs are here:  Opine Knowledge base API documentation.

If you’re interested in learning more, reach out to support@tryopine.com and we’ll get you set up.