Senso
Sign inSign up

Start here

Build with your AI agent and ground it in your knowledge base

Query your own knowledge. Every answer comes back with its sources.

Quickstart

01Get a Key (skip this step if you already have an api key ready)

Sign Up & Create a key

02Set up the CLI

Open your terminal, paste the block below, and paste your API key when senso login asks for it.

bash
npm install -g @senso-ai/cli &&
senso skills install context-layer --global &&
senso login

When the key is accepted you will see API key verified. The CLI stores it from there, so nothing after this needs the key again. --global installs the skill for every project rather than only the current one, and with no --agent it installs for every agent found on your machine — Claude Code, Codex, Cursor, Copilot, Gemini and Cline.

03Paste this into your agent to get started

Start your agent however you normally do, then send this as your first message.

prompt
Use the senso-context-layer skill to get me started with Senso.

The skill installed in step 02 picks this up. Getting an answer at all is the check: it means the key, the skill and your context layer are all live.

What people build with it

Ground an agent

Answers built only from your documents, returned with the sources they came from.

Power a workflow

Support, compliance and call center agents working from one source of truth.

Control what AI says about you

Publish what models should read, then measure whether the answer changed.

Ingest is stage 01 of six

Getting your documents in is the first stage. The rest is how you find what AI still gets wrong about you, fix it, and check that the answer changed.

01Build the Context LayerIngest sources into a knowledge base02Evaluate & RemediateCheck model answers against your sources03Generate & VerifyDraft content and verify its claims04Publish & ObservePublish, then measure the change
Open the applicationYour context layer, live.The whole loopSix stages, and where a human is required.Developer FAQsEvery term Senso uses, defined.

The context layer

Five sections to fill

Brand KitVoice, tone and the rules generation inheritsKnowledge BaseThe documents every answer is built fromContent TypesTemplates for the things you publishProduct CatalogWhat you sell, in a form an agent can quoteTopicsThe subjects you want to be found for

One place your agents read from, instead of five places nobody maintains.

Five sections, each holding a different kind of truth about your business. An answer draws on all of them at once, and every sentence it produces traces back to a document you own.

The dots are the readout that matters. A thin section is where answers go vague; an empty one is where they get invented.

How to fill them →Why ground truth →

See it run

Ingest knowledge

Hover any row
Upload your documentsPolicies, rates, termsPDF, Word, Excel, PowerPoint, HTML, CSV, JSON, XML — queryable once compiled.

Happens without you

Read my websitePages read on a scheduleComingYour public pages, re-read as they change. Nobody has to remember to re-upload.
Connect SlackDrop knowledge in a channelComingPost a decision in a channel, it lands in the knowledge base.
Connect your agentsClaude Code · Codex · CLILiveWhatever your agent can read, it can file. One MCP call, no connector to build.

Answer analysis

Running

What products or services do you offer?

10s

Six-week engagements, an annual product catalog1 and the advisory retainer3. Every line is quoted from a document you own2 — add more and run it again.

  1. 1product-catalog_2026.xlsx0.94
  2. 2about-us_who-we-are.pdf0.88
  3. 3Redwood_Six-Week.docx0.71
Sources cited
3
Top relevance
0.94
Answered in
…

Illustrative until you connect an organization.

Run this on your own knowledgeWith your organization, not an example.Open the playbook →

Already have a RAG system?

Keep it. Ask the same question of your stack and of Senso, then compare. Senso answers only from documents you own, with sources, so the difference is what your system invented or missed. Works against any pipeline, any model, local included.

What this covers, and what it doesn't

MCP covers ingest and query. Generation and publishing are on the CLI. Measurement needs step 2 first.