Install Jentic One Beta

Connect the Checkr.com API Docs to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Checkr.com API Docs, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fcheckr.com%2Fcheckr" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fcheckr.com%2Fcheckr" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Checkr.com API Docs API.

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

GET STARTED

Start building with Checkr.com API Docs API

Explore with Jentic One

View OpenAPI Document

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.

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.

Call GET /adverse_actions/{id} to read an adverse action

Key Endpoints

121 endpoints — the checkr api lets an agent run background checks and manage the people and records behind them.

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

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

Why Jentic?

What agents get from Jentic-routed access to this vendor.

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 isolation

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.

Intent-based discovery

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.

FAQs

Specific to using Checkr.com API Docs API through Jentic.

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.

Checkr.com API Docs

AI ReadinessNon-Ready (F)39/100

See full scorecard

Official vendor OpenAPI document · agent-readyIdentity AuthIdentity Verificationbasic121 EndpointsREST

For 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.

Use for: Create a candidate, List the candidates, Run background checks on a candidate, Upload a candidate document

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

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.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: CSignals: 4

90%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

35%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: A-Signals: 4

45%

Example Density

How richly the API is illustrated with examples.

97%

Example Validity

Percentage of examples that conform to their schemas.

50%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: CSignals: 4

55%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

99%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

59%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A-Signals: 1

78%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: FSignals: 1

10%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A-Signals: 1

72%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Checkr.com API Docs to your agent

Capabilities

Start building with Checkr.com API Docs API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Checkr.com API Docs

Jentic AI Readiness Score

Checkr.com API Docs

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness