> For the complete documentation index, see [llms.txt](https://docs.limio.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.limio.com/components/component-library/standard-components/component-hosted-component.md).

# Component: Hosted Component

**Purpose**: Customers can host components and styles that they can edit themselves by fetching code and injecting it in.

This component is designed to fetch a piece of code from a specified URL, parse the code, and inject it into the DOM of the current page. The code at the specified URL is expected to contain HTML elements, such as links, meta tags, scripts, and styles, as well as other content that will be injected into the body of the page.

**Additional configuration**\
For this to work, you need to add the URL as a trusted host to your shop's Content Security Policy (CSP). A guide on how to do that can be found [here](https://docs.limio.com/product/settings/security/content-security-policy-csp).

## Props

| Prop Name          | Label                               | Type   | Default Value | Description                         |
| ------------------ | ----------------------------------- | ------ | ------------- | ----------------------------------- |
| hostedComponentUrl | URL to hosted component source code | string | ""            | URL to hosted component source code |


---

# 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.limio.com/components/component-library/standard-components/component-hosted-component.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.