Cointacted is a WordPress-first product ecosystem. It adds frontend commands, site building and management, conversational AI, MCP, automation, ecommerce, community, wallet, and Web3 capabilities through focused add-ons.

No. WordPress remains the system of record for users, roles, content, settings, permissions, and plugin data. Cointacted extends those systems rather than moving them into a closed platform.

Social Terminal is the open-source core: an in-browser command interface for member actions, administrator tasks, and workflows exposed by installed Cointacted add-ons.

Cointacted add-ons are built around the shared core. Each add-on page and its documentation identify any additional dependency, integration, or configuration it needs.

Yes. The system is designed to be introduced incrementally: install the core, connect an account when needed, and add one capability at a time. Test sensitive workflows on staging first.

No. Members and site owners can use focused frontend experiences, while developers can extend commands, hooks, adapters, integrations, and MCP tools when deeper customization is required.

Cointacted AI lets members and administrators communicate with the website from the frontend. Approved requests can become controlled WordPress actions instead of remaining a separate chatbot conversation.

Frontend AI is the on-site conversation experience. MCP exposes selected Cointacted tools to compatible external assistants, allowing those assistants to work through explicitly defined actions and permissions.

No. Only actions intentionally exposed by the site and enabled add-ons should be available. WordPress roles, Cointacted permissions, add-on settings, and tool definitions remain authoritative.

No. Wallet and Web3 capabilities are optional. A site can use Social Terminal, SnapWeb, AI, MCP, search, community, ecommerce, and other add-ons without requiring every user to connect a wallet.

Depending on the add-on, Web3 workflows can include wallet identity, network detection, balances, signatures, transactions, contract calls, events, and chain-aware WordPress actions.

No private key should be entered into Cointacted or WordPress. Wallet connections are designed around user-controlled wallets such as MetaMask and WalletConnect, with signing handled by the wallet.

Yes. A workflow can require a WordPress role, a specific Cointacted permission, an account state, a connected wallet, or a combination of those checks before an action is available.

Commands and tools can be restricted through WordPress roles, Cointacted permissions, add-on settings, connected-account state, and optional wallet checks. The site decides which actions are exposed.

Only when the site has explicitly granted the required permission. Moving an interface to the frontend does not bypass WordPress roles, capabilities, or Cointacted access rules.

That depends on the provider, enabled add-on, selected tools, and workflow configuration. The site owner should expose only the context required for the action and review the provider-specific documentation.

No. MCP should expose only defined tools and their approved inputs. It is a controlled interface for selected capabilities, not unrestricted access to WordPress.

Yes, especially when an add-on can change accounts, content, orders, payments, permissions, wallets, or external systems. Confirm roles, error handling, and rollback paths before production use.

Start with the documentation for installation, commands, integrations, AI, MCP, and Web3. Use the Contact page for product questions, compatibility discussions, partnerships, or unresolved support needs.

Use the Contact page and clearly mark the message as a security report. Do not publish sensitive technical details before the issue has been reviewed.