Knowledge

An App can act as a knowledge provider — supplying documents that SAALT embeds into an Agent's Knowledge base. To enable this, declare hasKnowledgeProvider: true in /meta and implement two routes: /knowledge/listDocuments and /knowledge/getDocument.

/knowledge/listDocuments

Returns the list of documents the App wants to sync. SAALT compares this list against the previous response and enqueues new or changed documents for embedding.

Code
 
[
  {
    "id": "string",
    "name": "string",
    "lastUpdated": "string"
  }
]

• id — a stable identifier that uniquely identifies the document in your system.
• name — the display name shown in the Knowledge base.
• lastUpdated — timestamp of the document's last change; used to detect updates since the previous sync.

/knowledge/getDocument

Returns the full content of a single document. SAALT embeds the content and adds it to the vector store.

Code
 
{
  "id": "string",
  "name": "string",
  "content": "string",
  "updatedAt": "string",
  "metadata": {}
}

• id — the document identifier.
• name — the document name.
• content — plain-text content of the document.
• updatedAt — timestamp of the last content update.
• metadata — additional metadata as a JSON object.

Next steps

• Architecture — where the /knowledge/* routes fit among an App's required routes.
• Bridge — the SDK surface, including files.parseFile.
• Knowledge (user guide) — how end users see and manage documents.