> For the complete documentation index, see [llms.txt](https://doc.ozforensics.com/oz-knowledge/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.ozforensics.com/oz-knowledge/other/documentation-changelog.md).

# Documentation Changelog

#### October 2026

* Published recommendations on [how to update Oz components](/oz-knowledge/guides/administrator-guide/updates.md), including models.
* Added an [explanation for the automated usage reporting functionality](/oz-knowledge/guides/administrator-guide/automated-usage-reporting.md).
* Added a guide on [how to obtain images for each gesture in the multi-gesture scenario](/oz-knowledge/guides/developer-guide/api/oz-api/basic-scenarios/liveness/action-shot.md).
* If you used the on-device or hybrid analysis mode, please pay attention to the corresponding [migration guide](/oz-knowledge/guides/developer-guide/migration-guides/migration-from-on-device-and-hybrid.md).

#### July 2026

* Published an article on [how to install Oz Instant API in Kubernetes](/oz-knowledge/guides/administrator-guide/installation/installation-in-kubernetes/how-to-install-instant-api-in-kubernetes.md).
* Added instructions on [how to install Echo – Oz telemetry receiver](/oz-knowledge/guides/administrator-guide/telemetry/echo-oz-telemetry-receiver.md).
* Added a guide on [how to enable OpenTelemetry in Oz API](/oz-knowledge/guides/administrator-guide/telemetry/how-to-enable-opentelemetry-in-oz-api.md).
* Added [examples of SDK integration flows](/oz-knowledge/guides/developer-guide/sdk/sdk-integration-flows-on-premise.md) for on-premise installation with sequence diagrams.
* Updated the installation prerequisites for Docker and Kubernetes.
* Added the explanation on [how to run Web SDK in iframe](/oz-knowledge/guides/developer-guide/sdk/oz-liveness-websdk/web-plugin/launching-the-plugin/running-the-web-plugin-in-an-iframe.md).
* Added information on [how to add Android SDK using Google Dynamic Feature](/oz-knowledge/guides/developer-guide/sdk/oz-mobile-sdk/android/adding-sdk-to-a-project.md).
* Documentation is now available for AI via Context7 and via the built-in GitBook MCP: <https://doc.ozforensics.com/oz-knowledge/~gitbook/mcp>. If you use Claude Code or Codex, here are the CLI commands:

{% code title="Claude" expandable="true" %}

```bash
claude mcp add gitbook-documentation --scope user --transport http https://doc.ozforensics.com/oz-knowledge/~gitbook/mcp
```

{% endcode %}

{% code title="Codex" expandable="true" %}

```bash
codex mcp add gitbook-documentation --url https://doc.ozforensics.com/oz-knowledge/~gitbook/mcp
```

{% endcode %}

#### June 2026

* Updated [Quick Start Guides](/oz-knowledge/general/integration-quick-start-guides.md).
* Updated [Oz Licensing Options](/oz-knowledge/general/oz-liveness-and-biometry-key-concepts/oz-licensing-options.md) with a table of license-controlled features (`features.watermark`, `features.version-on-screen`, `features.on-device-liveness`, `configs.custom_logo`).
* [Mobile SDK integration guide](/oz-knowledge/general/integration-quick-start-guides/how-to-integrate-oz-liveness-into-your-mobile-application.md) now includes instructions on how to enable the debug environment to run the SDK with a debugger attached during development.
* Added a FAQ entry on [how to replace the Oz logo with a custom logo in our SDKs](/oz-knowledge/other/faq.md#can-i-add-my-own-logo-to-oz-sdk).

#### May 2026

* Added the [FAQ entry on the difference between `access_token` and `session_token`.](/oz-knowledge/other/faq.md#what-is-the-difference-between-access_token-and-session_token)
* Added the `session_token` method description to the [API reference](https://apidoc.ozforensics.com/) (Full API and Instant API).
* Added the OzCapsula request example to the [API reference](https://apidoc.ozforensics.com/) (Full API and Instant API).


---

# 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://doc.ozforensics.com/oz-knowledge/other/documentation-changelog.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.