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.
IFPydantic ValidationError when the LLM returns tool arguments as nested dicts instead of primitive strings.
THENCheck your tool function signatures: if a parameter expects a plain string but the model returns a dict (e.g., {'category': 'math'}), update the tool to unwrap the dict. For production, ensure your tool schemas clearly define expected types and consider post-processing the arguments before calling the tool.
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