Knowledge API

Knowledge is what a project teaches Subscriby Copilot beyond what Subscriby already knows about it: questions with their answers, and guides, each cut into passages the Copilot is handed when a question matches. An entry marked for members lets the Copilot answer a member from it, in the inbox, the project bot and the chat on the portal page; an entry kept to the team serves the suggested reply in the inbox and, next, the panel and the platform bot. The dashboard page is Knowledge, the last entry of a project's menu.

These routes take the project in the path and need the project-knowledge:* abilities: view-any for the list, view for one entry, create, update and delete for the writes. A document arrives as text over the API, where the dashboard also takes a .txt, .md or .markdown file; the Copilot reads the same passages either way. A PDF is not read yet on either.

The text rides on one entry, never on the list. GET …/knowledge answers every entry without its body; GET …/knowledge/{entry} and every write answer the entry with it, because a document's text can run to 50,000 characters and a project may hold 200 entries.

EndpointsCopy Anchor Link

Related

KnowledgeWhat to teach, how an entry is read, the two audiences.Copilot in Your InboxWhere the answers come out.knowledge.* eventsknowledge.created, knowledge.updated and knowledge.deleted.Ability CatalogThe five abilities.