> ## Documentation Index > Fetch the complete documentation index at: https://docs.getdedica.com/llms.txt > Use this file to discover all available pages before exploring further. # Review what Dedica found on your site > Approve, edit or dismiss the company profile, capabilities, agent tools and agent pages Dedica finds on your site. Only approved items reach AI agents. Dedica turns its analysis of your site into suggestions. During onboarding you confirm every one of them, and afterwards new suggestions wait as drafts on the **Review** page. The number next to **Review** in the menu shows how many are waiting, and the overview counts them by kind. Nothing is served to agents until a person approves it. ## What you review | Kind | What it is | | - | - | | Company profile | What Dedica understood your company does. Used in `llms.txt` and discovery files. | | Capabilities | Things visitors can do on your site. | | Agent tools | Actions agents can call through your [MCP server](https://docs.getdedica.com/serving/mcp-and-ask.md), such as a search, a quote or a checkout link. | | Pages for agents | Markdown versions of your pages that agents read. See [Agent pages](https://docs.getdedica.com/serving/agent-pages.md). | For each draft you can: * **Approve** it as it is. * **Edit** it, then approve your version. Fields you edit are never overwritten by later suggestions. * **Dismiss** it. The analysis won't suggest it again, but you can bring it back yourself from the **Agent View** page. You can also approve every draft of one kind at once, or approve everything. **Approve everything** asks you to confirm first and says how many drafts it approves. On the **Review** page, pick a kind on the left (or **All drafts**) to see just those drafts. During onboarding you can choose **Review later** on a step. Its drafts wait on the **Review** page until you review them. > [!TIP] > > Choose **Compare with the live page** on a page for agents to see exactly the markdown an agent will get, next to the page it came from. ## After you approve The **Agent View** page lists the items of each kind that aren't drafts. Pick a kind at the top (company profile, capabilities, agent tools or pages for agents), then **Live**, **Removed** or **Dismissed**. When a kind has drafts, Agent View links to them on the Review page. | State | What you can do | | - | - | | Live | **Edit** it, **Remove** it so agents stop getting it, or, for agent tools and pages for agents, **Turn off** to stop serving it without removing it. | | Turned off | **Turn on** to serve it again. | | Removed | **Restore** it. It goes live again. | | Dismissed | **Bring back as a draft** to review it again. | Every item also has a **History**: who or what changed it and when. Choose **Revert to this version** on an earlier entry to put that value back. To analyse your site again, for example after you changed it, choose **Analyse my site again** on the Agent View page. What the analysis finds arrives as drafts. You need the **owner** or **admin** role for this. ## Agent tools > [!WARNING] > > Approving an agent tool locks its name, because agents call it by name. You can edit a live tool's description or turn it off, but not rename it. Later analyses never rename an approved tool either. Dedica finds tools in your OpenAPI spec, your forms and, when JavaScript rendering is on, the JSON API calls your pages make when they load. When your site runs on a platform Dedica knows, it also suggests that platform's own public API as ready-made tools. It first makes one read-only request to check that the API answers. Today that covers **WooCommerce**: tools to search products, get a product, list product categories and list product reviews through the WooCommerce Store API, and a link that puts a product in the visitor's cart. These tools replace the product search box and add-to-cart forms, which would otherwise be suggested as separate tools. If your bot protection blocks the check, the tools are still suggested with lower confidence, but calls to them fail until you allow them through (see [What calls can reach](https://docs.getdedica.com/serving/mcp-and-ask.md#what-calls-can-reach)). Password and sign-in forms are never tools, and neither are forms your site submits with JavaScript only. A form that appears on many pages, such as a newsletter signup, is one tool. Agents fill in only the fields a visitor sees: hidden fields your form sends, such as a filter to products, go with every call unchanged, and spam traps are left out. Each tool is marked read-only or not, so agents know which calls change something. Tool calls are anonymous requests to your own domain. A tool that needs a signed-in user or a CSRF token usually fails, so dismiss it. When a tool's endpoint really changes, the review shows the old tool as removed and a new one added. Link them as the same tool to keep the old name and history. ## What is applied without review After onboarding, some changes don't wait for you: | Kind | Applied automatically | Waits for review | | - | - | - | | Crawled pages, `llms.txt` | Always | Never | | Agent tools | Never | Always | | Pages for agents | Updates to approved pages | New pages, removals | | Company profile, capabilities | First findings with high confidence | Changes to confirmed ones, removals | During onboarding, you confirm every finding. ## When changes reach agents Approved changes reach agents within about 60 seconds, not instantly. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.