A Google search your agent can actually run.
Serper is a data and sourcing tool, and one of the 52 tools hyreflow connects to Claude, ChatGPT and other AI assistants. Through hyreflow, an AI agent can run 9 actions, all of which look something up. Paid Serper actions cost 0.1 credits per request, from your hyreflow credit balance, so you need no Serper account, though you can connect your own key.
Serper gives the agent live Google results: web, news, maps and local business listings. It is the fastest way to check a fact, find a company's real domain, or pull local firms in a city before anything expensive runs.
Serper is cheap recall at the front of the pipeline. It narrows things down before a credit-costing tool touches them.
With hyreflow connected, you ask for the outcome in plain language and the assistant runs Serper for you. For example:
In a hyreflow run, Serper is most often paired with Shovels, Lusha, Exa and Firecrawl.
Through hyreflow, an AI agent can run 9 Serper actions, all of which look something up. Paid Serper actions cost 0.1 credits per request, from your hyreflow credit balance, so you need no Serper account, though you can connect your own key.
| Serper action | What it does | Cost through hyreflow |
|---|---|---|
| Scrape | Looks something up | 0.1 credits per request |
| Search | Looks something up | 0.1 credits per request |
| Autocomplete | Looks something up | 0.1 credits per request |
| Images | Looks something up | 0.1 credits per request |
| Maps | Looks something up | 0.1 credits per request |
| News | Looks something up | 0.1 credits per request |
| Places | Looks something up | 0.1 credits per request |
| Reviews | Looks something up | 0.1 credits per request |
| Scholar | Looks something up | 0.1 credits per request |
One credit is priced on the pricing page. The full price list for every tool is in the pricing tables.
39 hyreflow skills call Serper as part of the run. A skill is a whole pipeline your agent already knows, end to end.
use whenyou have a spec and want search strings you can paste into LinkedIn, Google or your ATS, without hand-typing forty title variants
use whenyou know exactly which firms to take people from, and which firms must never be touched
use whenyou are sourcing in a German-speaking market and the search returns fewer people than you know are there
use whena company's own team page already lists the people you want, and the databases hardly know the firm exists
use whenan industry event has published its speakers and the people on stage look like the hire your client wants
use whenyou are opening a new market or a new desk and need to know which companies are even worth calling
hyreflow ships a written playbook for Serper, and the agent loads it before the first call. Auth, rate limits, what each call costs, which actions need your approval, and the mistakes worth avoiding. It is the difference between an agent that knows the tool and one that guesses at it.
Read the Serper docs →HOW in lib/serper.py. Cheap, fast Google recall — strong first step before structured extraction/enrichment.
https://google.serper.dev · Scrape base: https://scrape.serper.dev · Auth: header X-API-KEY (env SERPER_API_KEY; never hardcode).{q, gl, hl, num, page, location, tbs, autocorrect}.search, news, images, places (local businesses), maps, scholar, reviews, autocomplete, scrape(url). Anything else → generic request().
Discovery/recall layer. Use search/places/maps to find companies/people/signals, scrape to pull a page → hand to enrichment (Apollo/Lusha/…) or research. Note: places/maps cover the "Google Maps" use case for local sourcing.
Field-shape note: these are vendor-native operational notes. The client returns the raw vendor JSON and uses the method names in this file — read field shapes accordingly (no normalized-wrapper /
result.data.prefix).
search for broad web research, newsy/changing facts, finding an entity before enrichment, or collecting candidate URLs to hand to extraction. maps for local business discovery, location-aware lookups, and phone/address/rating/website/CID retrieval.lib/serper.pyImport: from lib.serper import Serper → instantiate Serper() (reads key from env). Base: https://google.serper.dev. Generic passthrough: request(method, path, *, params, json).
autocomplete(query: str, **opts) -> dictimages(query: str, **opts) -> dictmaps(query: str, **opts) -> dict — POST /maps — Google Maps results.news(query: str, **opts) -> dictping() -> dict — Key-verification probe. Serper has no free account endpoint, so this fires the cheapest real query (1 result) to confirm the key authenticates — it spends ~1 Serper credit on whichever account the key belongs to (hyreflow charges 0).places(query: str, **opts) -> dict — POST /places — Google Places results (local businesses).reviews(query: str, **opts) -> dictscholar(query: str, **opts) -> dictscrape(url: str, *, include_markdown: bool = True) -> dict — POST scrape.serper.dev — fetch & parse a web page (text/markdown).search(query: str, **opts) -> dict — POST /search — Google web search. opts: gl, hl, num, page, location, tbs, autocorrect.Yes. hyreflow is a connector for Claude, ChatGPT and other AI assistants. Once hyreflow is connected, you ask for the outcome in plain language and the assistant calls Serper for you. hyreflow exposes 9 Serper actions this way.
No. hyreflow holds the Serper account and bills each action from your hyreflow credits. If you already pay for Serper, you can connect your own key instead, and hyreflow then charges no credits for those calls.
Paid Serper actions cost 0.1 credits per request, from your hyreflow credit balance, so you need no Serper account, though you can connect your own key. hyreflow can show the cost of a paid action before it runs.
Add the hyreflow MCP server to your assistant and sign in. hyreflow calls the Serper API directly and exposes its actions as tools the assistant can run, so there is no separate Serper server to install.
Connect hyreflow to Claude or ChatGPT and ask for the outcome. It reads the playbook above before it makes a single call.