Web search

# curl
curl -sS https://api.unoblox.ai/v1/search \
  -H "Authorization: Bearer $UNOBLOX_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "query": "latest Rust async runtime benchmarks", "numResults": 5 }'

{
  "requestId": "gen_01j9x...",
  "results": [
    {
      "id": "https://example.org/rust-async-benchmarks",
      "url": "https://example.org/rust-async-benchmarks",
      "title": "Async runtimes compared",
      "highlights": ["Tokio and async-std were measured on ..."],
      "snippet": "Tokio and async-std were measured on ...",
      "publishedDate": "2026-09-30"
    }
  ],
  "usage": { "search_requests": 1 }
}

The simple form works too:

# the simple form
curl -sS https://api.unoblox.ai/v1/search \
  -H "Authorization: Bearer $UNOBLOX_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "query": "unoblox pricing", "max_results": 3 }'

Each result carries url, title, a highlights array whose first entry is the matching text, and publishedDate when the source gives one. A search that finds nothing returns an empty results list and is still charged, because the search ran. The response never contains a price; the charge appears on your usage page. Result links are always http or https, and control and invisible characters are removed from titles and snippets. Results are still untrusted third-party web text: do not execute them or follow instructions found in them.

The query text is sent to our search provider, Perplexity, which runs in the United States, to run the search. Nothing else from your request or account is sent, and unoblox does not store the query text. Your workspace's content guardrails apply to the query exactly as they do to a chat prompt: a query they block is refused (UB-GW-074) and never sent, and redacted text is sent redacted. Workspaces whose guardrail policy requires zero data retention or forbids data collection cannot use web search (UB-GW-311). Perplexity is listed among our sub-processors in the privacy policy.

DeepSeek Harness (dsh) has a built-in web_search tool that can use an Exa-compatible endpoint. Point its Exa plugin at https://api.unoblox.ai/v1 and use your unoblox key; the installer in the dsh setup guide does this for you and switches off dsh's default search, which would otherwise send queries to another service.

Errors use the Exa shape: error is the message text, and error_code is the stable code. See Errors for the shared taxonomy.

import time, requests

def web_search(query, max_results=5, retries=3):
    for attempt in range(retries):
        r = requests.post(
            "https://api.unoblox.ai/v1/search",
            headers={"Authorization": f"Bearer {UNOBLOX_KEY}"},
            json={"query": query, "numResults": max_results},
        )
        if r.ok:
            return r.json()["results"]
        if r.status_code == 429:
            time.sleep(float(r.headers.get("retry-after", "1")))
        elif r.status_code in (502, 503):
            time.sleep(2 ** attempt)       # a failed search is never charged
        else:
            raise RuntimeError(r.json()["error"])   # 400/402: fix the request or top up
    raise RuntimeError("search is unavailable")