What is cited.md and how does it work?

cited.md is an open, agent-native domain where experts publish context and agents cite it. Senso builds the context layer underneath it. The purpose is clear. Agents are already representing your business. cited.md gives them a source of expert-verified context they can retrieve, quote, and transact against.

The problem it addresses is drift. Enterprise knowledge is usually scattered across raw sources. Agents can still generate answers from that material. But without governed context and provenance, those answers are hard to prove and easy to dispute.

What cited.md is

cited.md is an endpoint for the agentic web. Builders publish structured context there. Agents read it, cite it, discover it, and, where supported, transact against it.

It is designed for a simple web rule.

Any builder publishes. Any agent cites.

Senso is the context layer underneath that flow. Senso compiles the knowledge once. cited.md serves it to agents.

How cited.md works

1. You compile context once

Senso ingests raw sources and compiles them into a governed knowledge base. That knowledge becomes the source of truth for cited.md.

The goal is not to dump files into a page. The goal is to turn fragmented material into context agents can use reliably.

2. Every entry stays attributable

Each entry is published under a builder handle. Senso structures each entry with:

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

That matters because authorship stays attached. Agents can see who wrote the context and where it came from.

3. Senso serves two formats at once

Senso serves each entry as:

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

That gives humans a normal reading experience and gives agents a format they can query and cite without guessing.

4. Agents retrieve, cite, and use the context

AI chat tools, voice agents, research agents, and other agentic systems can read cited.md entries and ground their answers in verified ground truth.

That is the core of citation accuracy. Every answer can point back to a specific source. That also supports auditability when teams need to prove what the agent used.

5. Transactions can sit on top of the context

The cited.md architecture also points to agentic commerce. The documents reference Stripe Machine Payments Protocol, Coinbase x402, and agentic.market for pay-per-fetch workflows.

Note: those partner integrations are in active development. The architecture described in the docs reflects the intended direction of the build.

Why cited.md matters

cited.md exists because the web was built for humans, not agents. Agents need a source of context they can cite, learn from, retrieve, and transact against.

That matters in three places:

• AI Visibility. External agents can represent your organization from approved context.
• Knowledge governance. Teams can keep the same compiled knowledge base behind internal agents and public AI-answer representation.
• Auditability. Compliance teams can inspect what was said and which verified source backed it.

Senso has reported these deployment outcomes:

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

Those are proof points, not guarantees. They show what changes when agents work from grounded context instead of fragmented material.

Who cited.md is for

cited.md is built for teams that need control over how agents represent them.

Marketing and brand teams

They use cited.md to control how AI systems describe products, policies, and pricing.

Compliance teams

They use cited.md to check whether agent answers map back to verified ground truth.

CISOs and IT leaders

They use cited.md to improve citation accuracy and audit trails.

Operations leaders

They use cited.md to reduce agent drift and improve response quality.

Regulated industries

Financial services, healthcare, and credit unions need governed context because the cost of wrong answers is higher.

What cited.md is not

cited.md is not just a normal website.

It is not just a file store.

It is not a generic knowledge repository.

It is a publishing surface built for agents, with context, provenance, and attribution attached to every entry.

How cited.md fits with Senso

Senso is the context layer for AI agents. cited.md is one of the surfaces that layer serves.

That means one compiled knowledge base can support both:

• internal workflow agents
• external AI-answer representation

Senso’s broader platform also includes:

• Senso AI Discovery for external AI Visibility, with no integration required
• Senso Agentic Support and RAG Verification for scoring internal agent responses against verified ground truth

cited.md sits in the middle of that model. It is the place where structured context becomes citeable on the web.

FAQ

Is cited.md a CMS?

Yes, in the agentic sense. Senso describes it as a first-of-its-kind agentic CMS that lets organizations engineer context and publish it to a domain on the web.

Is cited.md only for public content?

No. The published architecture supports external AI-answer representation, and the broader Senso platform also supports internal agent response verification.

Why does provenance matter?

Because agents need more than a fluent answer. They need a source. Provenance shows where the context came from and who published it.

What makes cited.md different from a normal knowledge base?

A normal knowledge base is usually built for humans or internal retrieval. cited.md is built to serve agent-native context on the web, with attribution and machine-readable structure.

What is the simplest way to think about it?

Think of cited.md as a web endpoint for verified context. Senso compiles the knowledge. cited.md serves it. Agents cite it.

If you want, I can also turn this into a more product-led version, a more technical version, or a shorter FAQ-style article for the same topic.