Current limitations of Dedica

Dedica is in active development. This page lists what it doesn’t do yet, so you can plan around it. It changes as features ship.

Serving

In autopilot, Dedica’s llms.txt replaces one your site already publishes.
Once an agent tool is approved, Dedica’s /mcp replaces any /mcp your site already had.
Approved changes reach agents within about 60 seconds, not instantly.

Tool calls are anonymous. Endpoints that need a signed-in user, and forms protected by a CSRF token, usually fail.
The dashboard doesn’t show a tool’s arguments, and you can’t test-call a tool before approving it.
A live tool can’t be renamed, because agents call it by name. Turn it off instead.
Dedica only finds API calls a page makes when it loads. Calls a widget makes after the visitor types something aren’t found.
Ready-made platform tools cover WooCommerce only. WooCommerce tools can’t manage a cart or check out, because those calls need a session kept between calls; agents get an add-to-cart link instead. WooCommerce sites without pretty permalinks (no /wp-json/) aren’t recognised yet.

Dedica doesn’t alert you when your middleware stops sending heartbeats. The overview shows it as not connected.
Apart from sign-in codes and invitations, Dedica doesn’t send email, for example when an analysis finishes or new drafts arrive.
The Viewer role can’t be assigned from the Team page. Contact Dedica to make someone a viewer.

Your site isn’t re-analysed automatically. Choose Analyse my site again on the Agent View page to run a new analysis.
Competitor research isn’t available.

Agent traffic analytics.
Guardrails: blocking agents, route rules, rate limits and per-agent tool permissions.
Bot identity verification (IP ranges, Web Bot Auth).
Tokens for your own scripts. Agents connect to Dedica’s MCP server with OAuth, but there is no way yet to get a token for calling the REST API directly.
Single sign-on (SSO) with your company’s identity provider.