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.
IFWhen using Azure OpenAI GPT-5 or similar o-series models, passing 'max_tokens' parameter causes a BadRequestError indicating it is unsupported.
THENReplace 'max_tokens' with 'max_completion_tokens' in your LiteLLM configuration or API calls. Define the model in the model_list with the appropriate deployment name, e.g., model: azure/gpt-5/my-random-deployment-name, and ensure the api_base and api_key are set.
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