> ## Documentation Index
> Fetch the complete documentation index at: https://docs.get-rial.com/llms.txt
> Use this file to discover all available pages before exploring further.

# rial developer documentation

> Verify that a photo is real, at the moment of capture.

Build with rial: mint verifications from your backend, capture natively on Android, or script against the API from the command line.

<CardGroup cols={2}>
  <Card title="REST API" icon="cloud" href="/quickstart">
    Server-side integration. Mint verifications, receive webhooks.
  </Card>

  <Card title="Kotlin SDK" icon="android" href="/sdks/kotlin">
    Native Android capture: camera, templates, offline queue. **v0.10.1**
  </Card>

  <Card title="CLI" icon="terminal" href="/cli">
    Ad-hoc calls and scripting.
  </Card>

  <Card title="Swift SDK" icon="apple">
    Coming soon — native iOS capture.
  </Card>

  <Card title="React Native" icon="react">
    Coming soon — cross-platform capture module.
  </Card>
</CardGroup>

## What this API does

You mint a verification against your tenant account, get back a `capture_url`, and send that link to your end-user. They open it on their phone, capture the photos you asked for, and the verification's status moves through:

```
pending → partially_captured → completed | expired | failed
```

Once `completed`, the verification carries a verdict built from on-device signals — screen-recapture detection and AI-generation detection — plus the captured images themselves.

<Card title="Get started" icon="rocket" href="/quickstart" horizontal>
  Zero to a verification in five steps.
</Card>

## Core concepts

<CardGroup cols={2}>
  <Card title="Authentication" icon="key" href="/authentication">
    The two key types, environments, and how the SDKs authenticate.
  </Card>

  <Card title="Verdicts" icon="badge-check" href="/verdicts">
    How `status` and `verdict` are built, and what each signal checks.
  </Card>
</CardGroup>