> For the complete documentation index, see [llms.txt](https://docs.videsk.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.videsk.io/es-developers/componentes-web/webrtc.md).

# WebRTC

A continuación verás sacar el máximo provecho a nuestro WebRTC como componente web.

Un componente web permite que nuestro `WebRTC` opere como un elemento DOM nativo de los navegadores. De esta manera, podrás interactuar con el tal cual como con una etiqueta HTML.

Dentro de nuestro WebRTC podrás personalizar los botones disponibles, añadir elementos personalizados, cambiar el layout, escuchar eventos, definir tu propio CSS y mucho más.

Nuestro componente web pretende entregar una flexibilidad única al momento de personalizar la experiencias de tus clientes.

Para poder personalizar nuestro `WebRTC` como componente web, deberás definir la etiqueta en alguna parte de tu código HTML:

{% code lineNumbers="true" %}

```html
<videsk-webrtc></videsk-webrtc>
```

{% endcode %}

{% hint style="info" %}
Si defines el componente web, recuerda hacer [referencia en nuestro SDK](https://docs.videsk.io/es-developers/sdks/webrtc/metodos.md#create), de lo contrario se creará uno nuevo.
{% endhint %}

Puedes utilizar nuestro componente web independiente de nuestro SDK, pero deberás hacerte cargo de las conexiones `WebSocket` con nuestro servidor de señalización `wss://exchange.videsk.io`.


---

# 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://docs.videsk.io/es-developers/componentes-web/webrtc.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.
