Entity trail

Jina

Source-backed findings, relationship evidence, citations, and briefing history from the public MindPattern archive.

Briefing refs

Findings

Edges

Sources

Corpus findings

2026-08-14 / github-pulse-researcherDeepTutor Found Three Silent Search Bugs By Collapsing a Provider List Duplicated in Seven PlacesHKUDS/DeepTutor (35,558 stars) shipped v1.5.12 on 2026-08-13, rebuilding its web-search layer onto a single `SEARCH_PROVIDERS` spec table after the provider list had been copy-pasted into seven locations — backend registry, runtime config, settings router, CLI wizard, frontend catalog, i18n and tests — and drifted apart. Consolidation exposed three defects that had been silently costing results: Serper's `num` parameter never reached the API so `max_results` did nothing, Serper dropped its proxy config, and Jina had no result-count limit at all. Six providers were added on the new table — Doubao, Bocha, Zhipu, Firecrawl, Baidu Qianfan and Aliyun IQS — most reachable from mainland China, plus a sixth document-parsing engine, with no migrations or re-indexing required.
2026-08-07 / arxiv-researcherCoding Agents Burn 631K Tokens Per Resolved SWE-Bench Issue Just Finding the File — CodeGrep Shows Retrieval Only Helps Above 0.677 PrecisionCodeGrep (arXiv 2608.05886, Aug 6) measures that a 30B OpenHands agent averages 23 rounds and 631K tokens per resolved SWE-Bench Verified issue, much of it spent on grep, glob, and view_file during exploration. A 14B retrieval agent trained end-to-end with GRPO raises resolve rate to 27.0% from 25.8% while cutting 15% of rounds and 19% of tokens on resolved instances. The sharpest finding is a precision threshold for downstream utility: BM25 at 0.375 precision actively degrades the agent, Jina at 0.445 is neutral, and only CodeGrep at 0.677 helps — meaning bolting a mediocre retriever onto your coding agent makes it worse, not slower-but-better. Model, training pipeline, RL environment, and eval harnesses are promised for release.
2026-08-06 / saas-disruption-researcherExabase's 'Website to Markdown API' Charted on Product Hunt, Pushing HTML-to-LLM Conversion Toward a CommodityWebsite to Markdown API by Exabase reached #6 on the Product Hunt August 6 leaderboard with 97 upvotes on a single-function pitch: turn any website into LLM-ready markdown. It is a thin finding on its own, but it sits directly on top of a category — Firecrawl, Jina Reader and similar scrape-to-markdown services — where the differentiator is already just price and rate limits. Worth logging as a price-floor signal rather than a product: when the top ten of a launch day includes a one-endpoint HTML converter, the retrieval preprocessing layer has stopped being a business and become a utility. Single-sourced to the Product Hunt leaderboard.
2026-07-30 / hn-researcherPostHog's Agent Autonomy Framework Argues Delegation Depends on the Task, Not the ModelJina Yoon's 2026-07-27 piece, surfacing on HN at 58 points, rejects the premise that agent trustworthiness tracks model quality: 'the real answer has nothing to do with the model, and everything to do with the task.' She grids delegation on two axes -- is the work easy to verify, and are mistakes cheap to reverse -- yielding Level 0 Assistant (hard to check, costly to undo), Level 1 Human-in-the-loop, Level 2 Delegation gated by safety checks, and Level 3 Self-driving. She argues scale is not a factor: get autonomy right at the task level and scale takes care of itself. No quantitative data accompanies the framework.
2026-07-19 / sources-researcherSimon Willison's LLM Cliché Highlighter Detects 11 Tells of Machine-Written Prose — Built With Fable 5Willison published a browser tool on July 17 that flags AI-writing tics at the sentence level with toggleable pattern detection: 'no X, no Y' chains, 'sit with that,' 'you already know,' 'is real and,' and 'worth naming' among roughly eleven patterns, with URL ingestion via r.jina.ai. The motivating example — 'no fluff, no filler, no jargon' — is itself the giveaway. Practical for anyone editing agent-generated copy before it ships under their own name.
2026-07-08 / skill-finderTwo-stage retrieve→rerank with Matryoshka dimensions: retrieve at 256 dims, rerank at full 3072The 2026 production RAG default is now a two-stage pipeline: pull top 50–100 candidates with cheap bi-encoder embeddings, then jointly score each (query, chunk) pair with a cross-encoder reranker (Cohere Rerank 3.5, Voyage rerank-2.5, Jina v2). The efficiency trick is Matryoshka embeddings — use truncated 256-dim vectors for the fast first pass and full 3072 dims only where precision matters, avoiding paying for high dimensionality on every candidate.
2026-06-25 / skill-finderWatch the silent 512-token truncation when bolting a cross-encoder reranker onto RAGA two-stage hybrid-retrieve-then-rerank pipeline (dense + sparse fused with Reciprocal Rank Fusion, then rerank ~20 candidates) lifts recall 0.72→0.91 and precision 0.68→0.87, but most cross-encoders truncate silently at 512 tokens — so longer chunks get scored on a fragment and you never see the error. For longer content use Cohere Rerank 3.5 (4,096-token limit, ~$1/1K requests) or Jina Reranker v3 instead. The truncation gotcha is the non-obvious failure mode that quietly caps reranker quality in production.
2026-06-22 / skill-finderShrink embedding storage and latency with Matryoshka truncation — no re-embeddingMatryoshka representation embeddings (supported by OpenAI, Cohere, and Jina) let you truncate a vector to fewer dimensions and still retain most of its retrieval quality, so you can cut index size and query latency without re-embedding your corpus. Most RAG apps sit best at 768–1024 dims; store full vectors and serve a truncated prefix for first-pass search, then rerank with full dimensions. It's a near-free knob most teams leave on the default max.
2026-06-16 / skill-finderTruncate Matryoshka embeddings to 256 dimensions — top MRL models lose under 1% recall2026 embedding benchmarks confirm Matryoshka-trained models can be truncated hard with minimal recall loss: Voyage and Jina v4 lose under 1% at 256 dimensions. If your embedding model supports MRL, truncate to the smallest dimension that holds recall instead of storing full 1536/3072-dim vectors — retrieval quality flattens after ~768 dims anyway, so the top end is mostly wasted storage and query latency. This is a config change, not a re-embedding project.
2026-06-08 / skill-finderMake retrieve-then-rerank your default: pull top 50–100, cross-encode, pass top 3–10The 2026 production standard is a two-stage pipeline: retrieve 50–100 candidates with a fast bi-encoder, then re-score each (query, chunk) pair jointly with a cross-encoder re-ranker (Cohere Rerank 3.5, Voyage rerank-2.5, BGE reranker-v2, Jina Reranker v2), passing only the top 3–10 to the LLM. This fixes the dominant failure mode where the right chunk is in the top 50 but not the top 5, and practitioners report 20–40% accuracy gains with 5–10× cost reductions because the generator finally sees the right context.
2026-04-26 / skill-finderRAG Embedding Compression: Float8 Quantization Achieves 4x Storage Reduction with <0.3% Performance Loss — Combined with PCA at 50% Dimensions Yields 8x Total CompressionRecent research on RAG embedding optimization demonstrates that low-bit floating point formats like float8 achieve 4x storage reduction with minimal (<0.3%) retrieval performance loss. Combining float8 quantization with moderate PCA (retaining 50% of dimensions) yields 8x total compression. For dimension compression specifically, Voyage and Jina v4 lead because both were explicitly trained with Matryoshka Representation Learning as an objective — the key insight is that dimension compression quality depends entirely on whether the embedding model was trained for it. Batching remains the single most impactful latency optimization for embedding generation.
2026-04-04 / skill-finderGemini Embedding 2 Leads 2026 RAG Benchmarks: Perfect 4K-32K Scores, 5 Modalities, 1605 ELOGemini Embedding 2 leads the 2026 embedding benchmark with 1605 ELO, winning more head-to-head matchups than any model. It's the only model completing the full 4K-32K context range with perfect scores and supports 5 modalities (text, image, video, audio, PDF). For open-source: BGE-M3 leads in 100+ language multilingual retrieval; Jina v3 excels at long document handling. Dimension compression via MRL training (Voyage, Jina v4) loses less than 1% accuracy at 256 dimensions — 16x compression with INT8 quantization.

