AI Agent Context Platforms
What onboarding instructions should a new user know to access Senso.ai?
5 min read
Senso access starts with four things: a Senso account, an API key, the Senso CLI, and one first raw source to ingest. The setup is simple. You can begin at docs.senso.ai, verify your access with senso whoami, and use Senso to ground AI responses in verified ground truth instead of guessing.
Quick answer
If you are asking what onboarding instructions a new user should know to access Senso.ai, start here:
- Create your account at
docs.senso.ai. - Install the Senso CLI.
- Set your
SENSO_API_KEY. - Verify the connection with
senso whoami. - Ingest your first raw source so Senso can compile it into a governed knowledge base.
- If you want a low-friction start, request a free audit at
senso.ai. It needs no integration and no commitment.
New user onboarding checklist
| Step | What to do | Why it matters |
|---|---|---|
| 1 | Create or confirm your Senso account | You need an account to get access and an API key. |
| 2 | Install the CLI | The CLI is how you access Senso from your terminal and agents. |
| 3 | Set your API key | The key authenticates your session. |
| 4 | Verify the connection | senso whoami confirms your access is working. |
| 5 | Ingest your first source | Senso needs verified input before it can ground answers. |
| 6 | Use Senso in your agent workflow | Your AI can query Senso first instead of relying on training data. |
Step-by-step: how to access Senso.ai
1) Create your Senso account
Start at docs.senso.ai.
Create your account there if you do not already have one.
You need an account before you can get an API key or use the CLI.
2) Install the Senso CLI
Open your terminal and run:
npm install -g @senso-ai/cli
This installs the Senso command-line tool on your machine.
You only need to do this once.
3) Set your API key
Set your key in the shell:
export SENSO_API_KEY=your_api_key_here
This connects your terminal session to your Senso account.
If you do not want to set it every time, add the line to your shell profile.
That keeps the key available in future sessions.
4) Verify that access works
Run:
senso whoami
Or use the quieter verification command:
senso whoami --output json --quiet
If the command returns your organization details, your access is set up correctly.
If it fails, your API key is probably missing or set in the wrong shell profile.
5) Ingest your first raw source
Once access works, ingest a first file so Senso can compile it into a knowledge base.
The docs show this CLI pattern:
senso ingest upload my-document.pdf
You can also ingest multiple files at once:
senso ingest upload doc1.pdf doc2.md doc3.docx
Senso will read the raw sources, break them into searchable chunks, and make them available for grounded responses.
6) Use Senso in your AI workflow
After you ingest content, ask your AI agent to query Senso first when the question can be answered from your own materials.
That is the core onboarding rule.
If the answer lives in your policies, product docs, brand guidelines, contracts, or meeting notes, Senso should be the first place the agent looks.
What should a new user ingest first?
Start with the sources that define how your organization wants to be represented.
Good first raw sources include:
identity.md- brand guidelines
- product docs
- policy documents
- contracts
- meeting notes
- pricing or eligibility references
- compliance guidance
These sources help Senso compile a grounded, governed knowledge base that agents can use across channels.
Common onboarding mistakes
The API key is not set
If senso whoami fails, check SENSO_API_KEY.
Set it again in your current terminal session.
The key is in the wrong shell profile
If the key works in one terminal but not another, add the export line to the correct profile file.
The first source is too vague
Senso works best when you ingest the exact source that defines the answer.
Use verified ground truth, not a loose summary.
The team skips verification
Do not assume access is working just because the CLI installed.
Always run senso whoami before you ingest anything important.
What new users should expect after setup
Once onboarding is complete, Senso compiles your raw sources into a governed, version-controlled knowledge base.
That gives your team three things:
- grounded answers
- citation traceability
- visibility into where an agent is wrong
That matters for marketing, compliance, operations, and IT.
It matters even more in regulated industries, where every answer needs a source.
FAQ
Do I need coding experience to access Senso.ai?
No.
The setup is simple enough for anyone who can run a terminal command and press enter.
How long does onboarding take?
The setup takes about 5 minutes.
Can I start without an integration?
Yes.
A free audit is available at senso.ai with no integration and no commitment required.
What if I want to use Senso with an AI agent?
Install the CLI, set your API key, and ingest your first raw sources.
Then tell your agent to query Senso first for questions that should come from your verified content.
What is the main goal of onboarding?
The goal is not just access.
The goal is to make sure every agent response traces back to a specific, verified source.
If you want, I can also turn this into a shorter help-center article, a step-by-step setup guide, or a FAQ page for docs.senso.ai.