We already have a help center and a wiki. Why this?

Keep them. A wiki holds everything, including drafts and stale pages, and an AI reading it cannot tell which is which. Curated Data holds the smaller set of answers you must get right: policies, pricing, terms. Each one has a named owner and an approval step, and it is what your AI answers from.

What happens when a policy changes?

The edit becomes a draft while the current approved version keeps answering. Once the new version is signed off, every assistant you connect answers from it on the next question. Earlier versions stay in the history.

Can a customer-facing bot see internal-only guidance?

No. Every connection gets its own scoped key and only retrieves what it is cleared to read. Reps can see the internal playbook while the customer-facing bot only sees customer-safe answers.

Do we need engineers to set this up?

Not for the day-to-day. Writing and approving answers works like a shared doc with an approve button. Connecting an assistant is a one-time step for your IT team: one config block and a scoped key, with nothing to host.

Which AI tools does it work with?

Anything that speaks MCP, including Claude Desktop, Claude Code, Cursor, Windsurf, VS Code, and the OpenAI Agents SDK. There is also a REST API for tools that are not MCP native.

What happens if we switch AI vendors later?

Your knowledge layer carries over. MCP and REST are provider-neutral surfaces, so a new assistant connects with a new scoped key and reads the same approved answers — no migration, no re-approval. Underneath, every answer is a plain markdown document in an open format, not a proprietary store. The approval work your team does here outlives any one AI vendor choice.

How does it stay current after the initial import?

Two ways. Your team edits and re-approves answers as policies change — the usual path. And the assistants themselves help: the MCP connection instructs them to check the approved knowledge first and, when they hit a question it cannot answer, to file the missing fact as a suggestion. Suggestions land in your review queue as drafts. Your team approves before anything is served — agents propose, people decide.

How do we know an answer is current, and who approved it?

Every answer traces back to a specific approved version that records its author, reviewer, and approval time. Approvals and rejections land in an audit log you can hand to a security review.

For customer success, deal desk, and support teams

The answer your company approved.Not the AI's best guess.

Curated Data is where your team keeps the approved version of your policies, pricing, and terms. Every AI assistant you connect answers from it. When something changes, update it once and every answer follows.

Start free Try the guided demo

Free tier · no credit card · no infrastructure to run

Your workspace

Folders
- Policies
  14 pages
- Pricing
  9 pages
- Plans & entitlements
  6 pages
- Support playbooks
  11 pages
Recently approved
- Refund policy
  policies/refunds
  PublishedOct 3
- Discount matrix
  pricing/discount-matrix
  PublishedSep 28
- Plan entitlements
  plans/entitlements
  In reviewSep 19

Policies, pricing, and terms filed in one place, each page approved by a named owner.

Approved by your team
Every change tracked
Internal and customer-facing kept separate
Your knowledge stays portable

Your AI is already answering for your company. Make sure it answers correctly.

An AI without your company's knowledge fills the gaps with whatever it learned from the internet, and it does so confidently. That is how a help bot quotes a refund window you never offered, or a rep repeats last quarter's discount floor.

Curated Data gives every assistant one approved answer, written in your team's words, signed off by the owner you chose, and traceable when someone asks where it came from.

Sample

An AI on its ownno sources connected

A customer bought an annual plan 45 days ago and wants a refund. What do I tell them?

Annual plans almost always come with a 60-day refund window, so you are safe to approve this one in full.

no source · a guess

The same AI + Curated Dataconnected: curated-data (MCP)

A customer bought an annual plan 45 days ago and wants a refund. What do I tell them?

Found the approved policy.

The refund window is 30 days, so at day 45 this one misses it. Offer prorated account credit instead. That needs manager approval.

verified · policies/refunds · v7 · approved

Same question. The difference is whether the answer came from knowledge your team approved, or from a guess. Grounding will not make an AI perfect, but it shrinks the room for guessing and makes every answer traceable to a source you approved.

Built for the teams who answer for the company

You own the refund policy, the discount matrix, and the support playbook. Curated Data keeps them current and approved, so every AI you connect answers from the same source.

Heads of Customer Success

Every CSM quotes the renewal terms you approved.

Your CSMs ask an AI before they ask you. Keep playbooks, entitlements, and renewal policies approved and current, so every answer matches the one you would give.

See how it answers

Deal Desk & RevOps

Stop quoting last quarter's discount floor.

A quote built on last quarter's terms costs real money. Keep discount thresholds, payment terms, and approval rules in one approved source your sales assistants quote from.

See how it answers

Customer Service

Reps and your help bot give the same approved answer.

One policy, two audiences. Reps get the internal guidance, your help bot gets the customer-safe answer, and both stay current when the policy changes.

See how it answers

Your AI assistant

answering from approved knowledge

Asked

Can I refund an annual plan 45 days after purchase?

The approved answer

Refunds are available within 30 days of purchase. After 30 days, offer prorated account credit with manager approval.

Grounded in knowledge your team approved

