> For the complete documentation index, see [llms.txt](https://docs.ojin.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ojin.ai/apps.md).

# Apps

- [Human Agent](https://docs.ojin.ai/apps/overview.md): Ojin's star product, give your AI agent a face. A lifelike visual avatar that speaks, listens, and expresses emotion with real-time synchronized animation, embedded with a single line of code.
- [Create & Configure](https://docs.ojin.ai/apps/overview/configure.md): Set up your Human Agent in the Ojin dashboard. Pick a mode, configure appearance and behaviour, and publish it.
- [Tools & Events](https://docs.ojin.ai/apps/overview/tools.md): Let your Human Agent call functions during a conversation, and react to the agent from your own page.
- [Widget Integration](https://docs.ojin.ai/apps/overview/widget-integration.md): Embed a fully interactive Human Agent on your website with a single HTML tag.
- [Session API Reference](https://docs.ojin.ai/apps/overview/api-reference.md): Start agent sessions programmatically. The widget uses this API automatically, call it directly for custom integrations.


---

# 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.ojin.ai/apps.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.