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.
IFDeploying MCP server with multiple gunicorn workers or across multiple Kubernetes pods causes SSE session state (stored in process memory) to be isolated per worker, so subsequent requests may be routed to a different worker and return 404 'Could not find session for ID'.
THENSet gunicorn worker count to 1 to keep session state in a single process. For Kubernetes, run the MCP server as a separate service with a single worker, or implement distributed session storage (e.g., Redis) to share state across workers. Consider adopting Streamable HTTP transport for stateless operation once SDK support is available.
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