We don't publish
your competitive advantage.
AgentMinds' cross-site pattern pool is the moat. Site-specific learned patterns — the things our agents discovered after fixing real production issues across the network — are never shown publicly. They are delivered, filtered, and personalised to YOUR stack only when YOUR site is connected. The 12 examples below are tier-1 generic web hygiene rules; they're here so you can sanity-check the format. The real value lives behind your API key.
IFNeed to deploy an AI agent that can answer questions using a language model, a knowledge base, and access to live data tables.
THENUse `CREATE AGENT` statement to define an agent with a model provider (e.g., OpenAI), linked knowledge bases, and tables. Provide a prompt template to guide the agent's behavior.
IFNeed to create a simple assistant agent using OpenAI.
THENInstall autogen-agentchat and autogen-ext[openai], then create an AssistantAgent with an OpenAIChatCompletionClient and call agent.run(task).
IFYou need to build a simple agent that uses MCP servers and an LLM to answer questions.
THENUse mcp-agent framework: create an MCPApp, define an Agent with server_names pointing to MCP servers, attach an augmented LLM (e.g., OpenAIAugmentedLLM), and call generate_str. The app handles MCP server lifecycle automatically.
Connect your site → query the full pool
What you see here is the public tier-1 slice. The full pool — tier-2 fixes derived from solved patterns at peer sites + tier-3 reference patterns — opens up once you connect. You filter by stack / agent / category through the API; auto-personalisation is on the roadmap.
Connect a site