Senso
Also known as: Senso.ai
Verified context infrastructure for AI agents, with a compiled, permissioned knowledge base, monitoring of what AI models say about an organization, and a verify and publish loop, reachable by API, MCP server, CLI and agent skills.
Senso is verified context infrastructure for AI agents. Organizations ingest their policies, product data and positioning into a knowledge base that Senso compiles for agents to query, organized as a folder tree with permissions, tags and version history, alongside a brand kit, content types, a product catalog and topics. Senso then runs a six stage loop.
It monitors how ChatGPT, Claude, Gemini and Perplexity answer the questions an organization is tracked on, finds where answers are missing or wrong, drafts content from verified sources, checks each draft for source support, faithfulness, freshness and permission with only failures and close calls escalating to a human reviewer, publishes structured context for agents to read, and measures whether the answers changed.
Its products are Narrative Control for AI citations across the open web, a Context Layer that keeps internal copilots grounded, Context OS, an API for building on verified context, and a Partner Platform. Developers reach it through a REST API with scoped API keys, an MCP server that queries, reads and ingests over OAuth, a CLI, and installable agent skills for Claude Code, Codex, Cursor and other coding agents. Usage draws on organization credits. Senso publishes a live AI visibility benchmark for credit unions under the CuCopilot name and is backed by Y Combinator. Prices are not published.
Vendor details
Canonical URL
https://www.senso.ai
Category
Agent infrastructure
Funding status
Seed (Y Combinator W24)
Company status
independent
Use cases & customers
Primary use cases
Target customers
Deployment options
Integrations
Senso is API first, with partners such as TribalScale and Fundmore building on Senso's APIs. Senso ingests raw sources from PDFs, wikis and siloed systems through upload, its API, MCP server, CLI and connected agents. There are no native connectors, and connecting Slack and reading a website on a schedule are both coming.
In practice
Your marketing team wants to know what AI models say about your products. Senso runs your tracked prompts against the models you choose on a schedule and files the questions they leave unanswered in a gap report.
Your content team needs to publish answers without putting unchecked copy live. Senso checks each draft for source support, faithfulness, freshness and permission, and only failures and close calls go to a reviewer, who approves or rejects them before anything is published.
Your engineers want an internal coding agent to answer from company policy. They install Senso's agent skills in Claude Code or Cursor, and the agent queries the knowledge base through the MCP server, getting grounded answers that cite the source chunks behind them.
Sources & related URLs
Agentic Index coverage score
8.0 / 14 capabilities · 57%
| Integrations & Tool Calling | Partial |
|---|---|
|
Content reaches Senso by upload, the API and connected agents, and the review-publish skill publishes approved drafts to a destination. Reading a website on a schedule and connecting Slack are both coming. Shopify, Stripe and website crawling come as code recipes. There is no native, authenticated connector that lets an agent read and act in outside systems. SourceSenso, docs.senso.ai start, agent-skills and recipe pagesread 2026-09-21 |
|
| Workflow Orchestration | Partial |
|
A fixed six stage loop (ingest, evaluate, remediate, verify, publish, re-observe) runs over a pipeline that ingests, compiles, queries and generates. A quickstart skill sequences the other skills for a customer's coding agent. The pipeline is Senso's own, and customers cannot build workflows with branching, retries, fallbacks or deterministic nodes. SourceSenso, senso.ai llms.txt and docs.senso.ai concepts and agent-skillsread 2026-09-21 |
|
| Knowledge Grounding & RAG | Full |
|
Files (PDF, Word, Excel, PowerPoint, HTML, CSV, JSON, XML) and raw text come in through the API. Senso compiles each source before it can be queried and keeps sources in a knowledge base folder tree with permissions, tags and version history. Search returns a grounded answer that cites the source chunks behind it, with their relevance scores, and unanswered questions are filed as gaps. SourceSenso, docs.senso.ai concepts, knowledge-base and mcp-serverread 2026-09-21 |
|
| Human Oversight & Guardrails | Full |
|
In the verify stage, only failures and close calls from the automated check escalate to a human reviewer. Generated drafts wait in review until a person approves or rejects them, and nothing is published before that. The loop sets out which stages require a human. SourceSenso, senso.ai llms.txt and docs.senso.ai agent-skillsread 2026-09-21 |
|
| Security, Identity & Governance | Partial |
|
Admin, collaborator and viewer roles sit alongside custom roles built from granular permissions, each an action on a resource. API keys are scoped to knowledge base folders, and each folder has its own access list. OAuth connections to the MCP server act only with the approving person's permissions, using PKCE and rotating refresh tokens. There is no published certification or audit report. SourceSenso, docs.senso.ai permissions and mcp-serverread 2026-09-21 |
|
| Observability & Auditability | Partial |
|
Every query is recorded as a query turn in search history. Each turn is tagged by source, such as mcp, so agent traffic shows separately in analytics, and unanswered queries go into a gap report. The record shows that each request was made and whether it found an answer. There is no step by step view of the prompts, retrieved chunks, tool calls and outputs in an agent's run. SourceSenso, docs.senso.ai mcp-server and analyticsread 2026-09-21 |
|
| Memory & State Persistence | Not documented |
|
Shared context in Senso is the organization's knowledge base, which people and their agents query and add to. There is no separate session, conversation or agent memory. SourceSenso, docs.senso.ai shared-context and conceptsread 2026-09-21 |
|
| Deployment & Data Residency | Not documented |
|
Customers reach Senso as a hosted API, MCP server and application at senso.ai. There is no self hosted, dedicated cloud or VPC option, and customers cannot choose a region. SourceSenso, docs.senso.ai start, concepts and mcp-serverread 2026-09-21 |
|
| Prebuilt Agents / Templates / Packs | Full |
|
Teams can install a set of agent skills (quickstart, context-layer, evaluate-remediate, generate-verify, publish, search and review-publish) all at once or one at a time, including from the Shipables catalog, for Claude Code, Codex, Cursor, Copilot, Gemini and Cline. Reusable content type templates and recipes, such as a help center crawler and a blog to social converter, sit alongside them. SourceSenso, docs.senso.ai agent-skills, content-types and recipe pagesread 2026-09-21 |
|
| Triggers & Channel Coverage | Full |
|
An organization's tracked prompts run against AI models on a schedule, and the results feed the gap report. Otherwise, people and agents start work through the application, API, CLI and MCP server. SourceSenso, docs.senso.ai analytics and mcp-serverread 2026-09-21 |
|
| Model Flexibility & Routing | Not documented |
|
Customers choose which AI models Senso monitors, and a raw context endpoint lets them feed Senso's retrieval into their own LLM. Customers cannot choose the model Senso itself uses to generate answers and drafts. SourceSenso, docs.senso.ai analytics and conceptsread 2026-09-21 |
|
| APIs / SDKs / MCP Extensibility | Full |
|
A REST API at apiv2.senso.ai covers ingesting, compiling, querying and generating, authenticated with scoped organization API keys. An MCP server's tools query, read and ingest into the knowledge base over OAuth or an API key, and a CLI serves scripts and CI. SourceSenso, docs.senso.ai concepts, authentication, mcp-server and CLIread 2026-09-21 |
|
| Testing, Debugging & Optimization | Full |
|
Before anything Senso generates is published, an automated gate checks each draft for source support, faithfulness, freshness and permission. Drafts are checked against the organization's own sources, and the verification results are listed for review. Evaluation runs can be batched in parallel across tracked questions. SourceSenso, senso.ai llms.txt and docs.senso.ai use-cases/test-ai-answersread 2026-09-21 |
|
| Browser / Computer-use | Not documented |
|
Work happens through uploads, the API, the CLI and the MCP server, and no agent controls a browser, desktop or computer. SourceSenso, docs.senso.ai start and recipe pagesread 2026-09-21 |
|
The Agentic Index coverage score grades every vendor Full, Partial or Not documented against the same 14 buyer facing capabilities, from public evidence only. Each capability links to how all vendors in the index score on it. How this evidence is graded
Pricing
Not public; credits-based usage
Organization credits consumed by queries and generation, with a spend limit; rates not published.
Cost watchouts
Every query and generation consumes credits, and a call fails with a 402 once credits or the spend limit run out, so automated and monitoring traffic draws down the same balance.
Variable cost rationale
Queries and generation consume organization credits, so cost scales with usage, but no credit rate is published.
Sales call required
Yes, required for paid access
Free / trial
No free tier or trial published
Lowest paid plan
Not publicly listed.
Key ambiguities
senso.ai's llms.txt sends 'Get Started' to a waitlist, while docs.senso.ai offers sign-up and API keys; no pricing page or credit rates are published.
Related vendors
- AgentOps — Agent observability and debugging platform: open source SDKs trace…
- Agno — Python agent framework and AgentOS runtime (formerly Phidata) for…
- AIsa — Resource and payment gateway for AI agents, with one key to 110+…
- AlphaBitCore — AI control plane for regulated financial firms: one gateway enforces…
- Anchor Browser — Cloud hosted browser infrastructure that lets AI agents operate real…
- Apify — Cloud platform and marketplace of more than 73,000 ready-to-run…
Alternatives to Senso
The closest documented capability profiles to Senso among agent infrastructure platforms tracked by Agentic Index, ordered by similarity on the same 14 point evidence the rankings use. No vendor pays for placement.
- Shopify8.5 / 14Adds documented Memory & State Persistence
- Cyara4.5 / 14A lighter documented profile than Senso
- Fluid Topics7.5 / 14Adds documented Model Flexibility & RoutingSenso vs Fluid Topics →
- Personal AI9.5 / 14Adds documented Memory & State Persistence and Deployment & Data Residency, among others
- Force Equals8.0 / 14Adds documented Memory & State Persistence
- Kerno8.0 / 14Adds documented Memory & State Persistence and Deployment & Data Residency
Similarity is computed from each vendor's Agentic Index coverage score evidence, axis by axis, not from the totals. How this evidence is graded