AnySearch MCP integration for AI agents.
Connect AI agents to AnySearch through 4 structured actions, including batch search, extract, and get sub domains. Review authentication, inputs, workflows…
- ACTION CONTRACTS
- 4
- 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 AnySearch integration exposes
The AnySearch Agent App exposes 4 provider-backed actions for ai and data work. Its current contract lets an authorized agent run up to five independent general or vertical anysearch queries in parallel and return agent-ready markdown, fetch an html page through anysearch and return its cleaned content as markdown, and discover anysearch vertical sub-domains and their required parameters before running a specialized search. 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 AnySearch account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real AnySearch capabilities.
Showing 4 of 4 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
batch_searchREADRun up to five independent general or vertical AnySearch queries in parallel and return agent-ready Markdown.
INPUTS: queries
extractREVIEWFetch an HTML page through AnySearch and return its cleaned content as Markdown.
INPUTS: url
get_sub_domainsREADDiscover AnySearch vertical sub-domains and their required parameters before running a specialized search.
searchREADSearch AnySearch's automatically routed data sources and return structured source results.
INPUTS: query / max_results / domain / tag / content_types
INPUT CONTRACTS
Know what the action needs before it runs.
batch_search
queriesOPTIONAL- The search queries to execute in parallel.
extract
urlOPTIONAL- The HTTP or HTTPS page URL to fetch and convert to Markdown.
search
queryREQUIRED- The search query to execute.
max_resultsOPTIONAL- The maximum number of search results to return.
domainOPTIONAL- The top-level domain used to route the search.
tagOPTIONAL- A sub-domain capability tag, such as code.doc. Use a sub-domain returned by get_sub_domains when possible.
content_typesOPTIONAL- Content types to include, such as web, news, or doc.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Batch Search
Run up to five independent general or vertical AnySearch queries in parallel and return agent-ready Markdown. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
batch_searchVerify with Get Sub Domains
Discover AnySearch vertical sub-domains and their required parameters before running a specialized search. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_sub_domainsSAFETY BOUNDARY
Operate AnySearch with explicit limits
- Authorize AnySearch with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned AnySearch 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 AnySearch rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the AnySearch task completed successfully.
CONNECTION MODEL
API key
AnySearch API key sent as a Bearer token. Create and manage keys in the AnySearch console: https://www.anysearch.com/console/api-keys.
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
- 3
- WRITE SIGNALS
- 0
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 1
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 AnySearch.