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

elicitation_timeout

mcp-elicitation-timeout-elicitation-requests-timeout-within-2-3-seconds-ev-7d5b65d7

IFElicitation requests timeout within 2-3 seconds even with default 60s timeout when using a stateless MCP server.

THENImplement stateful server with session management for handling sampling/elicitation requests. Alternatively, ensure that the server maintains session state to avoid premature timeouts. The SDK provides a timeout parameter in the options, but this may not resolve the issue if the server is stateless.

Tier 170%

elicitation_timeout

mcp-elicitation-timeout-elicitation-requests-in-mcp-server-timeout-within--ef1bf6c6

IFElicitation requests in MCP server timeout within 2-3 seconds despite default 60-second timeout, causing MCP error -32001.

THENUpgrade to the latest SDK version that includes a timeout parameter in the options for elicitInput. However, even with the timeout parameter, the issue persists unless the MCP server is stateful with proper session management for sampling and elicitation requests.

Tier 170%

elicitation_timeout

mcp-elicitation-timeout-elicitation-requests-in-mcp-typescript-sdk-timeout-883f559c

IFElicitation requests in MCP TypeScript SDK timeout within 2–3 seconds despite the default 60-second timeout setting.

THENEnsure the MCP server is stateful and maintains session context for elicitation. If using a stateless server, implement session management or configure the server to handle elicitation requests persistently. Overriding the timeout option alone may not resolve the issue.

Tier 170%

elicitation_timeout

mcp-elicitation-timeout-elicitation-requests-for-tool-inputs-timeout-after-22a6cdb3

IFElicitation requests for tool inputs timeout after 2-3 seconds even though the SDK defaults to 60 seconds, when the server is stateless.

THENEnsure the MCP server is stateful and manages sessions properly for elicitation and sampling. If your server is stateless, implement session persistence or use a stateful middleware to maintain context across requests. Also verify that the `elicitInput` options parameter timeout is not inadvertently overridden to a low value.

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.