- Ingest structured or unstructured data.
- Configure agent prompts to guide AI behavior.
- Convert that data into executable context for downstream tasks.
/ingest
, and you’re off—no orchestration glue or boilerplate brokers needed.
What is Context OS?
Context OS is a unified knowledge layer for your application. It:- Ingests documents, emails, and web content.
- Normalises every item into schema‑safe records.
- Exposes rule‑driven endpoints so AI agents, chatbots, or workflow automations can run with minimal integration effort and always‑accurate context.
SOURCE → CONTEXT OS → DESTINATION
Component | Description | Details |
---|---|---|
SOURCE | Point any raw input at Senso | • POST /content/* — files, single pages, full‑site crawls• POST /conversations — calls, chats, support‑email threads |
SENSO WORKSPACE | Index, label, transform, and route the data | • /search , /generate — query / transform• /rules , /rules/{id}/values — classify (e.g., BUG, FEATURE)• /triggers + /webhooks — fire actions when a rule matches |
DESTINATION | Handle the JSON webhook payload (your code) | You expose an endpoint (GitHub, HubSpot, Slack, DB, etc.); Senso POSTs the clean JSON payload for you to process |
- Upload content (our “Hello World” text) so Senso has something to work with.
- Create a rule that flags any content containing the word HELLO.
- Register a webhook (point it at RequestBin, Hookdeck, or any public URL).
- Link a trigger so that every HELLO hit instantly calls your webhook.
- (Bonus) Run a quick search and generate to prove the Workspace can answer questions and transform text.
SENSO_KEY
) and you’ll see the complete Source → Workspace → Destination loop in action—ready to copy-paste for your own use case.
PrerequisiteEnsure you have received the “Your Senso Platform Access” email containing your unique API key and access domain. Contact [email protected] if you require assistance.