> For the complete documentation index, see [llms.txt](https://developers.oxylabs.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developers.oxylabs.io/help-center/data-for-llms/which-video-data-solution-should-i-pick-for-my-specific-use-case.md).

# Which video data solution should I pick for my specific use case?

Learn how to choose the right video data solution for your specific needs.

Here’s a quick guide to picking the right Oxylabs’ video data solution for your business needs:

* Use [High-Bandwidth Proxies](https://oxylabs.io/products/high-bandwidth-proxies) when you already have your video-download workflow and need to fetch massive volumes of video or audio data at high speed while avoiding IP blocks, timeouts, and failed transfers.
* Use [Video Data API](https://oxylabs.io/products/video-data-scraper) if you’d like to implement a ready-to-use solution that lets you find, validate, collect, and enrich enterprise-grade multimodal data at scale.
* Use [Ethical YouTube Datasets](https://oxylabs.io/products/youtube-datasets) when you need ready-made, creator-approved video data so you can skip scraping altogether and jump straight into model fine-tuning or analysis.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://developers.oxylabs.io/help-center/data-for-llms/which-video-data-solution-should-i-pick-for-my-specific-use-case.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.