From a customer question to a useful result
Start with one question your customers ask and one useful next action. Your approved information and connected receiving system define what AICNCT can deliver.
One task, three steps
Find supporting information
Publish the sources customers may use. On an enabled task page, customers describe their needs and see relevant evidence and missing details.
Review and confirm
Show the exact request before sending. The customer confirms the action; access to a connector alone does not publish its contents.
Check the result
Match the receipt to the receiving system. Review requests needing attention and saved source checks when approved information changes.
Connection paths
WordPress and WooCommerce: install AICNCT Connect, pair the site from its workspace and check the connection. Enable only the capabilities you intend to offer. Shop actions depend on the installed plugin and site configuration.
Shopify: arrange a store-specific connection. Product selection and checkout handoff must pass validation before the store’s capabilities are activated.
Other websites and business systems: agree one workflow, approved sources and a supported destination. The hosted task page is optional. A new backend needs configuration and a successful end-to-end check.
Know what the evidence proves
An AICNCT agent test is a controlled model/tool run with the business supplied as context. It is not an observation of an ordinary consumer conversation in ChatGPT or another assistant.
A request receipt establishes delivery. A checkout link is not a paid order. Payment needs a separate backend confirmation; attribution alone does not prove an additional sale.
Publishing MCP and llms.txt makes technical information available. Verify discovery, directory availability and consumer-client journeys separately for the intended account, region, client version and enabled capabilities.
For assistant users and connector reviewers
Open the site-specific MCP URL shown in the owner workspace in a browser. Where enabled, its guide supplies setup instructions, guide.md, server-card.json and tools.json. Use the displayed URL: a site-domain /mcp route requires a working installation. Test with a labelled test destination, check the available tools and compare the returned reference with the receiving record. Keep credentials out of public pages.