# Jina DeepSearch — quota probe, confirms shared account exhaustion (2026-08-25)

One test call was made to confirm whether Jina's DeepSearch API (`jina-deepsearch-v1`) draws against
the same account balance already exhausted by `s.jina.ai` search during the main benchmark run.

**Request:** `POST https://deepsearch.jina.ai/v1/chat/completions`, `model: "jina-deepsearch-v1"`,
query: "Serper SOC 2 Type II audit completion date" (Q48).

**Response: `http_status: 402`**

```json
{"error":"Account balance not enough to run this query, please recharge."}
```

**Confirmed: DeepSearch draws against the same exhausted account balance as the tested `s.jina.ai`
search endpoint.** Unlike Linkup, Tavily, and You.com — whose untested answer-mode endpoints all
returned real, scorable data on the first attempt — Jina's DeepSearch is genuinely blocked at the
account level, the same class of gap as Olostep's `/answers` endpoint.

**Disposition: Citation accuracy (answer APIs) and Answer quality (answer APIs) remain not scorable
for Jina, confirmed as a real quota block rather than an assumption.** Closing this requires adding
paid balance to the Jina account — a spend decision, not resolvable by further testing with the
current key.