> For the complete documentation index, see [llms.txt](https://docs.admira.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.admira.com/english/contents/html-content/url-contents.md).

# URL contents

In cases where it is required to load a web page on the player as content and its preload affects the issuance of its elements, a content has been created so that this load is compatible with the Admira player. The content is made up of a series of files, including access with the player api, for loading the content according to its broadcast. In one of them we must add the URL that we want to broadcast and upload the content as HTML + attachments.

Example:

<figure><img src="/files/zBfdWsNMkQyYsUSDPNAn" alt=""><figcaption><p>Content</p></figcaption></figure>

You can request the content from the QA department  <qa@admira.com>.

Once we have the content we just have to open the **variables.json** file

<figure><img src="/files/UoEmrTD1Oy5lNsk9DQ5x" alt=""><figcaption><p>Variables</p></figcaption></figure>

And then modify the URL for the content you want to upload.

Once this is done, we must upload the content to the platform as HTML + attachments.


---

# 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://docs.admira.com/english/contents/html-content/url-contents.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.