> For the complete documentation index, see [llms.txt](https://docs.1kosmos.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.1kosmos.com/mobile-sdk/native/android.md).

# Android

Integrate the 1Kosmos SDK into your native Android app to add identity verification and passwordless authentication.

The Android SDK provides authentication (PIN, device biometrics, LiveID), document scanning and verification, user onboarding, and passkey support, integrated into your Android app via Gradle.

### Requirements

* **OS**: Android 9 (API level 28) or higher, up to Android 16.x
* **Tools**: Android Studio Panda 2 (2025.3.2) or higher, Android Gradle Plugin 9.0.0 or higher
* **Devices**: All devices running Android 9 or higher

### What's in this section

* **Integration Guide**: step-by-step instructions to install the SDK via Gradle, initialize it, and implement each feature in a new or existing Android project.
* **API Reference**: reference documentation for the SDK's classes and the Error Manager, for when you need method-level or error-handling details.

### Where to start

Start with the Integration Guide to set up and initialize the SDK. Use the API Reference while implementing specific features.


---

# 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.1kosmos.com/mobile-sdk/native/android.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.