Your real-time SERP API solution. Mastering proxy management, CAPTCHAs, and JSON parsing for seamless web data extraction.
Your real-time SERP API solution. Mastering proxy management, CAPTCHAs, and JSON parsing for seamless web data extraction. On Nagent, Search api is exposed as a fully-configurable developer tools integration that any agent can call — 5 actions, and API key authentication. No code is required to wire Search api into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Search api to automate the kinds of tasks developer tools teams previously handled manually. Concrete examples — each one is a single agent step in Nagent — include:
Every action and trigger is paired with a structured input/output schema (visible in the sections below), so when you wire Search api into Helix — our agentic agent builder — the editor knows exactly what each step expects and produces. Configure once, deploy anywhere across your Nagent agents.
Every operation an agent can call against Search api, with input parameters and output schema. Drop these into any step of an agent built in Helix.
SEARCH_API_GET_ACCOUNT_INFOTool to retrieve account usage statistics including monthly usage, remaining credits, hourly limits, and subscription period information. Use when you need to check current account status or usage limits.
Input parameters
Enterprise-only feature. When set to true, disables all logging and persistent storage for this request.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
SEARCH_API_GET_CACHED_SEARCH_BY_IDTool to retrieve cached search results by search ID in JSON format. Use when you need to access previously executed search results without re-running the query. The search ID is found in the search_metadata.id or search_metadata.json_url field from initial search responses. Cached results are available for 90 days.
Input parameters
The unique identifier for a previously executed search, formatted as 'search_\[alphanumeric\]'. This ID is found in the 'id' or 'json_url' field of the search_metadata from initial search responses.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
SEARCH_API_GET_CACHED_SEARCH_HTML_BY_IDTool to retrieve cached search results by search ID in HTML format. Use when you need to access the raw HTML snapshot of a previous search execution. The search ID is available in the search_metadata.id or search_metadata.html_url field from initial search responses.
Input parameters
The unique identifier for a previously executed search. This ID is found in the 'id' or 'html_url' field of the search_metadata from initial search responses.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
SEARCH_API_GET_LOCATIONSTool to get available locations for geo-localized search queries. Use when you need to find location identifiers for targeting Google searches to specific geographic areas. Returns location metadata including identifiers, names, coordinates, and population reach.
Input parameters
Search query for location lookup. The location name you want to search for (e.g., 'new york', 'london', 'tokyo').
Maximum number of results to return. Default is 10, maximum allowed is 100.
Enterprise feature only. When set to true, disables logging of the request. Only available for enterprise accounts.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
SEARCH_API_SEARCHTool to perform unified search across 40+ search engines including Google, Bing, Yahoo, DuckDuckGo, YouTube, Amazon, and more. Use when you need to retrieve search results with rich structured data including organic results, ads, knowledge graphs, local listings, images, videos, and related searches. Supports advanced filtering by location, language, date, device type, and SafeSearch settings.
Input parameters
Search query terms with support for operators and advanced filters.
Restricts results by country via TLD or IP geolocation.
Country code for results (default: us). Two-letter country code.
Interface language code (default: en). Two-letter language code.
Restricts results by document language (format: lang_xx).
Number of results per page. Note: Google now returns a constant 10 results regardless of this parameter.
Set to 1 to exclude auto-corrected results.
Results page number for pagination (default: 1).
SafeSearch setting: 'active' to filter explicit content or 'off' to disable (default: off).
Google-encoded location parameter. Cannot be used together with location parameter.
Knowledge Graph identifier for entity-specific searches.
Device type for search results: desktop, mobile, or tablet (default: desktop).
Specifies the search engine to use. Supported engines include: google, bing, yahoo, duckduckgo, youtube, google_maps, google_shopping, google_jobs, google_hotels, amazon_search, ebay_search, walmart_search, apple_app_store, baidu, yandex, naver, and many more.
Enable (1) or disable (0) duplicate content filters (default: 1).
Canonical search location for geo-targeted results (e.g., 'United States', 'London,England,United Kingdom').
Filter results by date: last_hour, last_day, last_week, last_month, or last_year.
Google domain to search (default: google.com).
Enterprise-only feature. When set to true, disables all logging and persistent storage for this request.
Custom date range end in MM/DD/YYYY format.
Custom date range start in MM/DD/YYYY format.
Search optimization strategy: 'performance' or 'ads' (default: performance).
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
No publicly available marketplace agent is found using this tool yet. There are 53 agents privately built on Nagent that already use Search api.
Build on Nagent
Connect Search api to any Nagent agent in minutes — no API key management, no boilerplate. Just configure and deploy.
The five questions agent builders ask before adopting a new integration.
Open the External Integrations panel inside Nagent (app.nagent.ai/externalIntegration), find Search api, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, Search api is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Search api is connected, you configure its 5 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop Search api steps into any workflow visually. Pick an action (e.g., one of those listed above), fill in the inputs (Helix knows the required vs. optional schema for each parameter), and connect it to upstream/downstream steps. Triggers run as the entry point of an agent, so when a Search api event fires, the agent kicks off automatically.
Every Search api action and trigger ships with a fully-typed schema — input parameters with name, type, required flag, and description, plus the output payload shape. The schemas are documented in the sections above. Helix uses these schemas to validate your configuration at build time and to type-check the data flowing between steps.
Yes. While Search api ships with 5 pre-built developer tools actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Search api together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Search api-based workflows tailored to your business.