High Volume API for SEO companies, data mining services, and SEO Tool Suite as a SaaS.
High Volume API for SEO companies, data mining services, and SEO Tool Suite as a SaaS. On Nagent, Serphouse is exposed as a fully-configurable developer tools integration that any agent can call — 18 actions, and API key authentication. No code is required to wire Serphouse into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Serphouse 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 Serphouse 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 Serphouse, with input parameters and output schema. Drop these into any step of an agent built in Helix.
SERPHOUSE_ACCOUNT_INFOTool to retrieve account information including active plan, credit usage, and account details. Use when you need to check account status, remaining credits, or active subscription plans.
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
SERPHOUSE_DOMAIN_LISTTool to retrieve comprehensive list of search engine domains supported by the SERP API including Google, Bing, and Yahoo. Use when you need to know which domains are available for search queries.
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
SERPHOUSE_GOOGLE_JOBS_SEARCHTool to perform real-time Google Jobs search to retrieve job listings. Use when you need to search for job postings on Google with specific query terms, location, and filters.
Input parameters
Search phrase to query for job listings.
Location name as string (e.g., 'New York,New York,United States'). Mutually exclusive with loc_id - provide either loc or loc_id, not both.
Language code for search results (e.g., 'en' for English, 'fr' for French).
Google domain to search (e.g., 'google.com', 'google.co.uk').
Location ID as integer. Mutually exclusive with loc - provide either loc or loc_id, not both.
Filter by posting date. Accepts 'h' (past hour), 'd' (24 hours), 'w' (week), 'm' (month), 'y' (year), or custom date range format.
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
SERPHOUSE_GOOGLE_SERP_ADVANCED_SCHEDULEDTool to schedule Google SERP scraping tasks that fetch up to 100 results by iterating through multiple result pages. Use when you need comprehensive search results beyond Google's 10-result limit. Credits are reserved upfront based on max_pages (1 page = 1 credit), with automatic refunds for unused pages.
Input parameters
List of search tasks to schedule. Each task will retrieve up to 100 results across multiple pages.
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
SERPHOUSE_LANGUAGE_LISTTool to retrieve full list of languages supported by Google, Bing, and Yahoo for SERP requests. Use when you need language codes for making SERP API requests or when configuring language-specific searches.
Input parameters
Specifies the search engine source. Valid values are 'google', 'bing', or 'yahoo'
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
SERPHOUSE_LOCATION_SEARCHTool to search and retrieve available locations for SERP API from Google or Bing geographical targeting data. Use when you need to find valid location targets before making SERP API requests.
Input parameters
Search term to filter the location database. This is the location name or keyword you want to search for.
Specifies the location provider. Must be either 'google' or 'bing'. Different providers have different location lists.
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
SERPHOUSE_SERP_CHECKTool to check the status of a previously submitted SERP task. Use when monitoring task completion progress or verifying whether a SERP task has finished processing.
Input parameters
Unique identifier of the SERP task to check status for. This ID is returned when the task was initially created.
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
SERPHOUSE_SERP_LIVE_GETTool to execute real-time search requests and retrieve search engine results immediately via HTTP GET. Use when you need to perform searches on Google, Bing, or Yahoo and get instant SERP data.
Input parameters
Search phrase to query.
Location name for geographically targeted results. Mutually exclusive with loc_id.
Result language using ISO language codes (e.g., 'en', 'fr', 'es').
Results page number to retrieve. Defaults to first page.
Device type for the search.
Search engine domain to use.
Location ID for geographically targeted results. Mutually exclusive with loc.
Filter similar or omitted results. '0' to disable, '1' to enable (default).
Google verbatim search mode. '0' for disabled, '1' for enabled.
Type of search results to retrieve.
Publication timeframe. Use 'h'/'d'/'w'/'m'/'y' for relative dates or 'YYYY-MM-DD,YYYY-MM-DD' format for date ranges.
Number of results per page. Defaults to 100.
Response format type. Defaults to 'json'.
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
SERPHOUSE_SERP_LIVE_POSTTool to execute real-time search requests and retrieve search engine results immediately using HTTP POST method. Use when you need to get fresh SERP data from Google, Bing, or Yahoo with specific location and device targeting. Supports web, news, image, and shopping search types with advanced filtering options.
Input parameters
Search phrase or query to search for.
Location name for the search (e.g., 'New York,New York,United States'). Either loc or loc_id must be specified.
Language code for the search (e.g., 'en' for English, 'fr' for French).
Page number of results to retrieve. Default is 1.
Device type to simulate for the search.
Search engine domain to use for the search.
Location ID for the search. Either loc or loc_id must be specified.
Similar/Omitted results filter. Default is 1. 0 = disabled, 1 = enabled.
Google Verbatim search mode. 0 = disabled, 1 = enabled.
Type of search results to retrieve.
Date filter for results. Use 'h' (hour), 'd' (day), 'w' (week), 'm' (month), 'y' (year), or custom range 'YYYY-MM-DD,YYYY-MM-DD'.
Number of results per page. Default is 100.
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
SERPHOUSE_SERP_SCHEDULETool to schedule SERP search tasks for asynchronous processing. Use when you need to queue multiple search tasks (up to 100 at once) for later execution. Results can be retrieved via webhook or polling.
Input parameters
Array of SERP tasks to schedule. Maximum 100 tasks per 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
SERPHOUSE_TRENDS_CATEGORIES_LISTTool to retrieve the full list of categories and subcategories for Google Trends searches. Use when you need category IDs for filtering trends analysis.
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
SERPHOUSE_TRENDS_CHECKTool to check the status of a previously submitted trend search task. Use when you need to monitor completion progress of a trend search.
Input parameters
Unique identifier of the SERP task to check status for.
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
SERPHOUSE_TRENDS_COUNTRY_LISTTool to retrieve the full list of countries and states for Google Trends searches. Use when you need geographic targeting options for trends analysis.
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
SERPHOUSE_TRENDS_GETTool to retrieve the results of a completed trend search query. Use when you need to fetch trend data for a specific task ID that was previously submitted. The task must be completed before results are available.
Input parameters
Unique identifier of your trend search task. This is the task ID returned from the trend search 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
SERPHOUSE_TRENDS_LANGUAGE_LISTTool to retrieve the full list of supported languages for Google Trends searches. Use when you need to identify valid language codes for trend search requests.
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
SERPHOUSE_TRENDS_SCHEDULETool to schedule Google Trends search tasks with configuration for keywords, time ranges, and geographic locations. Use when you need to collect Google Trends data for specific keywords, time periods, or regions. Supports batch processing of up to 100 tasks.
Input parameters
Array of trend search tasks to schedule (max 100 tasks in batch)
Notification URL for task completion via GET request
Webhook URL for result delivery via POST 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
SERPHOUSE_TRENDS_SEARCHTool to perform real-time Google Trends search to retrieve trend data for specified keywords. Use when you need to analyze keyword popularity across time periods and geographic locations.
Input parameters
Geographic location. '' for Worldwide or country/state code.
Time range specification. Valid values: 'now 1-H', 'now 4-H', 'now 1-d', 'now 7-d', 'today 1-m', 'today 3-m', 'today 12-m', 'today 5-y', or custom range 'YYYY-MM-DD YYYY-MM-DD'.
Category filter. 0 for all categories or specific category ID.
Search terms (max 5). Single term like 'google' or comma-separated like 'google,youtube'.
Search property type. Valid values: '' (Web), 'images', 'news', 'froogle', 'youtube'.
Language code. 'en' or other language codes.
Timezone offset value. Available offsets from timezone list endpoint.
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
SERPHOUSE_TRENDS_TIMEZONE_LISTTool to retrieve full list of timezones and offset values for use in Google Trend search requests. Use when you need timezone information for trend analysis or when configuring timezone-specific trend searches.
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 58 agents privately built on Nagent that already use Serphouse.
Build on Nagent
Connect Serphouse 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 Serphouse, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, Serphouse is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Serphouse is connected, you configure its 18 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop Serphouse 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 Serphouse event fires, the agent kicks off automatically.
Every Serphouse 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 Serphouse ships with 18 pre-built developer tools actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Serphouse together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Serphouse-based workflows tailored to your business.