How Mereon is organized

A quick tour of the things the API returns. Understanding these makes every response easier to read.

Source content

Everything starts with content: the videos, documents, and guides your organization uploads. Mereon stores the full text of documents and the transcript of videos, split into chapters so you can reference a specific section.

The content endpoints list these resources and return their text.

Topics and items

Mereon reads your source content and builds a knowledge graph out of it.

• A topic is a subject your organization knows about, such as “Expense approval” or “Onboarding a new client”. Topics belong to a category and can relate to other topics.
• An item is a specific piece of knowledge under a topic: a process (how something is done), a policy (a rule), or a fact. Items can nest, so a process can have sub-steps.

The topics and items endpoints walk this structure.

Evidence

Every item is backed by evidence: the exact place in a source document or video that the knowledge came from. Evidence carries the quote, the character range or video timestamps, and a confidence score, plus a link to the original content. This is how an AI tool can cite its sources rather than assert things.

Duties (ownership)

Mereon tracks who is Responsible, Accountable, Consulted, or Informed for an area of the business (the RACI model). Duties can be assigned directly to a topic or inherited from a parent area like a space or category. The duties endpoint answers “who owns this”.

Issues

As the knowledge base grows, Mereon flags issues: conflicts between documents, duplicates, stale content, structure gaps, and misclassifications. The issues endpoint lets you pull these so a tool or dashboard can surface what needs attention.

Lessons

A lesson is an authored training unit built on top of your content. Lessons are distinct from the raw source files: a lesson teaches a sequence of content pieces. The lessons endpoints list the catalog and return what each lesson is built from.

Deep links

Every entity the API returns carries a url field that links straight to it in the Mereon app. Use these so people (and tools) can jump from an API result to the real thing.