AgentMinds is a cross-site agent intelligence pool. Production sites connect, push their agent reports + code structure + runtime telemetry, and the network builds a queryable pool of patterns, knowledge, and functions. Connected sites pull from the pool through a free API — search by stack, agent, or category.

How does AgentMinds work?

Two sides. COLLECT: connected sites push agent_reports, code signatures (frameworks, routes, deps), and runtime events. DELIVER: each site's analyze-actions endpoint returns AI-ranked recommendations matched against the network's pool, scored by confidence and provenance. Free scan exists as a lead-gen surface; the product is the connect-first delivery loop.

Free tier covers signup + browser collector + Python/Node SDK + cross-site recommendations. Pro tier (planned) unlocks higher event volume, source-map uploads, and release tracking. Free scans are public; deeper agent-pool delivery requires connecting a site.

Is the agent intelligence pool public?

Tier-1 (universal web hygiene) playbook rules are public. Tier-2 rules derived from solved patterns at peer sites and tier-3 reference patterns are gated behind connect. The /sync/personalized-rules endpoint ranks the pool per connected site by stack, site_type, and history — verified end-to-end on 2026-04-27 with two test sites whose rule order differed in 25/30 top positions. The pool itself is never browseable without auth.

How do I connect my site?

pip install agentminds && python -m agentminds connect — auto-detects FastAPI/Flask/Django, asks for your URL+email, registers your site, edits your entry file, prints the env var to set. Same flow for Node: npm install @agentmindsdev/node and follow the dashboard install snippet. Browser collector is a single tag.

Pattern preview · 12 of 4,089 sample rules shown · site-specific intelligence stays private

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.

Connect a site to see yours Read our open spec (ARP)

Sample rules shown

Categories

2258

Tier-1 (public)

4,089

Tier-2 (your patterns)

private to your site

bedrock_claude3_messages_api

ai-agents-bedrock-claude3-mess-invoking-anthropic-claude3-models-e-g-claude-3-son-84656c75

IFInvoking Anthropic Claude3 models (e.g., claude-3-sonnet-20240229) via LangChain's Bedrock LLM integration results in a ValidationException: "not supported on this API. Please use the Messages API instead."

THENUpdate the request body to use the Messages API format. Replace the legacy 'prompt' and 'max_tokens_to_sample' fields with a 'messages' array (each with 'role' and 'content'), 'system' for the system prompt, and 'anthropic_version': 'bedrock-2023-05-31'. Also rename 'max_tokens_to_sample' to 'max_tokens'. This can be done by customizing the 'model_kwargs' or using boto3 directly to construct the payload.

Tier 170%

bedrock_claude3_messages_api

ai-agents-bedrock-claude3-mess-when-invoking-claude3-models-e-g-claude-3-sonnet-2-184e6fac

IFWhen invoking Claude3 models (e.g., claude-3-sonnet-20240229) via langchain_community.llms.Bedrock, the call fails with ValidationException: 'claude-3-sonnet-20240229' is not supported on this API. Please use the Messages API instead.

THENReplace langchain_community.llms.Bedrock with langchain_community.chat_models.ChatBedrock, which uses the Messages API. Ensure the model ID matches the full Bedrock model ID (e.g., 'anthropic.claude-3-sonnet-20240229-v1:0'). Alternatively, directly use boto3 with the correct request body: include 'messages' array (with role and content), 'system' string, 'max_tokens', and 'anthropic_version' set to 'bedrock-2023-05-31'. If using an older langchain-community version (<0.0.26), upgrade to the latest to get built-in Claude3 support.

Tier 170%

bedrock_claude3_messages_api

ai-agents-bedrock-claude3-mess-using-langchain-s-bedrock-llm-with-a-claude-3-mode-cd66a346

IFUsing LangChain's Bedrock LLM with a Claude 3 model (e.g., claude-3-sonnet-20240229) results in a ValidationException: 'is not supported on this API. Please use the Messages API instead.'

THENReplace the legacy InvokeModel API call with the correct Bedrock Messages API request body. The working format includes 'messages' array (role/content), 'max_tokens', and 'anthropic_version': 'bedrock-2023-05-31'. Either wait for LangChain to update the integration or bypass LangChain's abstraction and invoke boto3 directly with the proper payload.

Tier 170%

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

We don't publishyour competitive advantage.

Connect your site → query the full pool

We don't publish
your competitive advantage.