canonical: https://jentic.com/apis/checkr.com/checkr

# Checkr.com API Docs

The Checkr API lets an agent run background checks and manage the people and records behind them. It can retrieve and create accounts, list and create candidates, retrieve or delete an adverse action, create and list continuous checks for a candidate, and upload and list candidate documents. It is a background screening and identity verification service.

## For AI agents

Run background checks and manage candidates through the Checkr API. Create candidates, set up continuous checks, upload documents, and handle adverse actions. Secured with HTTP basic authentication.

## Scope

Does not handle payroll or applicant tracking - use it to run background checks and manage the candidates, documents, and adverse actions behind them.

## Capabilities

- Retrieve and create accounts
- List and create candidates
- Retrieve or delete an adverse action
- Create and list continuous checks for a candidate
- Upload and list candidate documents

## Use cases

### Screen candidates

Run background screening inside an agent workflow. The agent creates a candidate and sets up the continuous checks that keep the screening current.

Example prompt: Call POST /candidates, then POST `/candidates/{candidate_id}/continuous_checks`

### Manage candidate documents

Keep the documents behind a screening in order. The agent uploads candidate documents and lists them back to confirm what is on file.

Example prompt: Call POST `/candidates/{candidate_id}/documents` to upload a document

### Handle adverse actions

Work with adverse-action records tied to a screening. The agent reads an adverse action to review it or deletes one that should be withdrawn.

Example prompt: Call GET `/adverse_actions/{id}` to read an adverse action

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/account` | Retrieve the current account |
| POST | `/accounts` | Create an account |
| GET | `/candidates` | List candidates |
| POST | `/candidates` | Create a candidate |
| GET | `/adverse_actions/{id}` | Retrieve an adverse action |
| DELETE | `/adverse_actions/{id}` | Delete an adverse action |
| GET | `/candidates/{candidate_id}/documents` | List a candidate's documents |
| POST | `/candidates/{candidate_id}/documents` | Upload a candidate document |

## Key resources

- **Candidates** — People being screened and the checks run against them
- **Adverse Actions** — Adverse-action records tied to a candidate's screening
- **Accounts** — Checkr accounts that candidates and checks belong to

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 39 / 100
- **Maturity:** Non-Ready
- **Dimensions:**
  - Foundational Compliance: 56 / 100
  - Developer Experience & Jentic Compatibility: 73 / 100
  - AI-Readiness & Agent Experience: 53 / 100
  - Agent Usability: 78 / 100
  - Security: 10 / 100
  - AI Discoverability: 72 / 100
- **View full report:** https://jentic.com/apis/checkr.com/checkr/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring the Checkr API by hand means managing basic-auth credentials, pointing at the api.checkr.com host, and shaping the candidate and check requests yourself. Through Jentic you install once, import the Checkr API from the Jentic API Directory, store the credentials once, and your agent calls it.
- **Permission scoping:** You decide which operations your agent may call, so it can read candidates without being able to create them or delete adverse actions. Because the candidate id sits in the URL path (`/candidates/{candidate_id}/documents`), a rule can pin the agent to a single candidate rather than the whole account.
- **Credential handling:** Your Checkr credentials, sent using HTTP basic authentication, are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'create a candidate' or 'read an adverse action', and Jentic returns the matching operation with its input schema so the agent calls the right endpoint without reading the reference.

## Related APIs

- **Onfido** — Alternative identity verification API
- **Veriff** — Alternative identity verification API
- **Truora** — Complementary background check API for Latin America

## FAQ

### What authentication does the Checkr API use?

The Checkr API uses HTTP basic authentication. Through Jentic, those credentials are stored encrypted in your Jentic One instance and injected at execution time, so they never enter the agent context.

### What can an agent do with the Checkr API?

It can retrieve and create accounts, list and create candidates, retrieve or delete an adverse action, create and list continuous checks for a candidate, and upload and list candidate documents. The API is built for background screening and identity verification.

### How does an agent connect to the Checkr API through Jentic?

Install Jentic One, import the Checkr API from the Jentic API Directory, and store the credentials once. Your agent then calls the operations you have allowed without handling the raw credentials.

### What are the rate limits for the Checkr API?

Rate limits are not specified in the OpenAPI spec. Check the Checkr documentation for current limits. Through Jentic, retries are handled in the execution layer.

### How many endpoints does the Checkr API have?

The Checkr API exposes 121 endpoints covering accounts, candidates, documents, continuous checks, and adverse actions.

### Can I limit what my agent is allowed to do with the Checkr API?

Yes. Jentic One is self-hosted by you, so your own rules decide which operations your agent may call. You can let it read candidates without being able to create them or delete adverse actions, and because the candidate id sits in the URL path, such as `/candidates/{candidate_id}/documents`, a rule can pin the agent to a single candidate.