Perplexity Search API Integrated into Hermes Agent
Perplexity has added its Search API to Hermes Agent, providing live web retrieval and page extraction across an index of over 400 billion URLs.
Perplexity Search API integration enables live web retrieval and scraping within Hermes Agent.
- Perplexity has integrated its Search API into Hermes Agent, starting in Hermes v0.21.1 (tag v2026.9.7).
- The integration powers Hermes's
web_searchandweb_extracttools with access to an index exceeding 400 billion URLs. - Developers can decouple web retrieval from their underlying LLM reasoning provider by providing a dedicated Perplexity API key.
- Configuration is supported through the interactive Hermes CLI setup wizard or direct edits to local YAML and environment files.
Overview of the Hermes Integration
Perplexity has announced that its Search API is now directly supported in Hermes Agent, an open-source AI agent framework developed by Nous Research. Announced by the Perplexity Developers account on X and outlined in official Perplexity integration documentation, the feature allows Hermes to connect to Perplexity's index of over 400 billion URLs for real-time web search and content extraction.
The update brings Perplexity's infrastructure to two core agent toolsets: web_search, which retrieves and ranks snippets based on relevance, and web_extract, which pulls targeted passages directly from specific URLs. This tooling enables autonomous agents to ground responses and reasoning pipelines in live web data.
Decoupling Search from the Core Language Model
A central design detail of the integration is that configuring Perplexity as the web backend does not alter the underlying model that drives the agent. Hermes allows users to select any supported model provider for reasoning and text generation while configuring a separate Perplexity API key strictly for web browsing actions.
This separation allows developers to retain specialized reasoning models, local open-source weights, or enterprise API endpoints while using Perplexity specifically for indexing, crawling, and snippet ranking. The Perplexity provider is available starting in Hermes version 0.21.1 (tagged as v2026.9.7) via Hermes PR 102055. Installations running Hermes v0.21.0 or earlier require an update via hermes update before the provider appears in tool menus.
Setup and Configuration Process
Developers configuring the integration must satisfy three initial prerequisites: an active Hermes model provider configured for chat and reasoning, a valid Perplexity API key generated from the Perplexity API Console, and Hermes v0.21.1 or later.
Hermes supports both interactive and manual configuration paths. For guided configuration, developers can run the tool setup wizard:
- Run
hermes toolsin the terminal. - Select Reconfigure an existing tool’s provider or API key.
- Navigate to Web Search & Scraping and choose Perplexity.
- Input the Perplexity API key at the prompt.
Hermes stores API secrets in ~/.hermes/.env and general settings in ~/.hermes/config.yaml. For manual configuration, users can set PERPLEXITY_API_KEY in their environment file and map the web backend parameters in the YAML configuration:
web:
backend: perplexity
search_backend: perplexity
extract_backend: perplexity
Because tool-specific overrides take precedence over the generic backend parameter, explicitly defining both search_backend and extract_backend ensures calls are not diverted to an older provider.
Verification and Tool Behavior
To verify the integration without interference from caching or automatic keyless fallbacks, Perplexity's documentation recommends temporarily disabling fallback flags in ~/.hermes/config.yaml, setting keyless_fallback: false, keyless_rescue: false, and cache_enabled: false.
Developers can test connectivity by initiating a session using hermes chat --toolsets web and prompting the agent to invoke web_search with a deterministic query, such as requesting a list of URLs and descriptions. When successful, Hermes exposes the explicit tool execution call and populates structured results. Upstream search limits are managed in rounded cache buckets by Hermes, which handles slicing the final array of results to the specific count requested by the user prompt.
Once verified, the combination of web_search and web_extract allows agents to complete complex research pipelines, such as compiling technical briefs, cross-referencing documentation, and validating real-time software release specifications against live documentation.
Enjoyed this?
Get more posts like this delivered to your inbox.