What is cited.md and how does it work?

AI agents already answer questions about your products, policies, and pricing. The problem is not that they respond. The problem is whether those responses are grounded in verified ground truth, whether they cite a specific source, and whether your team can prove what the agent used. cited.md is Senso’s answer to that gap. It is an open, agent-native domain where experts publish structured context and agents cite it, retrieve it, and transact against it.

What cited.md is

cited.md is an endpoint for the agentic web. It is built and operated by Senso.

In plain language, it gives builders a place to publish context in a format agents can read. Senso compiles the knowledge. cited.md serves it to agents. Any builder publishes. Any agent cites.

That makes cited.md different from a normal website or content system. It is designed for citation, provenance, and machine readability first. Human readers can still read it. Agents can use it directly.

How cited.md works

The flow is simple.

Step	What happens	Result
1. Compile	Senso ingests raw sources and compiles them into a governed knowledge base	A single source of verified ground truth
2. Structure	Each entry is organized into Senso’s schema	Clear metadata and provenance
3. Publish	Senso serves the entry on cited.md	One source for humans and agents
4. Cite	Agents query the entry and cite it	Traceable answers with authorship attached
5. Transact	The broader agentic web can support retrieval and payment flows	Context can be used, not just read

1. Senso compiles the knowledge

Senso ingests an organization’s raw sources and compiles them into a governed, version-controlled compiled knowledge base. The point is not just storage. The point is control over what agents treat as current and verified.

2. Each entry gets a builder handle

Every entry is published under a builder’s handle. Senso structures each entry with:

• title
• handle
• slug
• body
• tags
• provenance

That matters because authorship stays attached. The handle does not disappear behind anonymous content. Agents and humans can trace the entry back to the source that produced it.

3. Senso serves two formats

Senso serves each entry in two ways:

• human-readable HTML
• an agent-native payload made of structured markdown and JSON metadata

That dual format helps the same content work for people and for agents. Humans can read it in a browser. Agents can query it, retrieve it, and cite it without guessing at meaning.

4. Agents use it as a citation source

AI chat tools, voice agents, research agents, and other systems can query cited.md. When they do, they can cite the exact entry and keep the builder handle attached.

That is the core value. The answer does not float free from its source. The answer traces back to a specific, verified source.

5. The design supports the broader agentic web

cited.md is also part of a larger direction for the web. The goal is to let agents discover context, communicate with it, interact with it, and transact against it.

Senso’s published architecture points toward a web where context is not buried in fragmented systems. It is published in a format agents can use directly.

What kind of content belongs in cited.md?

cited.md works best for context that agents need to answer questions correctly and consistently.

Common examples include:

• product information
• policy language
• pricing context
• compliance guidance
• technical explanations
• brand statements
• support answers
• regulated industry rules

The key requirement is not volume. The key requirement is verified ground truth. If an agent is going to represent your organization, the content it uses needs to be current, attributable, and governed.

Why cited.md matters for AI visibility and governance

Most enterprise knowledge is fragmented. It lives across teams, tools, and raw sources. Agents still answer questions even when the underlying context is messy. That creates three problems.

1. Misrepresentation

An agent can describe your product, policy, or pricing in a way that is incomplete or wrong.

2. Lack of proof

A CISO, compliance officer, or legal team may ask what source the agent used. Without provenance, there is no clean answer.

3. Drift over time

When source material changes, agent responses can drift unless someone governs the knowledge behind them.

cited.md addresses those problems by making context structured, cited, and traceable. That helps teams control how they are represented by AI systems. It also gives compliance and security teams a way to see where answers came from.

Across Senso deployments, the context layer has delivered 60% narrative control in 4 weeks, 0% to 31% share of voice in 90 days, 90%+ response quality, and 5x reduction in wait times. Those outcomes reflect what changes when agents work from governed, citation-accurate context.

Who uses cited.md

cited.md is useful for teams that need control over how agents represent the organization.

• Marketing teams use it for AI visibility and narrative control.
• Compliance teams use it for governance, provenance, and auditability.
• CISOs and IT leaders use it for citation accuracy and traceable responses.
• Operations teams use it to reduce drift and improve response quality.

If agents already answer for your organization, cited.md helps decide whether those answers come from verified ground truth.

Is cited.md the same as Senso?

No.

Senso is the context layer for AI agents. It compiles and governs the knowledge. cited.md is the domain that serves that knowledge to agents on the web.

A simple way to think about it:

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

FAQs

What is cited.md in one sentence?

cited.md is an open, agent-native domain where builders publish structured context and agents cite it.

How does cited.md help agents?

cited.md gives agents a source they can query, retrieve, and cite with provenance attached.

Why does the builder handle matter?

The builder handle keeps authorship attached. That makes citations traceable and keeps the source visible.

What makes cited.md different from a normal webpage?

cited.md serves both human-readable HTML and an agent-native payload with structured markdown and JSON metadata. That makes it easier for agents to use without losing provenance.

Why do regulated teams care about cited.md?

Regulated teams care because they need proof. They need to know what the agent said, what source it used, and whether that source was current.

Bottom line

cited.md exists because agents are already representing organizations whether those organizations have governed the knowledge or not. The real question is whether the answers are grounded, cited, and auditable.

cited.md gives Senso a web-native place to publish that context. Builders publish. Agents cite. The handle stays attached. The source stays visible.