Why these examples are different
The agents below are not composites or aspirations. They are the twelve roles a fresh Ahel install ships with, copied from the seed catalog: the same job descriptions, the same action lists. That matters because the action list is the agent. “An agent that handles your marketing” tells you nothing; “an agent that may call brave.web and three other search actions, and nothing else” tells you exactly what it can and cannot do.
If you have not read a definition yet, what is an AI agent covers the anatomy these examples share: a role, a model, named actions, missions with done-states, and a receipt per run.
Research agents
The most broadly useful cluster. Each of the three holds a different rung of the same ladder: search results, page text, and full browser sessions for the sites that fight back.
Finds it, then reads it: a vague reference becomes concrete URLs and page text.
brave.web · brave.site · brave.news · brave.llm_context
Turns a question or a URL into readable page text, past the bot walls that break plain fetch.
browserbase.search · browserbase.fetch_page · browserbase.fetch_raw · browserbase.fetch_proxied
Hands a multi-step browser job to a cloud browser session, then babysits it to an answer.
browserbase.agent_run · browserbase.run_status · browserbase.run_messages · browserbase.run_stop
The division of labor is deliberate. The Web Researcher answers “where is it?”; the Page Researcher answers “what does it say?”; the Browser Operator exists for jobs that need an actual browser walking through pages. One agent with all three jobs would be vaguer at each — narrow roles are easier to check.
Search and SEO agents
Two roles on one provider, split by question size: the whole-domain picture versus a single lookup.
Whole-domain SEO picture: traffic, keywords, competitors, backlinks — on a prepaid meter.
dataforseo.domain_overview · dataforseo.ranked_keywords · dataforseo.competitors · dataforseo.keyword_gap · dataforseo.backlinks_summary
Where a keyword, page, or domain stands in Google right now — one lookup per question.
dataforseo.serp_organic · dataforseo.keyword_suggestions · dataforseo.page_audit
Note the phrase on a prepaid meter in the SEO Analyst’s job description — it is part of the seed data because cost behavior belongs in a job description. An agent that spends money should say so where the operator hires it, not surprise them in an invoice.
Infrastructure agents
Agents that watch the machinery a small team runs but rarely looks at: DNS, edge traffic, and the cloud-browser account that quietly accumulates sessions.
Is a domain wired up correctly, and does the edge config match what the internet resolves?
cloudflare.zones · cloudflare.dns_records · dns.resolve
How a site is doing at the edge — volume, cache hits, 5xx, and who is getting blocked.
cloudflare.traffic · cloudflare.firewall_events · cloudflare.zone
The few irreversible edge changes: purge a cache after a deploy, add a verification TXT record.
cloudflare.purge_urls · cloudflare.purge_host · cloudflare.dns_add_txt
What is still running on the cloud-browser account and what it has cost — and kills orphaned sessions.
browserbase.sessions_list · browserbase.project_usage · browserbase.session_release
The Edge Operator is the interesting one: it is the only role in this group allowed to change anything, and its powers are exactly the few changes that are safe to delegate — purging a cache, adding a TXT record. Reads and writes live in separate roles on purpose, so “look at the traffic” can never drift into “change the config.”
Security agents
Three roles that turn security feeds into a verdict a person can act on.
Given a CVE or a product name, says whether you have to act on it today.
cvedb.cve · nvd.cve · epss.score · cvedb.kev_new · cvedb.product
An IP, domain, URL, or file hash out of a log — is it known-bad, and what is it actually?
threatfox.ioc · threatfox.hash · urlhaus.recent · shodan.host
What is exposed on a host or domain, and how large a footprint looks from outside.
shodan.dns_resolve · shodan.host · shodan.search · shodan.domain · shodan.count
The Vulnerability Analyst ships with its rubric written into the role: known-exploited or a high exploit-probability score means act now; a critical severity score with a negligible exploit-probability means schedule it; anything else is note only. It is also required to name the field a verdict was based on, and to say when a lookup missed rather than guess. That last instruction is the difference between an agent you can use and an agent you have to babysit.
What backs them: any model you connect
One thing the roster deliberately does not specify is a model. A role is model-agnostic: the same Web Researcher runs on whichever provider lane you connect — an Anthropic key, an OpenAI key, an OpenRouter key — because the role contributes the job description and the action list, and the model contributes the judgment. That split is what keeps the examples durable: when a better model arrives, the roster does not change, the work just gets sharper.
It also keeps the economics readable. The agents run on keys you already pay for, at the provider’s own prices; the platform is not reselling tokens to you with a margin hidden inside an “agent fee.” Where a role can spend real money — the SEO Analyst’s metered lookups, the Browser Operator’s cloud sessions — the roster says so up front, and the Session Auditor exists precisely to watch one of those meters.
The pattern worth copying
Read the twelve as one dataset and a few rules fall out — useful whether you run them in Ahel or build your own:
- A job description is one sentence. If the role needs a paragraph, it is two roles.
- Actions are enumerated, not implied. Every capability has a name you can read before the agent ever runs.
- Reading and changing are different jobs. Eleven of the twelve can only look things up; the one that can make changes holds the shortest, most explicit list.
- Honesty is written into the role.“Say it missed” beats a confident guess every time the answer matters.
These twelve are the seed roster, not the ceiling — the agent directory carries the job titles a workforce can hire across seven sectors, and the use-case library shows the same roles placed against real weekly work. The providers behind the actions — search, SEO data, edge, cloud browsers, security feeds — are listed on integrations.