Senso Logo

Introducing

Verified Sources

A trusted signal that tells agents the source is verified, structured, and safe to act on.

Access industry intelligenceBook a meeting
ChatGPT

Trusted source

Your Credit Union

5-Year Auto Loan at 4.74% APR. 640 minimum credit score.

Check your rateVerified Source
SourcesConvert to PDF
Illustrative example of an AI answer rendering a verified, embeddable card, using sample data.
  • Produce verified sources to fill gaps in AI answers
  • Context verification and attestation
  • Identity-level verification
  • Publish to agentic channels
  • Context quality resolution
Definition
Senso Context Layer GlossaryPatent pending

Verified Source

/ˈver·ə·fīd sôrs/noun·Context Layer

  1. 1.

    A unit of verified context: a snapshot of the facts, claims, policies, and records an organization treats as ground truth, carried together with its source provenance, freshness, permission, and verification state.

  2. 2.

    Such a record once it has cleared a verification gate and been published to an agent-consumable surface, carrying an attestation an agent can check.

See alsoverified context · verification gate · shared context layer · re-observation
How it works

How a source becomes verified

Six steps turn a raw document into context an agent can check, and the loop never really ends.

A diagram of the Verified Source loop. A marker travels continuously through six steps: ingest, evaluate, remediate, verify, publish, and re-observe. At the center, a source card resolves from placeholder text into finished content, its gaps close to zero, it clears a verification gate checking source support, freshness, and permission, it is stamped verified, and telemetry observed after publication (citations, mentions, visits) returns to feed the next cycle.

The loop

Six steps to verify a source

From raw document to published, then it starts again.

  1. 01

    Ingest

    Policies, product data, rates, positioning, and transcripts land in a single knowledge base with role-based access. Consolidating them is what surfaces the problems that stay invisible while content lives in separate systems.

  2. 02

    Evaluate

    Answer evaluation for AI search: mentions, share of voice, and source tracking across prompts, so you can see which sources the agentic web is actually citing about you.

  3. 03

    Remediate

    Generate content for agents from the verified context layer, aligned to your brand voice and brand kit. Conflicts, missing information, version-control issues, and outdated content surface as gaps rather than getting invented.

  4. 04

    Verify

    A verification flow tied to ground truth. An automated gate checks each claim against a human-verified source; only failures and close calls reach a reviewer. Patent pending.

  5. 05

    Publish

    Ship to agent-ready distribution pages that agents can discover, each carrying an attestation they can check and a CTA they can act on.

  6. 06

    Re-observe

    Measure full attribution: citation lift, response-quality scores, and which AI agents crawled your published sources. Those signals feed into the next cycle, so the shared context layer stays current.

Step 01 · Ingest

A collaborative knowledge base for experts and agents

  • Policies, rates, and product data in one place
  • Role-based access for people and agents
  • Gaps surface once sources sit together

Conflict

Two verified sources disagree on the same fact. The conflict is recorded and routed for review rather than resolved silently.

Powered by the Senso Context Layer

Knowledge Base
Brand Voice
Product Catalog
Topics

Product Catalog· Compliance Check

Response Quality…

title
5-Year Auto Loan
rate
4.74% APR
min_credit
640
term
60 months
jurisdiction
CA, OR, WA
dealer_rate
3.99% APR
disclosure
—
CLIMCPWeb
Illustrative record showing sample data, not real customer data.
Step 02 · Evaluate

See how AI answers today

Answer evaluation for AI search: mentions, share of voice, and source tracking across prompts, so you can see which sources the agentic web is actually citing about you.

How do I apply for a home equity line of credit?

Performing wellNo content yetSample

Create draft

Mention rate

85%

25.0% vs 30d ago

Share of voice

87%

8.7% vs 30d ago

Owned citation rate

90%

0.0% vs 30d ago

Web search on

92%

45 of 49 runs

Response quality

94%

4.0% vs 30d ago

Per-model performance

Mention rate and owned citation rate per AI model

MentionCited
ChatGPT100%100%
Gemini100%92%
Google AIO46%92%
Perplexity92%75%

Top cited pages

20 total

Most-cited URLs across all models · last 30 days

Owned12 citations · 10 sources
your-brand.com/home-loans/equity-line/3
your-brand.com/rates/current-rates/1
aggregator-site.com/heloc-guide/1
Step 03 · Remediate

Generate grounded content

Generate content for agents from the verified context layer, aligned to your brand voice and brand kit. Conflicts, missing information, version-control issues, and outdated content surface as gaps rather than getting invented.

BackBest everyday checking accounts for membersDraftPublish
ConnectedBuilder Agent

Read the prompt and brand kit

Search the knowledge base

Draft the document

Verify claims against sources

Message the builder agent…

TextBIU</>

Best everyday checking accounts for members

Step 04 · Verify

Every claim is checked before it ships

