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 router with multiple model entries that specify different aws_region_name, the endpoint URL for /converse is assembled using the default AWS region from boto3 credentials instead of the per-model region, resulting in a 400 error: 'The provided model identifier is invalid.'
THENSet the AWS_DEFAULT_REGION environment variable in the container to one of the regions used in the model config (e.g., us-east-1) to override the boto3 default. Alternatively, upgrade LiteLLM to a version where this bug is fixed; as a temporary workaround, ensure all models in the router share the same region if inference profiles are used.
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