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 Claude 4.5 Sonnet via AWS Bedrock with the /v1/chat/completion endpoint, requests fail with 400 error: 'aws_access_key_id: Extra inputs are not permitted' or 'aws_role_name: Extra inputs are not permitted'.
THENRemove aws_access_key_id, aws_role_name, and similar extra fields from the model configuration for Bedrock. Instead, use an inference profile ARN (e.g., 'eu.anthropic.claude-sonnet-4-5-20250929-v1:0' or 'global.anthropic.claude-sonnet-4-5-20250929-v1:0') and set AWS credentials globally via environment variables or provider-level config. The /v1/messages endpoint works normally as an alternative.
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