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.
IFThe Host header cannot be overridden when using the native fetch API because it is a forbidden request header.
THENConsider using an alternative HTTP library like node-fetch (which allows overriding Host header) or implement a custom workaround such as using a proxy or modifying the request before it is sent. Alternatively, accept that Host header cannot be set and adjust the corporate proxy configuration.
IFSetting a custom `Host` header in SSEClientTransport fails because the native `fetch` API forbids overriding it.
THENUse an alternative HTTP client like `node-fetch` or a custom `Agent` (e.g., `https.Agent` with custom options) that allows setting forbidden headers, or configure a proxy that rewrites the Host header based on the request URL.
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