Which search engines can Lyro query through Zenserp?

Google, Bing, and Yandex each have their own action, and List Search Engines returns the supported engine domains so a query can be aimed at the right one. Google also has the extra endpoints - Shopping product detail, Trends, and reverse image search - that the other engines do not expose here.

Why does Lyro look up country and language codes before running a search?

Google expects gl and hl parameters plus a supported location string, not plain country names. List Countries, List Supported Languages, and List Locations return the valid values, which is what stops a market-specific search from quietly returning default results.

Can Lyro submit a batch of searches?

It can report on batches but not create them. List Batches returns the batches already submitted under your API key with their processing status and history, while the searches Lyro runs itself go through the single-query actions.

How do we avoid running out of Zenserp requests mid-task?

Get API Status returns the requests remaining on the connected API key. Checking it before a broad sweep - several markets, several engines - lets Lyro report the budget up front rather than stopping halfway through with partial data.

Zenserp MCP integration

Runs Google, Bing, and Yandex searches scoped to a market, pulls Shopping product detail and Trends data, and reports remaining API quota.

Connect Zenserp See all integrations

12actions available

Three actions you can hand over today

Every action runs live through MCP. Nothing to build, nothing to maintain.

Zenserp google search
Lyro performs Google searches via Zenserp to fetch current web results for customer questions. Support teams access real-time information directly in conversations.
Google trends
Lyro retrieves Google Trends data to show customers what searches are trending around topics. Agents provide context on search popularity without external tools.
Get shopping product details
Lyro retrieves detailed product information from Google Shopping results. Support agents answer pricing and availability questions with structured product data.

See all 12 actions

How businesses use Zenserp + Lyro

Each card is one request a support team gets, and the Zenserp actions Lyro runs to close it.

Pull structured results from the engine that matters
Lyro queries Google, Bing, or Yandex through Zenserp and gets parsed SERP data back, checking the supported engine domains first when the market uses something other than Google.
Zenserp Google SearchBing SearchYandex Search via ZenserpList Search Engines
Point a search at one specific market
Lyro resolves the valid country, interface language, and geo location parameters before searching, so results reflect what a customer in that market sees rather than a default ranking.
List CountriesList Supported LanguagesList Locations
Answer a demand or product research question
Lyro compares keyword popularity over time, opens a Google Shopping product page for its full detail, and runs a reverse image search to find where a picture already appears online.
Google TrendsGet Shopping Product DetailsGoogle Reverse Image Search
Keep batch jobs and quota in view
Lyro lists the batches submitted under the API key with their processing status and reports how many requests the key has left before a large sweep starts.
List BatchesGet API Status

How it works

Get started in 3 steps

Connect once, then just ask. There is no workflow builder to learn and nothing to maintain — Lyro reads the Zenserp actions it has and picks the ones a request needs.

01
Connect Zenserp
Authorize the Zenserp account your team already uses — one consent screen, no API keys, no mapping tables. Lyro can only do what you granted that account, and you can disconnect it at any time.
02
Tell your agent what you need
Describe the job the way you would hand it to a teammate. Lyro maps it to the Zenserp actions that close it and chains as many as the request needs.
03
Watch it work
The agent runs the actions inside the conversation the customer is already in, so nobody copies data between tabs and your team can take over at any point.
Get started free

Zenserp · Lyro

Everything else about Zenserp

Setup, permissions, and the limits of what Lyro can do inside Zenserp.

Google, Bing, and Yandex each have their own action, and List Search Engines returns the supported engine domains so a query can be aimed at the right one. Google also has the extra endpoints - Shopping product detail, Trends, and reverse image search - that the other engines do not expose here.

Every action available in Zenserp

All 12 actions your agent can call on Zenserp, straight from the live MCP connection.

Bing search
Obtain Bing search results.
Get shopping product details
Retrieve detailed Google Shopping product page information by product_id.
Get API status
Check the remaining API requests for your API key.
Google reverse image search
Perform a reverse image search on Google.
Zenserp google search
Perform a standard Google search via Zenserp.
Google trends
Retrieve Google Trends data.
List batches
List all submitted batches for your Zenserp API key.
List countries
Get the list of supported Google country (gl) parameters.
List supported languages
Get a list of supported Google interface language (hl) parameters.
List locations
Get a list of supported geo locations for search targeting.
List search engines
Get the list of supported search engines that can be queried via Zenserp.
Yandex search via zenserp
Obtain Yandex search results via Zenserp API.