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 the Bedrock LLM class with 'meta.llama2-13b-chat-v1' model, a 'Malformed input request: 2 schema violations found' error occurs.
THENUpdate the Bedrock integration to specifically handle the 'meta' provider. In the `_prepare_input_and_invoke` method, for the 'meta' provider, use 'prompt' as the input key instead of 'inputText' (used by other providers). Also ensure the `stop_sequences` key is omitted if unsupported. Upgrading to langchain >=0.0.336 may be insufficient; manual code patching is required until the fix is merged.
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