The API
Because one of the key benefits of large language models is the ability to extract information from unstructured data (such as text), SID does not attempt to impose a specific data model on you. Instead, most of the API is centered around text chunks, which are simply strings of text with some metadata attached to them. These are intended to be fed into a language model, which will then produce the final output. Chunks are created by retrieving text from the various data sources that a user has configured. Read on for more details on how this works.Query Endpoint
The main endpoint of the API is the/query endpoint.
Given a query string,
it retrieves text chunks whose content is relevant to the query.
These can then be used to generate the final, personalized, output.
Where does the data actually come from?
Currently, SID exposes data from the following sources:- Google Drive
- Notion
- Gmail
Why SID accounts?
There are two key benefits for using SID accounts, as opposed to a fully white-labeled solution: For you, it means that you don’t have to go through the hassle of being verified by each data source individually. In the case of google drive and gmail, for instance, this process takes weeks and requires a detailed security review of your application. For your users, if they already have a SID account, they can immediately get started with the full feature set of you application, without having to go through the hassle of setting up each data source individually.What’s next?
Quickstart
Give the API a try by following the quickstart guide
Integrate SID
Learn about the steps needed to integrate SID into your application