Deep Search

Deep search is the long-running search mode inside search_call. It uses Perplexity’s deep research model path by default and allows a longer timeout than ordinary search.

Runtime Contract

{
  "query": "compare ERC-8004 agent identity with hosted SDK agent handoff models",
  "mode": "deep"
}

The runtime sends the query as a single user message, applies SEARCH_DEEP_REASONING_EFFORT when set, and waits up to 120 seconds. The response is returned as compact text plus citations when available.

Configuration

Setting	Default
`PERPLEXITY_API_KEY`	Required for `deep`.
`SEARCH_DEEP_MODEL`	`sonar-deep-research`.
`SEARCH_DEEP_REASONING_EFFORT`	`low`.

When To Use

Use deep search when the agent needs a slower research pass with public sources: market checks, regulatory summaries, technical comparisons, or source collection before synthesis. Do not use deep search for private account data, authenticated user actions, or deterministic workflow state. Those belong to connectors, Backpack, scratchpad, conclave, or MAL steps.

Search vs Synthesis

Deep search gathers and summarizes public information. It is not the final authority for a workflow. In a MAL plan, the usual pattern is:

steps:
  - op: tool
    saveAs: research
    toolName: search_call
    args:
      mode: deep
      query: "market evidence for agent-to-agent workflow runtimes"

  - op: synthesize
    saveAs: answer
    from: ["research"]
    instruction: "Write a concise technical comparison. Do not invent claims."
    model: "gpt-5.5"

  - op: stop
    output: "{{answer}}"

Overview

Memory

Harness

Tools

Runtime Contract

Configuration

When To Use

Search vs Synthesis

​Runtime Contract

​Configuration

​When To Use

​Search vs Synthesis

​Related

Runtime Contract

Configuration

When To Use

Search vs Synthesis

Related