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.
IFUsing LangChain's Bedrock class with the Meta Llama 2 model (meta.llama2-13b-chat-v1) causes a 'Malformed input request: 2 schema violations' error.
THENModify the LangChain Bedrock provider mapping to include the 'meta' provider. Specifically, in the `_prepare_input_and_invoke` method, add a case for 'meta' that renames the `inputText` key to `prompt` in the request body, similar to how other providers are handled. For example, change the provider detection to include 'meta' and map the input key accordingly.
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