
cited.md — An Endpoint for Agents on the Agentic Web
cited.md is a proposed endpoint for the agentic web. It gives AI agents a stable place to read, cite, and transact against published material, using handle-based authorship and machine-payable rails such as Stripe MPP, Coinbase x402, and CDP.
That matters because agents already represent organizations in public answers. If the source is fragmented, the answer drifts. cited.md treats that as a knowledge governance problem, not a formatting problem.
What is cited.md?
cited.md is a proposed publishing domain that lets machines find the approved version of content and its proof. Senso’s route map describes /cited-md as an essay, and it ships a /cited-md.md mirror for machine-friendly access.
The essay is 1,734 lines long. That scope shows the topic is not just publishing syntax. It is a full model for authorship, citation, and machine payment on the agentic web.
What does cited.md include?
cited.md centers three ideas:
- Handle-based authorship, so the author identity is durable and traceable.
- Machine-payable rails, named in the essay as Stripe MPP, Coinbase x402, and CDP.
- Retrievable proof, so the approved version can be cited and checked later.
These pieces matter together. A page that can be read by agents, attributed to an author, and tied to payment rails becomes an endpoint, not just a webpage.
Why does the agentic web need an endpoint like cited.md?
The agentic web needs a publishable destination because agents do not just browse. They discover, evaluate, verify, and increasingly transact. A normal page can present information, but it does not guarantee the approved version or its proof.
cited.md addresses that gap by making publication machine-facing. The goal is simple: distribute the exact approved version and make its proof retrievable.
What problem does this solve?
It solves the gap between where knowledge lives and where agents need it to be.
-
Agents need a canonical source.
If an agent answers for your brand, it needs a place to point back to. -
Teams need proof, not just output.
Senso’s model is built around verified ground truth and citation accuracy, so every answer can trace back to a specific source. -
Published content and payment are converging.
The cited.md proposal names machine-payable rails, which means the endpoint is meant to support both reading and action.
How is cited.md different from a normal publishing page?
cited.md is built for agents first, while a standard page is built for readers first. That changes how authorship, proof, and transaction paths are handled.
| Property | Standard publishing page | cited.md |
|---|---|---|
| Primary audience | People | Agents and people |
| Authorship | Often a byline or CMS field | Handle-based authorship |
| Proof | Usually separate from the page | Designed to be retrievable |
| Transactions | Separate checkout or billing flow | Machine-payable rails are part of the model |
| Distribution | Human navigation | Agent-readable destination |
The key difference is not the file extension. It is the publishing contract. cited.md is meant to be a destination where agents can cite the source and keep the proof attached.
How does cited.md fit into Senso’s knowledge governance model?
cited.md sits on top of governed knowledge. Senso compiles an enterprise’s full knowledge surface into a governed, version-controlled compiled knowledge base, and every answer traces back to a specific, verified source.
That matters because an endpoint cannot prove anything if the source layer is already fragmented. cited.md only works when raw sources have already been compiled into verified ground truth.
Why does that matter for regulated teams?
Regulated teams need auditability. If a CISO, compliance lead, or operations leader asks where an answer came from, the organization needs a retrievable trail.
Senso’s model is built for that pressure. The route map places /verified-sources beside /cited-md, and /verified-sources is the canonical definition of a Verified Source. That pairing matters because one page defines the source and the other provides the publishing surface.
What does cited.md mean for AI Visibility?
cited.md gives AI Visibility a destination that agents can cite with confidence. If public AI responses are already representing your brand, then the question is whether those responses point to verified ground truth or drift into guesswork.
Senso’s AI Discovery product is built to score public AI responses for accuracy, brand visibility, and compliance against verified ground truth. cited.md supports that model by giving agents a place to point to the approved version.
Who should care most?
- Marketing teams that need narrative control in public AI answers.
- Compliance teams that need citation accuracy and audit trails.
- Operations teams that need response quality without manual cleanup.
- Technical teams that need one compiled knowledge base to serve both internal workflow agents and external AI-answer representation.
Where does cited.md sit in Senso’s site architecture?
cited.md is not an isolated idea. Senso’s route map shows /cited-md as one of the editorial pages meant to be cited by AI agents, and it also serves /cited-md.md as a markdown twin.
The page has its own white shell and scoped layout, which separates it from the default chrome. It also carries a hand-written JSON-LD @graph, which reinforces that the page is meant to be structured for machine use, not only human reading.
What should teams take from cited.md?
The main lesson is that AI answers need governed sources. If agents are already answering questions about your products, policies, and pricing, then you need a surface that can prove where each answer came from.
cited.md is that surface in proposal form. It is a publishing endpoint for the agentic web, built around authorship, proof, and machine action.
FAQs
What is cited.md?
cited.md is a proposal for an agent-native publishing domain. It combines handle-based authorship, machine-payable rails, and retrievable proof so agents can cite an approved version.
Is cited.md a standard?
No. In Senso’s essay, cited.md is a proposal, not a web-wide standard. It describes where publishing may go as agents become the primary interface to business information.
How is cited.md different from a normal blog post?
A normal blog post is usually built for human reading. cited.md is built as a destination that agents can read, cite, and connect to proof and payment paths.
Does cited.md replace a website?
No. It can sit beside a website or CMS as an approved destination. Senso’s platform notes that an organization can use its own site, a brand-specific page on cited.md, or both.
Why does this matter for compliance?
Because compliance needs proof. If an agent gives an answer, the organization needs to show the verified source behind that answer and the version that was approved.