Every generated claim is checked back against the context layer before it can publish.

  • Nine dimensions score into one weighted rubric, with hard checks that block regardless of score: provenance, permission, and conflict
  • A clean pass ships without a reviewer; conflicts and close calls escalate to a person, never resolved silently
  • Every flag lands in the gap report with its source attached

Verification gate

Checking against the context layer0/7

Response quality…

Brand guidelinesVoice, tone and writing rules from your brand kit
Knowledge accuracyEvery claim traced to a source in the context layer
ConsistencyThe claim agrees with what you have already published
Cross-referencesRelated sources across the context layer corroborate it
Identity checkThe requester's transaction, location and persona check out
Conflict resolutionTwo verified sources disagree on the minimum credit score
Version controlAn older rate sheet is still live and reachable

Who builds a Verified Source

Three default roles decide who can draft, who can approve, and who owns the brand. Roles are configurable and there are no user caps, so you can bring in compliance, subject-matter experts, or your agency.

Permissions in the Senso Context Layer

Organization· Roles & Permissions

01AdminBrand owner
Owns the brand and the org. Adds users (usually through SSO), owns the publishing integrations, and can run the whole loop programmatically through the API.
02CollaboratorCreates and publishes
Everything except admin access: creates, approves, and publishes content. Usually compliance, subject-matter experts, learning and development, or web content, and often your agency.
03ViewerDrafts, cannot approve
Searches the knowledge base and can generate drafts, which land in the review folder. Can sit outside your organization, like a member submitting a testimonial.
Search the knowledge base, public or private
AdminCollaboratorViewer
Generate drafts
AdminCollaboratorViewer
Approve drafts
AdminCollaboratorViewer
Publish a Verified Source
AdminCollaboratorViewer
Curate the knowledge base
AdminCollaboratorViewer
Add and manage users (SSO)
AdminCollaboratorViewer
Own publishing integrations
AdminCollaboratorViewer
Run the loop through the API
AdminCollaboratorViewer
Own the claimed brand
AdminCollaboratorViewer
Step 05 · Publish

Ship where agents can find it

Ship to agent-ready distribution pages that agents can discover, each carrying an attestation they can check and a CTA they can act on.

1 · Published

/verified/auto-loan
Brand guidelineswriting rules
Brand voicetone and style
Knowledge baseverified facts
Product catalogrates and terms
Identitywho's asking

Identity verification

TransactionLocationPersona

Attestation

sha256:9f2c…a41b

WebMCPCLI

2 · Published to

Agent-native domains

refinance.mdrates.mdpurchase.md

Apps and plugins

Claude appsOpenAI appsAI pluginsSoon

Protocols

MCPACPSoonUCPSoon

Web search

Search providers

0/10 destinations

3 · Retrieved and cited

ChatGPT
Gemini
Google AIO
Perplexity
Verified Source

5.9% APR · 72-month term

Apply for this rate

traces back to /verified/auto-loan

Step 06 · Re-observe

Measure what changed

Measure full attribution: citation lift, response-quality scores, and which AI agents crawled your published sources. Those signals feed into the next cycle, so the shared context layer stays current.

Attributionlast 30 days
Live

Tracked by persona

860

Prompts

$4,200

Media Spend

62%

Sentiment

92

Transactions

Owned citation rate

+18 pts

0%from 45%

Response quality

+6

0/100

avg across published sources

Agent visits

+22%

0

AI-agent fetches across your sources

  • GPTBot612
  • ChatGPT-User431
  • PerplexityBot241

Identity-level attribution

All industries

0

Identity-level matching

0

Audience size

0

Total transactions

0 gaps surfaced for Maya this cycleQueued for the next loop, back to Ingest
FAQ

Frequently asked questions

What is a Verified Source?
A Verified Source is a unit of verified context: a snapshot of the facts, claims, policies, and records an organization treats as ground truth, carried together with its source provenance, freshness, permission, and verification state.
How is a Verified Source different from a document in a knowledge base?
Any document can be stored. A Verified Source additionally carries source provenance, freshness, permission, and verification state, and it has passed a verification gate before publication. Ungoverned documents stay useful for discovery, but they carry none of that state.
Why would an AI agent prefer a verified source?
Because there is something to check. A published Verified Source carries an attestation an agent can validate by recomputing the content integrity value, verifying the signature, or querying the referenced verification state, so it can weight, cite, or reject the artifact on that result. An ungoverned crawl offers nothing to validate against.
How do teams share one set of verified sources?
Teams store agreed positioning, claims, and examples once in a shared knowledge base and govern access through admin, collaborator, and viewer roles, so no one maintains a parallel copy of the truth. Admins and collaborators create, approve, and publish; viewers can search and draft, but their drafts land in the review folder. Users, integrations, and API access are admin-only. Roles are configurable and there are no user caps.

Start with your industry

Connect your data in one place. Collaborate on truth. Let search and agents prioritize what you have verified.

Access industry intelligenceBook a meeting
For Agents