Built by Metorial, the integration platform for agentic AI.
Provider Summary
search web engines
search product listings
retrieve image results
search news articles
query local business data
search flights
retrieve Google Trends data
search academic papers
extract shopping prices
reverse image search
Fourteen tools cover web search (Google, Bing, DuckDuckGo, Yahoo, Yandex, Baidu, Naver), images (including Google Lens), news, videos, shopping, Maps, Flights, Scholar, Trends, Jobs, autocomplete, locations, account information and exact search archives. Each engine receives its documented native parameters.
Connect using your API key from https://serpapi.com/manage-api-key. Authentication verifies the free native Account API and binds its account ID to the key. Existing token-only connections remain usable; reconnect to store the additional account binding. Account information and locations are free. Searches may consume credits; cached requests are free only when all parameters match and the native cache is valid. This integration does not enforce a spending cap.
async: true returns native queued/processing status and the search ID. It cannot be combined with noCache: true or a Ludicrous Speed account. Use get_search to read the exact ID once rather than resubmitting a query. Native failure, pending status and missing metadata never imply completed results. Network failures may leave a search or charge; inspect native account history before retrying.
get_search can provide completed JSON/HTML files through the authenticated archive. The provider documents retention for up to 31 days after completion. No renewal or guaranteed expiry timestamp is invented. There is no search-history deletion, credit refund or cleanup tool.
Compatibility guidance:
numResults is retained in the schema but refused locally because Google no longer supports num. Page offsets advance by 10; startOffset permits an exact offset.startOffset after the first page. All offsets are native, not inferred completeness claims.mkt/cc; DuckDuckGo uses kl. Supply country with language to form these native regional codes. Yandex uses a native regionId rather than an ISO country.startIndex and deprecated chips; use nextPageToken and native filterToken (uds).stops retains the native values: 0 any, 1 nonstop, 2 up to one stop, 3 up to two stops. Prices use only native currency information or the documented Flights default USD.nativeLocationId; the historical numeric locationId remains optional and is never populated by lossy coercion. GPS uses native longitude, latitude order.Provider documentation: Search, Account, Archive, Locations, Jobs, Shopping.