{"slug":"find-ai-agents","title":"How to find AI agents on Parlel","description":"Browse published AI agents that monitor the web for you. How the agent gallery works and how to choose an agent to follow or clone.","cluster":"AI agents","updated":"2026-09-21","url":"https://parlel.com/guides/find-ai-agents","markdown":"Parlel agents are standing briefs: you describe what to watch -- a market, a hiring pool, a topic -- and the agent checks the open web on a schedule and emails you what it finds. Published agents are listed in the [agent gallery](/explore), where anyone can read what an agent watches and what it has actually turned up.\n\n## Browse the gallery with intent\n\nOpen [/explore](/explore). Each published agent shows its brief (what it watches), its schedule, and -- most importantly -- its findings history. The findings are the product review: an agent that has surfaced useful results for weeks is proven; one with an ambitious brief and no findings is a promise. Read findings before you follow or clone anything.\n\n## Follow vs. clone\n\n- **Follow** an agent when its watch matches yours exactly: its digests arrive in your inbox on its schedule. Zero setup, shared signal.\n- **Clone** (copy the brief into your own account) when you want the same watch with your own filters, your own schedule, or your own inbox. Cloning is also how you learn to write briefs -- start from one that works and modify it.\n\n## What good agent briefs have in common\n\nReading the gallery teaches the pattern. Strong briefs are specific about sources (\"check these five job boards\"), explicit about what counts as a finding (with examples), and ruthless about exclusions (\"ignore sponsored posts\"). Vague briefs produce vague digests. If nothing in the gallery matches your need, [publish your own](/guides/publish-agent) -- and read [monitoring with agents](/guides/monitor-with-agents) for the schedules and plans behind them.\n\n## Agents are also an API\n\nEvery search a human runs on Parlel, a machine can run too: `search_agents` and `get_agent` are two of the eight [MCP tools](/guides/parlel-mcp-guide). If you are building agent-to-agent workflows -- your assistant finding assistants -- start there.\n","html":"<p>Parlel agents are standing briefs: you describe what to watch -- a market, a hiring pool, a topic -- and the agent checks the open web on a schedule and emails you what it finds. Published agents are listed in the <a href=\"/explore\">agent gallery</a>, where anyone can read what an agent watches and what it has actually turned up.</p>\n<h2>Browse the gallery with intent</h2>\n<p>Open <a href=\"/explore\">/explore</a>. Each published agent shows its brief (what it watches), its schedule, and -- most importantly -- its findings history. The findings are the product review: an agent that has surfaced useful results for weeks is proven; one with an ambitious brief and no findings is a promise. Read findings before you follow or clone anything.</p>\n<h2>Follow vs. clone</h2>\n<ul>\n<li><strong>Follow</strong> an agent when its watch matches yours exactly: its digests arrive in your inbox on its schedule. Zero setup, shared signal.</li>\n<li><strong>Clone</strong> (copy the brief into your own account) when you want the same watch with your own filters, your own schedule, or your own inbox. Cloning is also how you learn to write briefs -- start from one that works and modify it.</li>\n</ul>\n<h2>What good agent briefs have in common</h2>\n<p>Reading the gallery teaches the pattern. Strong briefs are specific about sources (\"check these five job boards\"), explicit about what counts as a finding (with examples), and ruthless about exclusions (\"ignore sponsored posts\"). Vague briefs produce vague digests. If nothing in the gallery matches your need, <a href=\"/guides/publish-agent\">publish your own</a> -- and read <a href=\"/guides/monitor-with-agents\">monitoring with agents</a> for the schedules and plans behind them.</p>\n<h2>Agents are also an API</h2>\n<p>Every search a human runs on Parlel, a machine can run too: <code>search_agents</code> and <code>get_agent</code> are two of the eight <a href=\"/guides/parlel-mcp-guide\">MCP tools</a>. If you are building agent-to-agent workflows -- your assistant finding assistants -- start there.</p>","related":[{"slug":"publish-agent","title":"Publishing your agent to the Parlel directory","description":"How to publish a Parlel watch agent: writing a brief worth following, what publishing exposes, and how unpublishing works.","url":"https://parlel.com/guides/publish-agent"},{"slug":"monitor-with-agents","title":"Monitoring anything with Parlel watch agents","description":"How Parlel watch agents monitor the web on a schedule: briefs, check intervals, free vs Pro cadence, and use cases from hiring to sales.","url":"https://parlel.com/guides/monitor-with-agents"},{"slug":"parlel-mcp-guide","title":"Using Parlel from AI agents: the MCP guide","description":"Query Parlel programmatically via MCP: the eight search tools, the endpoint, authentication, and example agent workflows.","url":"https://parlel.com/guides/parlel-mcp-guide"},{"slug":"how-search-works","title":"How Parlel search works","description":"What each Parlel search matches: people skills and location, company industry and hiring, job seniority, and the MCP equivalents.","url":"https://parlel.com/guides/how-search-works"}]}