Knowledge bases and vector_store
The product name in the dashboard is knowledge base. The public API uses OpenAI’s resource name, vector_store, so existing OpenAI clients keep working if you change the base URL and API key.
A vector store id is the knowledge base id. Creating a vector store creates a knowledge base. Searching a vector store searches that knowledge base. There is no separate vector-store product.
Add documents
Upload a file with multipart form data, or attach a document that is already in the knowledge base by id. Send eitherfile or file_id, not both.
Supported uploads include PDF, Office documents (.doc, .docx, .ppt, .pptx, .xls, .xlsx), text and markup (.txt, .md, .html, .csv, .tsv, .json), and common source files such as .py and .ts. Each file can be up to 512 MB.
status is in_progress while the file is being parsed, then completed or failed. Poll retrieve until it finishes, then read the parsed text:
Connected sources
From the knowledge base page you can connect:- Google Drive
- OneDrive and SharePoint
- Dropbox
- Notion
- Amazon S3
Search
query may be a string or a list of strings. Optional filters follow the OpenAI comparison and compound filter shape (eq, ne, gt, gte, lt, lte, in, nin, and, or). ranking_options.score_threshold drops hits below that score. max_num_results is between 1 and 50 (default 10).
Each hit includes file_id, filename, score, attributes, and content (text chunks).
API reference
All routes are onhttps://api.synapsai.cloud and use your API key.
List endpoints return an OpenAI-style page:
object, data, first_id, last_id, and has_more. limit is 1–100 (default 20). order is asc or desc.
Your API key needs vector-store permissions. A key scoped to a single knowledge base can upload files to that knowledge base only.
Python SDK
pip install --upgrade synapsai-python. client.vector_stores and client.vector_stores.files call https://api.synapsai.cloud/v1. They create, list, update, delete, and search knowledge bases, and upload or attach files. The SDK uses the name vector_store because the HTTP API does.
upload_paths walks directories recursively. AsyncSynapsAI has the same methods. The CLI uploads files with synapsai upload-vector-store-files.
Use a knowledge base from other products
- Agents. Assign one or more knowledge bases when you deploy an agent. The agent can search them and load a full document. Those tools are attached automatically; you do not add them to the tool list.
- MCP. SynapsAI runs an MCP server mounted at
/mcp. SendAuthorization: Bearerwith your API key. The tools aresearch_knowledge_base(kb_id,query) andretrieve_knowledge_base_content(kb_id,document_id).document_idis the file id returned by search.
Deleting a knowledge base fails if an agent still references it. Remove it from those agents first.

