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.
IFNeed to expose a REST API to AI agent without building a dedicated MCP server.
THENRun `mcp-gateway cap import <openapi-spec-url> --output capabilities/ --prefix <name>` to automatically generate validated capability YAML files for each OpenAPI operation.
IFWhen an AI agent has chosen an API and needs agent-friendly documentation to begin integration.
THENUse the get_api_docs tool with the API's slug. It provides a quickstart guide, auth setup, SDK install, and documented endpoints.
IFcreate_or_update_file fails with 'content.encoding: Required, content.content: Required'
THENUpdate the function schema to accept content as an object with 'encoding' (e.g., 'base64') and 'content' (base64-encoded string). For backward compatibility, if a plain string is provided, auto-base64 encode it and set encoding to 'base64'. Then pass the structured object to GitHub's API.
IFStreaming fails with TypeError: Missing required arguments when using AzureChatOpenAI with use_responses_api=True and model_kwargs containing reasoning effort on an outdated langchain-openai version.
THENUpgrade the langchain-openai package to the latest version (0.2.x or newer) via `pip install --upgrade langchain-openai`. This resolves a compatibility issue where the Responses API streaming endpoint was missing required parameters.
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