> For the complete documentation index, see [llms.txt](https://docs.cobrowse.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cobrowse.io/agent-side-integrations/custom-integrations.md).

# Custom integrations

Rather than accessing Cobrowse.io via our website, many of our customers integrate the agent-side UI directly into their own applications.

We provide a variety of resources to make this as easy as possible, including:

* [Agent SDK](/agent-side-integrations/agent-sdk.md) (client-side JavaScript SDK)
* [Agent UI component library](/agent-side-integrations/agent-sdk.md) (written in React)
* [Authentication (JWTs) ](/agent-side-integrations/json-web-tokens-jwts.md)(automatic authentication and permission scoping)
* [IFrame embeds](/agent-side-integrations/custom-iframe-embeds.md) (eg. to embed the entire Cobrowse.io dashboard)

Using a combination of these resources, Cobrowse.io can be seamlessly integrated as a white-labeled feature into your own products and services.

After your initial Cobrowse account setup, there's no need to register each individual user to your Cobrowse account - this is all done automatically through use of [JWTs](/agent-side-integrations/json-web-tokens-jwts.md).


---

# 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.cobrowse.io/agent-side-integrations/custom-integrations.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.