Module 1 of 4 · Stage 01

Build the Context Layer

01Build the Context LayerGet your knowledge in 02Evaluate & RemediateFind what is wrong 03Verify & PublishFix it and ship it 04Re-observe & ActivateMeasure what changed

Objective

Get your approved sources into one place an agent can query, so every answer it gives can point at a document you own.

Immediate, seconds to minutes · Produces a knowledge base you can query · Usually whoever owns the source material

In the loop

Ingest is the only stage that produces nothing but input. Every other stage reads what you put in here, so a gap at this stage surfaces as a wrong answer several stages later, where it is far harder to trace.

Do this	Call	Why
Get one folder in first	`POST /org/kb/upload`	The loop cannot start until something is queryable. Structure is easier to fix than absence.
Send markdown as text	`POST /org/kb/raw`	senso ingest upload rejects .md. Text and markdown go in this way or over MCP.
Put it in the section it will be checked against	`POST /org/kb/folders`	A price in a PDF in the Knowledge Base cannot be checked against the Product Catalog.
Wait for compilation	`GET /org/kb/sync-status`	A document is queryable only once processing finishes. Do not assume it.

Step 1 — Say who you are

Two fields. Everything after this is scoped to them, and the domain is what makes a citation count as yours.

Organization nameDomain you own

These two decide what counts as yours. The domain is how a citation gets classified as your own source rather than someone else's.

curl https://apiv2.senso.ai/api/v1/org/brand-kit \
  -H "X-API-Key: $SENSO_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"guidelines": {"brand_name": "Acme Credit Union", "brand_domain": "https://acme.com"}}'

Stays in your browser. Runs once you have a key.

Step 2 — Put your sources in the right section

Five sections, not one folder. Where a source goes decides what it can be checked against later. Run a test search to see which sections actually carry an answer.

Brand Kit

/org/brand-kit6 of 6 fields

Voice, tone and rules, so generated content sounds like you.

Knowledge Base

/org/kb14 documents

The sources that make an answer citable.

Content Types

/org/content-types4 templates

Templates controlling structure, tone and CTAs.

Product Catalog

/org/product-lines8 products

What you sell, and on what terms.

Topics

/org/tags11 tags

The tags joining questions, sources and gaps.

Test search

Ask the context layer something and see which sections carry the answer. If one section does all the work, the rest are not pulling their weight yet.

These are documents you own. Whether they are true, current and approved is the gate in stage 03. Counts are illustrative until you connect an organization.

Common mistake

Putting a price in a PDF in the Knowledge Base. A claim about that price cannot then be checked against the Product Catalog, because as far as the system is concerned there is no catalog.

Context Layer

The five sections together. Everything Senso treats as your approved truth, as opposed to anything it reads from the open web.

Full definition →

Each has a reference page: Brand Kit, Knowledge Base, Content Types, Product Catalog and Topics.

Step 3 — Ask it something

Query it and read what comes back. You get an answer plus the documents behind it, each with an id you can cite. If nothing relevant is there, it tells you, rather than inventing an answer.

Start Here connects an agent and runs all three in about five minutes.

Grounded answer

An answer built only from your documents, returned with the sources it used. The interesting half is the negative case: no relevant source means no answer, not a guess.

Full definition →

How to reach it

POST/org/kb/rawOpen in API reference →Ingest markdown or plain text straight into the knowledge base.

POST/org/kb/uploadOpen in API reference →Upload files: PDF, Word, Excel, PowerPoint, HTML, CSV, JSON, XML.

PUT/org/brand-kitOpen in API reference →Set brand name, domain, voice, tone and writing rules.

POST/org/product-linesOpen in API reference →Add a product, its terms, pricing and eligibility. The Product Catalog.

POST/org/tagsOpen in API reference →Create a topic. Tags are how gaps line up with content later.

POST/org/searchOpen in API reference →Query it and get an answer with the documents behind it.

Rules for this stage

Confirm the organization before any write.
Search before ingesting again — identical text does not create a second copy.
Updating a document replaces its body. Read it first, send the whole new version.
A document is not searchable until compilation finishes. Poll until it reports complete.
Never put API keys, tokens or customer personal data in a source.

No approvals are needed anywhere in this stage. Gates start in module 2, when something proposes changing what you consider true, and in module 3, when anything goes out.

Done when

Each source is in its own section, not all in one folder
A search returns an answer with its sources
An irrelevant question returns nothing rather than a guess

An internal answer is not a Verified Source. That takes the gate in module 3.

Module 2: Evaluate & Remediate The Loop

Next module