> For the complete documentation index, see [llms.txt](https://http3-explained.haxx.se/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://http3-explained.haxx.se/es/quic/quic-api.md).

# API

Uno de los factores de éxito de TCP regular y de los programas que lo utilizan, es la API de sockets estandarizada. Tiene una funcionalidad bien definida y usando esta API puedes mover programas entre muchos sistemas operativos diferentes ya que TCP funciona el mismo.

QUIC no está ahí. No hay una API estándar para QUIC.

Con QUIC, tienes que elegir una de las implementaciones de bibliotecas existentes y y seguir su API. Esto hace que las aplicaciones estén "encerradas" en una sola biblioteca hasta una sola biblioteca. Cambiar a otra biblioteca significa otra API y eso podría implicar mucho trabajo.

Además, como QUIC se implementa normalmente en el espacio de usuario, no puede fácilmente extender la API del socket o aparecer de forma similar a la funcionalidad existente de TCP y UDP. existentes. Usar QUIC significará usar otra API además de la API de sockets.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://http3-explained.haxx.se/es/quic/quic-api.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.