Features for compiled documentation context

Octoplexity prepares documentation before runtime so assistants, chatbots, APIs, and MCP tools receive tighter context with citations, permissions, and source provenance intact.

Four systems, one context layer.

The platform combines source intake, compilation, governance, and runtime delivery so teams do not have to stitch together separate tools for every AI surface.

SourcesUploads, web docs, support centers, API references
CompilerSource spans, claims, entities, summaries, graph edges
PolicyTenant, project, source, role, key, and MCP boundaries
RuntimeContext packets for chat, API, MCP, and internal tools

Source and compile

Source intake

Upload documents or crawl web documentation, then normalize each source into documents, versions, and source spans.

Document compiler

Compile claims, entities, summaries, relationships, and provenance before the user asks a question.

Context packets

Return compact, cited, model-ready payloads instead of loosely ranked chunks stuffed into prompts.

Govern and deliver

Permission filtering

Apply tenant, project, source, role, API key, and MCP client boundaries before context reaches a model.

API and MCP delivery

Serve compiled context to internal assistants, agent tools, website chatbots, and customer applications.

Hosted knowledge bot

Use a managed website bot surface when teams need customer-facing answers without building a custom chat UI.

Improve and verify

Feedback weighting

Use corrections, missing-source reports, and accepted answers to refine source weighting and packet assembly.

Source provenance

Keep every generated artifact tied to source spans, document versions, and freshness signals.

QuestionCan this customer use SSO and keep audit history?
Intent: policy or compliancePermission filter: support roleSources: security docs and admin guide
Context packet

SSO supports SAML 2.0 and OIDC. Audit events include member, source, key, billing, and permission changes.

[1] Security.md[2] Admin Guide

Context packets are the runtime contract.

Each packet is assembled for a request, permission scope, source version, and token budget. Downstream systems can answer with the right context instead of searching every source from scratch.

Give your AI systems a better context layer.

Bring documentation, support knowledge, sales context, and website answers into one compiled source of truth.

Request access