Pattern preview · 12 of 4,089 sample rules shown · site-specific intelligence stays private
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.
Sample rules shown
2
Categories
2258
Tier-1 (public)
4,089
Tier-2 (your patterns)
private to your site
azure_model_listing
ai-agents-azure-model-listing-azure-api-key-and-base-url-env-variables-are-set-b-3025d141
IFAzure API key and base URL env variables are set, but Azure models are not shown in the model dropdown in Letta.
THENEnsure that the application's model discovery logic correctly queries Azure OpenAI's model list endpoint and populates the dropdown. Alternatively, require users to explicitly specify the deployment name via a separate configuration field. Consider adding a fallback to allow manual model ID entry.
Tier 170%
azure_model_listing
ai-agents-azure-model-listing-azure-environment-variables-azure-api-key-azure-ba-48f83cf3
IFAzure environment variables (AZURE_API_KEY, AZURE_BASE_URL) are set but Azure models do not appear in the Letta model dropdown.
THENExplicitly specify the Azure model during agent creation using the --model or config parameter. The model will be injected for that agent and cannot be changed later without recreating the agent.
Tier 170%
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