> 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/overview.md).

# Overview

Add identity verification and passwordless authentication to your mobile apps with 1Kosmos native and cross-platform SDKs.

The 1Kosmos Mobile SDKs let you embed document capture, LiveID biometrics, and credential-based login directly into your iOS, Android, Flutter, and React Native applications. Instead of sending users to a hosted page, you control the experience inside your app while 1Kosmos handles verification, liveness detection, and cryptographic binding behind the scenes.

Every integration produces the same result: a verified identity bound to the user's device, stored as a reusable credential that works across every 1Kosmos-enabled application in your environment.

### What you can do with the Mobile SDK

#### Authentication

Add PIN, device biometrics, or LiveID authentication to your app. Users can register these methods and then use them to log in without passwords.

#### User onboarding

Link and unlink user accounts, and authenticate users inside your app without leaving the experience.

#### Document scanning

Capture driver's licenses, passports, and national IDs directly in your app using the built-in document scanner.

#### Document registration

Add, remove, and restore PIN, LiveID, and identity documents (driver's license, passport, national ID, and other miscellaneous documents) to or from the 1Kosmos platform.

#### Document verification

Verify the data users present: driver's license verification, SSN verification, document liveness, face liveness, and face comparison.

#### Passkeys

Register and authenticate users with FIDO2 passkeys. Works with the 1Kosmos platform for account linking and JWT issuance, or standalone for apps not connected to 1Kosmos.

### Choose your SDK

Pick the SDK that matches your codebase. The cross-platform SDKs wrap the same native libraries, so capabilities and verification behavior are identical regardless of which one you choose.

| SDK                                                               | When to use it                                              | Dependency management       |
| ----------------------------------------------------------------- | ----------------------------------------------------------- | --------------------------- |
| [**Flutter**](/mobile-sdk/flutter-integration-guide.md)           | Single codebase for iOS and Android built with Flutter      | pub.dev                     |
| [**React Native**](/mobile-sdk/react-native-integration-guide.md) | Single codebase for iOS and Android built with React Native | npm                         |
| [**Native iOS**](/mobile-sdk/native/ios/integration-guide.md)     | Swift or Objective-C app; smallest dependency footprint     | Swift Package Manager (SPM) |
| [**Native Android**](/mobile-sdk/native/android.md)               | Kotlin or Java app; smallest dependency footprint           | Gradle                      |

### How it works

1. **Install the SDK** into your project.
2. **Initialize with your tenant credentials** and configure the verification or authentication level your journey requires.
3. **Launch the flow** from a button or screen in your app.
4. **Receive the result** in your app callback: a pass/fail outcome plus the verified identity details your backend needs.

### Security model

The SDK ships in a locked state. An app must successfully authenticate or register a user before any SDK function becomes available. If an unauthenticated request is made, the SDK returns an `Unauthorized access` error. This prevents a compromised app from invoking verification or authentication APIs on behalf of an attacker.

### Getting access

Request access to the SDK and demo applications by emailing the 1Kosmos support team.

### Next steps

* [Flutter Integration Guide](/mobile-sdk/flutter-integration-guide.md)
* [React Native Integration Guide](/mobile-sdk/react-native-integration-guide.md)
* [Native iOS Integration Guide](/mobile-sdk/native/ios/integration-guide.md)
* [Native Android Integration Guide](/mobile-sdk/native/android/integration-guide.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 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/overview.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.