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.
IFDeciding whether to use a single Claude API call, a workflow with tool use, or Managed site_1.
THENStart simple: use single API calls for classification, summarization, extraction, Q&A. Use workflow (API + tool use) for multi-step pipelines you orchestrate. Use Managed site_1 only when you want Anthropic to run the agent loop and host a container for tool execution. Check if deploying via third-party provider (Bedrock/Vertex/Foundry) — if so, Managed site_2 is unavailable; use Claude API + tool use for all agent needs.
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