> For the complete documentation index, see [llms.txt](https://projectsolo.gitbook.io/solo/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://projectsolo.gitbook.io/solo/integration-guide.md).

# Integration Guide

## Integration overview

Solo is designed for minimal-friction integration. Projects can add Proof of Humanity verification to a dApp or backend without rebuilding their core architecture.

<table><thead><tr><th width="199.52734375">Area</th><th>Current documentation position</th></tr></thead><tbody><tr><td><strong>Integration type</strong></td><td>Server-side REST API.</td></tr><tr><td><strong>Chains supported</strong></td><td>EVM-compatible chains, based on the current Solo draft.</td></tr><tr><td><strong>Device requirements</strong></td><td>Any smartphone on iOS or Android; no specialized hardware.</td></tr><tr><td><strong>Verification latency</strong></td><td>Fast verification architecture; sub-second re-verification triggers.</td></tr><tr><td><strong>Data storage position</strong></td><td>No biometric data should be stored by Solo or partners under the default proof-of-humanity flow described in the draft.</td></tr><tr><td><strong>Compliance posture</strong></td><td>No KYC and no raw biometrics by default; regulated KYC should remain a separate partner workflow where legally required.</td></tr></tbody></table>

{% stepper %}
{% step %}

## Register your project

Contact the Solo BD team to register your project and receive an API key. Provide:

* Project name and description.
* Primary use case, such as airdrop, governance, gaming, data labeling, patient identity, financial onboarding, or fraud prevention.
* Target chain and expected verification volume.
* Preferred integration method, such as frontend SDK or smart contract.

{% hint style="info" %}
**Partnership Contact**

Reach out via projectsolo.xyz to begin the integration process. Existing partners receive priority technical support and co-marketing opportunities.
{% endhint %}
{% endstep %}

{% step %}

## API integration

Solo’s API handles the full verification flow: your backend creates a session, the user verifies inside the Solo app, and your backend receives the result. No biometric data touches your infrastructure. The integration requires two API calls and takes hours, not weeks.
{% endstep %}

{% step %}

## Smart contract integration for Web3 projects

For on-chain enforcement, such as airdrop contracts or governance modules, Solo provides a PoH Verifier contract that any Solidity contract can call to validate a PoH proof before executing. Non-blockchain integrations proceed directly from Step 2 to Step 4.
{% endstep %}

{% step %}

## Continuous verification configuration

Enable mid-session re-verification by configuring trigger conditions in your project settings.

{% hint style="info" %}
**Note on UX**

Re-verification is designed to be as frictionless as a phone unlock: a brief face-forward prompt. Completion rate in prototype testing is high when trigger frequency is calibrated to session type.
{% endhint %}
{% endstep %}
{% endstepper %}

## Integration complexity by use case

* **Low complexity:** airdrop gating, governance voting, simple claim or signup checks.
* **Medium complexity:** financial onboarding, telehealth identity checks, government services, quest or reward campaigns, data labeling, gaming, and DePIN contribution.
* **Higher complexity:** SocialFi, credit scoring, and future credential-layer integrations that require reputation or anonymous credential design.