Skip to main content
Each site has a serving mode that tells the middleware what to do. The middleware reads it from Dedica about every 30 seconds, so a change takes effect without redeploying anything. In both modes, people, browsers and search engines always get your normal pages.

​
Switch modes

Once your middleware is connected, an owner or admin turns serving on from the overview with Turn on serving, and off again with Turn off serving. After you turn serving on, Dedica checks that agents really get your content. It fetches /llms.txt and one of your agent pages from your domain the way an agent would, and compares them with what it serves. The check repeats every 10 seconds for about two minutes, because the middleware picks up the change within about 30 seconds. If a path doesn’t match, the overview says why: Once every path matches, the overview says You’re live. Choose Check again at any time to rerun the check. An AI agent connected to Dedica’s MCP server can also change the mode, if your role allows it.

​
What autopilot replaces

In autopilot, Dedica’s llms.txt replaces one you already publish. Once an agent tool is live, Dedica’s /mcp replaces any /mcp your site already had.
Discovery files such as /openapi.json and /.well-known/ard.json are different: if your site already serves the file, yours wins.