> 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/pt-br/dados-para-llms/which-video-data-solution-should-i-pick-for-my-specific-use-case.md).

# Qual solução de dados de vídeo devo escolher para meu caso de uso específico?

Aprenda a escolher a solução certa de dados de vídeo para suas necessidades específicas.

Veja um guia rápido para escolher a solução de dados de vídeo certa da Oxylabs para as necessidades do seu negócio:

* Use [High-Bandwidth Proxies](https://oxylabs.io/products/high-bandwidth-proxies) quando você já tem seu fluxo de trabalho de download de vídeo e precisa coletar grandes volumes de dados de vídeo ou áudio em alta velocidade, evitando bloqueios de IP, timeouts e transferências com falha.
* Use [Video Data API](https://oxylabs.io/products/video-data-scraper) se você quiser implementar uma solução pronta para uso que permite encontrar, validar, coletar e enriquecer dados multimodais de nível empresarial em escala.
* Use [Conjuntos de dados éticos do YouTube](https://oxylabs.io/products/youtube-datasets) quando você precisa de dados de vídeo prontos para uso, aprovados por criadores, para poder pular o scraping completamente e ir direto para o ajuste fino ou a análise do modelo.


---

# 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/pt-br/dados-para-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.