source: policies/refundsapproved by CS leadership

Same question your team fields every day, answered from the version a named person approved.

Write it down once. Approve it. Every assistant uses it.

Three steps take an answer from a page someone on your team wrote to something every AI you connect can cite: Write, Approve, Serve, plus the Audit trail they leave.

Write it down once, in your team’s words

Every policy, definition, and product detail gets one page with a named owner, an approval status, tags, and links to related answers. This is the saved page as your team sees it.

pricing/discount-matrix.md

Approved

Ownerrevops

Typepolicy

Tagspricingcustomer-facingdiscounts

Discount matrix

For a 2-year agreement, offer up to 15% without approval. Discounts from 16 to 25% need deal desk approval. Above 25% goes to the CRO.

Quick rules

Up to 15%no approval required
16 to 25%deal desk approval required
Above 25%CRO sign-off required

Linked pagesdeal desk approvalpayment termsentitlements

Pages link together, so related answers stay connected
Plain, portable documents underneath. Never locked in.

The approved answer, wherever your team uses AI

Assistants connect with a scoped key and get back the current approved version, limited to what that connection is cleared to read.

key: help-center-botreads: customer-safe only

MCP · search_knowledge

→ search_knowledge("What is the max discount on a 2-year agreement?")

{
  "path": "pricing/discount-matrix",
  "revision": 12,
  "status": "approved",
  "body": "Up to 15% without approval…"
}

# drafts and in-review versions are never returned

Hosted for you: nothing to run or scale
Customer-facing tools only see what they are cleared to share

Works with any MCP client

Claude Desktop
Claude Code
Cursor
Windsurf
VS Code
OpenAI Agents SDK
plus REST for everything else

Send your IT team the docs →

Answers you can defend to a customer, a boss, or an auditor

Every answer your AI gives traces back to a version a named person approved: recorded, versioned, and scoped. The controls your security team will ask about are built in.

Built on the Open Knowledge Format standard

A named person signs off before anything is served.

A named person approved every answer
Nothing unreviewed is ever served. Each change is signed off and recorded in the audit log.
Customer-facing stays customer-safe
Each connection has its own scoped key and only sees what it is cleared to share. Internal guidance stays internal.
Every version kept
Every page records its versions, author, reviewer, and approval time.
Isolated per workspace
Every workspace is its own tenant. One company's knowledge never crosses into another.
Security review & DPA
Available on request for Enterprise.
OIDC SSO is available on Enterprise. SAML and SCIM are on the roadmap.
No lock-in
Plain, portable documents underneath, built on the Open Knowledge Format standard. Your knowledge stays yours.

Automatic organization

AI routing, duplicate prevention, balanced folders, and a curated OKF bundle report

Roll out at your pace: Shadow → Suggest → Auto.

Shadow
Decisions are recorded only. Nothing moves.
Suggest
Decisions are shown to reviewers to accept.
Auto
Confident decisions are applied within your confidence threshold and daily AI spending cap.

Publishing always stays human-approved. Automatic organization files and tidies drafts; a named person still approves every page before it is served.

Nothing leaves until an admin opts in. Content and folder metadata go to an outside AI provider only after a workspace admin turns the setting on and acknowledges the notice. Off sends nothing.

Available on paid plans. Compare plans →

Start free. Grow when your team does.

Every plan includes the full write, approve, publish workflow and works with every assistant you connect. Higher tiers lift caps and add controls.

Compare plans →

Free

$0forever

For a single team getting started.

Up to 200 answer pages
5 members
MCP + REST access

Start free

For production

Team

$99/mo

For teams putting approved answers behind AI in production.

Up to 5,000 answer pages
25 members
100,000 API requests / day
Automatic organization

Choose Team

Enterprise

Custom

For scale, security review, and dedicated support through sales.

Expanded member limits
Custom rate limits & SLAs
Security review & DPA

Talk to sales

Before you rely on an AI for answers

The questions to ask first

Curated Data is deliberately narrower than a wiki or an enterprise search tool. These are the boundaries and controls that make it dependable.

Explore examples →Read the full docs →

Give your AI the approved answers

Create a workspace, approve the answers your AI needs, and connect it. No credit card.

Create your workspace Try the guided demo →

The answer your company approved.Not the AI's best guess.

Your AI is already answering for your company. Make sure it answers correctly.

Built for the teams who answer for the company

Heads of Customer Success

Deal Desk & RevOps

Customer Service

Write it down once. Approve it. Every assistant uses it.

Write it down once, in your team’s words

Someone you trust signs off before any AI uses it

The approved answer, wherever your team uses AI

Every change on the record

Answers you can defend to a customer, a boss, or an auditor

A named person approved every answer

Customer-facing stays customer-safe

Every version kept

Isolated per workspace

Security review & DPA

No lock-in

Automatic organization

Shadow

Suggest

Auto

Start free. Grow when your team does.

Free

Team

Enterprise

The questions to ask first

Give your AI the approved answers

Opening Curated Data