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.
IFSSE transport relies on in-memory session storage, causing 400 errors when serverless instances route POST /messages to a different instance than the initial GET /sse.
THENMigrate from SSE transport to Streamable HTTP with stateless mode. In the TypeScript SDK, use the default `StreamableHTTPServerTransport` without explicit session management, or call `transport.start()` without a session callback when only stateless operation is needed. This avoids per-session in-memory state and works across serverless instances.
IFMCP server deployed in a serverless environment (e.g., AWS Lambda, Cloudflare Workers) using the stateful SSE transport fails because subsequent POST /messages requests may land on different instances that lack in-memory session state.
THENMigrate from the SSE transport to the Streamable HTTP transport, which supports stateless mode and external session persistence. Alternatively, enable the stateless mode in the SDK. This ensures requests can be handled by any instance without requiring shared memory.
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