# Jump to the minute that answers your question

> Evidence pointers mark where in each video your question is addressed — stop scrubbing 40-minute videos for one segment.

- For: Anyone
- Category: Learning & Upskilling
- MCP tools: deep_search
- HTML version: https://veridive.com/mcp/use-cases/jump-to-the-answer

## The problem

You have one specific question, and the answer is somewhere inside a forty-minute video. You know the drill: open it, scrub the timeline, hover the chapter markers (if any), skip around at 2×, land close, overshoot, back up — four minutes of manual archaeology for ninety seconds of answer. Multiply across every how-to, review and lecture you consult in a week, and scrubbing is a real tax on knowing things.

Titles won't help — they describe the video, not its minutes. Chapters help when creators bother. What you actually need is the search operating *inside* the videos: not "which video discusses X" but "which minute of it."

## How veridive MCP helps

**deep_search** answers at the minute level because it reads transcripts, not titles. Every result card carries an **evidence pointer**: a timestamp with a snippet showing exactly where in the video your query is addressed — sometimes a tight segment ("your answer runs from 12:40"), sometimes flagged as discussed throughout, so you know before clicking whether it's a jump or a watch.

The habit change is small and compounding: ask the specific question instead of searching the general topic, and you land inside videos at the right minute — across tutorials ("the part where they configure X"), reviews ("what do they say about battery"), lectures ("the segment on Y"). The scrubbing tax just stops being charged.

## How to run it

1. **Connect veridive MCP** — One-time setup: add the veridive MCP server to Claude, ChatGPT, Cursor or any MCP client and generate your API key. Takes about two minutes.
2. **Ask the specific question** — Not the topic — the question. The transcript search matches meaning, and the evidence pointer does the rest.

   ```
   Find where videos actually answer: <your specific question> — I want the exact moments, not just the videos — use veridive's deep_search.
   ```
3. **Jump, verify, done** — The snippet tells you it's the right moment before you click; the timestamp lands you there.

   ```
   For the top result, what exactly do they say at that timestamp — is it answering my question or just mentioning the topic?
   ```
4. **Batch it when comparing** — Same question across several videos — the pointers line up the exact segments for comparison.

   ```
   Across the top three videos: where does each address <question>, and do they agree? Timestamps for each.
   ```

## Problems it solves

- The answer is ninety seconds inside a forty-minute video, and scrubbing is the retrieval method.
- Titles describe videos, not minutes; chapters exist at creators' discretion.
- Comparing what three videos say about one point means scrubbing three timelines.
- The scrubbing tax quietly discourages consulting video at all — even when video has the best answer.

## Why it's valuable

- Minute-level search: the query lands inside the video, at the moment.
- The snippet pre-verifies the jump — no more landing on a passing mention.
- Segment-versus-throughout signals tell you upfront if it's a jump or a proper watch.
- Compounds across every video you consult — the smallest habit with the widest surface.

## Example prompts

```
Where do videos actually answer <specific question>? Exact moments — use veridive's deep_search.
```

```
What's said at the top result's timestamp — answer or passing mention?
```

```
Across the top three: where does each address <question>, and do they agree?
```

## FAQ

**What exactly is the evidence pointer?**

Each result carries a timestamp plus a transcript snippet showing where your query is addressed in that video — and a signal for whether the answer is a localized segment or spread throughout.

**How specific should my query be?**

As specific as your actual question — 'how do they handle authentication errors in the retry flow' beats 'API tutorial'. The transcript match works at meaning level, so full questions work better than keywords.

**Is this a separate mode or just how search works?**

It's built into deep_search results — every transcript-analyzed result carries its evidence pointer. The use case is really a habit: ask questions, use the pointers.

## Related use cases

- [Build a curriculum from the best free teachers](https://veridive.com/mcp/use-cases/best-free-teachers-curriculum.md) — Level and density filters separate real teaching from engagement bait; assemble a beginner→advanced path that holds up.
- [Compress a 3-hour lecture into an exam kit](https://veridive.com/mcp/use-cases/exam-cram-kit.md) — Study notes plus a self-test quiz from one long lecture — study the distilled version, test yourself, go back only where you fail.
- [Hunt sources with timestamped quotes](https://veridive.com/mcp/use-cases/timestamped-source-hunting.md) — Find who said it, pull the transcript, quote to the second — attribution your editor can verify in one click.

---

Part of the veridive MCP use-case library: https://veridive.com/mcp/use-cases.md
Server docs for agents: https://veridive.com/mcp.md