SearchApi MCP integration for AI agents.
Connect AI agents to SearchApi through 5 structured actions, including get account info, get cached search html, and get cached search json. Review authentic…
- ACTION CONTRACTS
- 5
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the SearchApi integration exposes
The SearchApi Agent App exposes 5 provider-backed actions for data and location work. Its current contract lets an authorized agent retrieve account usage statistics for the connected searchapi api key, retrieve one cached searchapi search result in html format by search identifier, and retrieve one cached searchapi search result in json format by search identifier. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected SearchApi account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real SearchApi capabilities.
Showing 5 of 5 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_account_infoREADRetrieve account usage statistics for the connected SearchApi API key.
get_cached_search_htmlREADRetrieve one cached SearchApi search result in HTML format by search identifier.
INPUTS: searchId
get_cached_search_jsonREADRetrieve one cached SearchApi search result in JSON format by search identifier.
INPUTS: searchId
get_locationsREADLook up canonical SearchApi locations for geo-targeted search queries.
INPUTS: q / limit / zeroRetention
searchREADRun one SearchApi search request with the first-pass common query parameters.
INPUTS: engine / q / location / gl / hl
INPUT CONTRACTS
Know what the action needs before it runs.
get_cached_search_html
searchIdOPTIONAL- Search identifier returned by SearchApi.
get_cached_search_json
searchIdOPTIONAL- Search identifier returned by SearchApi.
get_locations
qREQUIRED- Search query used to match locations.
limitOPTIONAL- Maximum number of location matches to return.
zeroRetentionOPTIONAL- Whether SearchApi should disable logging for the request.
search
engineREQUIRED- Search engine identifier accepted by SearchApi.
qREQUIRED- Search query sent to SearchApi.
locationOPTIONAL- Canonical search location accepted by SearchApi.
glOPTIONAL- Two-letter country code used for localized results.
hlOPTIONAL- Two-letter language code used for localized results.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Account Info
Retrieve account usage statistics for the connected SearchApi API key. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_account_infoVerify with Get Cached Search Html
Retrieve one cached SearchApi search result in HTML format by search identifier. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_cached_search_htmlSAFETY BOUNDARY
Operate SearchApi with explicit limits
- Authorize SearchApi with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned SearchApi data may still be sensitive and should be minimized before it enters model context.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in SearchApi rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the SearchApi task completed successfully.
CONNECTION MODEL
API key
SearchApi API key passed as the api_key query parameter. Find it on the SearchApi homepage after signing in: https://www.searchapi.io/.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 5
- WRITE SIGNALS
- 0
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 0
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by SearchApi.