# Choose Your Integration

## Comparison

|  | API | Embeds | Partner | MCP |
|  --- | --- | --- | --- | --- |
| Custom UI | ✓ | ✗ | ✓ | ✗ |
| Pre-built UI | ✗ | ✓ | ✗ | ✗ |
| Full API control | ✓ | Partial | ✓ | ✗ |
| AI-powered queries | ✗ | ✗ | ✗ | ✓ |
| Multi-tenant (your customers run checks) | ✗ | ✓ | ✓ | ✗ |
| Revenue share | ✗ | ✗ | ✓ | ✗ |


## Decision guide

Run checks via code
**Use the Checkr API.** Create candidates, order checks with packages, retrieve results, and listen for webhook events through a standard REST API.

Drop in a sign-up or consent UI
**Use Checkr Embeds.** The WebSDK provides pre-built components for the full candidate flow — sign-up, disclosure, consent, and report views.

Your customers run checks through your platform
**Use the Partner Program.** Connect your customers' Checkr accounts via OAuth, manage packages on their behalf, and earn revenue sharing.

Query Checkr data with an AI assistant
**Use Customer MCP.** Connect Claude or any MCP-compatible AI assistant to your Checkr account and ask questions in natural language.

## Still not sure?

Start with the [Quick Start](/get-started/quick-start) to create your first background check using the API. Once you understand the core flow, it's easier to evaluate which product fits your architecture.