Agent-First Content Package
Make your Xperience by Kentico site legible to people, crawlers, apps, and AI agents from one content model. Everything Refined Element built for Ask Refined Element, built on your site.
Limited engagement slots — availability confirmed within one business day.
How It Works
Book or Reach Out
Request the Agent-First Content Package using the request form, or book a 20-minute fit call first if you have questions.
What We Need From You
- Admin access to the Xperience by Kentico instance and the repository
- One content owner available for interviews
- Agreement on the knowledge scope in week 1
Delivery Window
3 weeks (15 business days)
What You Receive
Live agent-readable surfaces on your own domain, a short "how agents see your site" report covering before and after, the MCP server published under your name, and documentation for your editors.
What's Included
- week 1 discovery: content-model review and selection of the 10–20 pieces of knowledge worth exposing
- weeks 2–3 build: typed knowledge content types in a headless channel — articles, checklists, and endpoint descriptors
- generated llms.txt and llms-full.txt, emitted from your content rather than hand-maintained
- JSON-LD structured data on key pages
- a public JSON knowledge API with rate limiting
- a published MCP server for your site, on npm and NuGet
- an editing workflow so marketers keep it current
- optional add-on, quoted separately: one L402-paid endpoint for premium content, through Lightning Enable — Refined Element's agent-commerce software
What's Excluded
- It excludes content writing beyond restructuring what you already have, site redesign, migration work, and Bitcoin or Lightning wallet setup — the last is covered by the optional paid-endpoint add-on if you choose it.
What We Need From You
- Admin access to the Xperience by Kentico instance and the repository
- One content owner available for interviews
- Agreement on the knowledge scope in week 1
Timeframe & Deliverable
Timeframe: 3 weeks (15 business days)
Live agent-readable surfaces on your own domain, a short "how agents see your site" report covering before and after, the MCP server published under your name, and documentation for your editors.
Frequently Asked Questions
Do we need to accept Bitcoin?
No. The paid endpoint is an optional add-on, quoted separately, and nothing else in the package depends on it. Skip it and you still get the typed knowledge content types, the generated discovery files, the structured data, the public JSON knowledge API, the MCP server, and the editing workflow.
Does this replace SEO?
No. It sits on the same structured content and the same canonical and sitemap discipline that search already depends on. Agent-first marketing — GEO, generative engine optimization — adds surfaces a crawler-era site simply doesn't publish: machine-readable discovery files, typed knowledge, and an API an assistant can call. It takes nothing away from what you have.
Will our editors need new tools?
No. Your editors keep working in Xperience exactly as they do today. The knowledge types are ordinary Xperience content types, and everything downstream — the discovery files, the structured data, the JSON API, the MCP server — is generated from what they publish. Documenting that workflow for them is part of the engagement, not an afterthought.
What if our content model isn't structured?
Week 1 tells you. Discovery reviews the content model before anything gets built, and if what's there can't carry typed knowledge yet, I say so rather than building on it. Sometimes the honest answer is an Xperience Rescue Sprint or a readiness assessment first, and this package waits until the foundation is worth building on.
Is the MCP server ours?
Yes. It is published under your name, on npm and NuGet, under the MIT license, from a repository you own. You can keep releasing it after the engagement ends without me involved at all.
Standalone value—no obligation to hire Refined Element for implementation.