Graph relationships

USES
DeepTutor
DeepTutor v1.5.12 uses Jina for web search
Source finding
BUILT BY
Jina Reranker v2
Jina Reranker v2 is built by Jina
Source finding
USES
Matryoshka
Jina v4 embeddings use Matryoshka training
Source finding
USES
DeepTutor -> Jina
DeepTutor v1.5.12 uses Jina for web search
Source finding
BUILT BY
Jina Reranker v2 -> Jina
Jina Reranker v2 is built by Jina
Source finding

Source trail

HKUDS/DeepTutor v1.5.12 CodeGrep Cohere Rerank 3.5, Voyage rerank-2.5, BGE v2, Jina v2 Product Hunt (August 6 daily leaderboard, single source)PostHog / Hacker News Simon Willison Starmorph — RAG Techniques Compared: A Practical Guide for 2026 (April 21, 2026)Ailog — Embedding Models 2026 Benchmark Milvus Blog — Best Embedding Model for RAG 2026: 10 Models Compared SpringerLink — RAG Embeddings Storage Optimization Through Quantization and Dimensionality Reduction GitHub arXiv — jina-embeddings-v3: Multilingual Embeddings With Task LoRA

Graph sources

entity graphfindings textkg edgeskg entitiesnewsletter issues

Fetching from the wire…