> 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/products/pt-br/proxies/dedicated-isp-proxies/enterprise/protocols.md).

# Protocolos

Saiba mais sobre os protocolos suportados e as configurações padrão de porta do serviço Dedicated ISP Proxy.

{% hint style="info" %}
Nossa equipe de Suporte ao Cliente está disponível 24/7 - entre em contato por [**support@oxylabs.io**](mailto:support@oxylabs.io) ou via chat ao vivo em nosso [**site**](https://oxylabs.io/). Eles ajudarão você a ativar o protocolo SOCKS5 para sua conta. Por padrão, o protocolo HTTP está habilitado.
{% endhint %}

#### HTTP

Nossa documentação inclui exemplos de código mostrando como se conectar aos Proxies usando `HTTP` protocolo. O protocolo é compatível com bibliotecas comuns e software de terceiros.

#### **SOCKS5**

Para usar `SOCKS5` o protocolo, você precisa adicionar `socks5h` na sua solicitação, por exemplo:

```
curl -x socks5h://1.2.3.4:1180 -U USERNAME:PASSWORD ip.oxylabs.io
```

#### Portas dos Proxies

A configuração padrão das portas de proxy inclui `80` e `443`, que são portas padrão projetadas para acomodar os `HTTP` e `HTTPS` protocolos, conforme descrito na tabela abaixo. Para acessar outras portas, é necessário passar por verificação de conformidade, entre em contato com nosso [**suporte**](mailto:support@oxylabs.io).

| Protocolo | Porta |
| --------- | ----- |
| `HTTP`    | `80`  |
| `HTTPS`   | `443` |


---

# 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/products/pt-br/proxies/dedicated-isp-proxies/enterprise/protocols.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.