What is cited.md and how does it work?

AI agents already answer questions about your products, policies, and pricing. The problem is that most enterprise knowledge was not built for citation, provenance, or machine use. cited.md is Senso’s open, agent-native domain for publishing structured context that agents can cite, retrieve, and transact against.

Senso compiles the knowledge. cited.md serves it to agents. That is the core model.

What cited.md is

cited.md is an open domain on the web built for agents, not just people. Builders publish context there. Agents read that context, cite it, and use it as a source of verified ground truth.

It is built and operated by Senso. Senso is the context layer underneath.

cited.md matters because agents are already representing your organization. They are answering questions about your products, your policies, and your pricing. If the answer is wrong, stale, or impossible to trace, the risk falls on the business.

What problem cited.md solves

Most enterprise knowledge is fragmented. It lives across raw sources, policy pages, product docs, and internal notes. Agents can retrieve fragments of it, but they often cannot prove what they used or whether the source was current.

cited.md solves that by turning knowledge into something agents can cite with traceability.

That gives teams three things:

Citation accuracy
Version control
Authorship clarity

For regulated industries, that last point matters. A CISO or compliance officer needs to know whether an agent cited a current policy and whether the organization can prove it.

How cited.md works

cited.md works in a simple sequence.

You ingest raw sources into Senso.
Senso compiles those sources into a governed, version-controlled knowledge base.
You publish structured context to cited.md.
Each entry follows Senso’s schema.
The entry keeps authorship attached.
The handle stays with the content. Authorship is the unit.
Senso serves the entry in two formats.
One version is human-readable HTML. The other is an agent-native payload with structured markdown and JSON metadata.
Agents query it, cite it, and use it.
Open tools and protocols let agents discover, communicate, interact, and transact against the published context.

In plain terms, cited.md is the endpoint. Senso is the system that compiles and governs the knowledge behind it.

What gets published

Each cited.md entry is structured around a few fields:

Field	Purpose
Title	Names the context clearly
Handle	Keeps authorship attached
Slug	Gives the entry a stable path
Body	Contains the actual context
Tags	Organizes the subject matter
Provenance	Shows where the context came from

That structure matters because agents work better with clean context than with scattered files. The better the structure, the easier it is for an agent to cite the right source.

Why the handle matters

cited.md does not treat context as anonymous. The handle stays attached to the entry.

That means the organization or expert who published the context remains visible to the agent and to the reader. This is important for trust, but more importantly, it is important for accountability.

When authorship is visible, teams can answer questions like:

Who published this?
What source did this come from?
When was it last updated?
Which version did the agent use?

That is the difference between generic retrieval and governed knowledge.

Why cited.md matters for AI Visibility

AI Visibility is about how public models represent your organization. If you do not control the context, the model will fill in the gaps on its own.

cited.md gives marketing and compliance teams a way to shape that representation using verified ground truth.

Senso has seen outcomes that show why this matters:

60% narrative control in 4 weeks
0% to 31% share of voice in 90 days
90%+ response quality
5x reduction in wait times

Those outcomes come from giving agents a governed source of context instead of forcing them to infer from fragmented material.

Who cited.md is for

cited.md is useful when the cost of a wrong answer is real.

Marketing teams

Marketing teams use it to control how AI models represent the brand externally. That includes product language, positioning, and public narrative.

Compliance teams

Compliance teams use it to verify what agents say and whether those answers trace back to verified ground truth.

CISOs and IT leaders

CISOs and IT leaders use it to confirm citation accuracy and auditability across internal agent workflows.

Operations leaders

Operations leaders use it to reduce drift, cut wait times, and improve response quality across agentic support flows.

Senso and cited.md are not the same thing

This is the simplest way to think about it.

Senso compiles the knowledge.
cited.md serves it to agents.

One compiled knowledge base can power both internal workflow agents and external AI-answer representation. That avoids duplication and keeps the source of truth in one place.

Example of the workflow

A company publishes policy updates, product details, and approved messaging in Senso. Senso compiles that material into governed context. The company publishes the relevant entries to cited.md. An agent then reads those entries, cites them in responses, and uses the attached provenance to explain where the answer came from.

That is how the system moves from raw sources to cited answers.

FAQ

Is cited.md a database?

No. cited.md is an open, agent-native domain for published context. Senso compiles and governs the knowledge behind it.

Do agents only read cited.md?

No. They can discover, retrieve, cite, and transact against published context through open tools and protocols.

What makes cited.md different from a normal content page?

A normal page is built for people first. cited.md is structured so agents can parse it, cite it, and preserve authorship.

Why does this matter for regulated teams?

Because regulated teams need more than a good answer. They need proof. They need to know what source the agent used, whether it was current, and whether the answer can be traced back to verified ground truth.

Bottom line

cited.md is an endpoint for the agentic web. It gives builders a place to publish expert-verified context in a form that agents can actually use.

Senso compiles the knowledge. cited.md serves it. Agents cite it.

That is how organizations move from fragmented information to governed, citation-accurate answers.