Checkr (BYOK)

Checkr (BYOK) — connector documentation

• MCP endpoint: https://byok-checkr.connectorbay.com/mcp
• REST API: POST https://byok-checkr.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-checkr.connectorbay.com/openapi.json
• Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
• Authentication: your own Checkr Checkr secret API key (production, not the publishable key), sent in the X-Upstream-Key header of every request (never stored, logged or cached)
• Health: https://byok-checkr.connectorbay.com/health · Tool schemas: https://byok-checkr.connectorbay.com/tools.json
• Publisher: Unify Dynamics LLC · connectorbay.com/byok-checkr · agent@connectorbay.com

What Checkr (BYOK) is for

Checkr (BYOK) lets an AI assistant read your own Checkr data through the Checkr API with a key you supply (Checkr secret API key (production, not the publishable key)). Read-only: 9 tools (get_account, list_candidates, get_candidate, get_report, get_report_eta, list_invitations, get_invitation, list_packages, list_geos). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to api.checkr.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Checkr. Checkr and its logos are trademarks of their owners and are used only to say which service the connector works with.

Ask your assistant things like:

• "Is my Checkr account authorized for API use and which screenings can it order?"
• "Which Checkr candidates are waiting for an adjudication decision?"
• "What reports does Checkr candidate e44aa283528e6fde7d542194 have?"
• "Is Checkr report 4722c07dd9a10c3985ae432a complete and what is the result?"
• "When will Checkr report 4722c07dd9a10c3985ae432a be finished?"
• "Which Checkr invitations are still pending?"

What it does

• get_account: Show the Checkr account the key belongs to: name, whether it is authorized for API use, purpose and the screenings it can order.
• list_candidates: List Checkr candidates with their custom id, adjudication decision and the ids of their reports. Names, contact details and identity numbers are left out. Does not return candidates with non-US work locations.
• get_candidate: Get one Checkr candidate by id: custom id, adjudication and the ids of their reports (no name, contact or identity data).
• get_report: Get the status of one Checkr background check report: status, overall result, package, adjudication, assessment and key dates. Individual search findings are not included.
• get_report_eta: Get the estimated completion time of a pending Checkr report.
• list_invitations: List Checkr invitations (requests sent to candidates to start a background check) by status or candidate. Does not return invitations with non-US work locations; the invitation link is left out.
• get_invitation: Get one Checkr invitation by id with status, package, candidate, report id and dates (no invitation link).
• list_packages: List the Checkr screening packages of the account with name, slug, price in cents and the screenings each includes.
• list_geos: List the Checkr geos (work locations) set up for the account, optionally filtered by name or state.

BYOK key

You bring your own Checkr Checkr secret API key (production, not the publishable key) (https://help.checkr.com/hc/en-us/articles/360010450474-Account-Settings#developer). Your assistant sends it in the X-Upstream-Key header with each request. ConnectorBay uses it for that one call only: it is never stored, logged or cached, never shown in an answer, and it is only sent to api.checkr.com over https, with no redirects followed. Create a key with the fewest permissions the tools need (read-only if the provider offers it), and revoke it at the provider whenever you like.

Data sources

• https://docs.checkr.com (the API this connector calls, with a BYOK key)

Live from the Checkr API (api.checkr.com) with a BYOK key; documentation: https://docs.checkr.com. Endpoints checked against that documentation on 2026-10-16.

What it is not

Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Checkr. Checkr and its logos are trademarks of their owners and are used only to say which service the connector works with. It is read-only: it never creates, changes, sends or deletes anything in your Checkr account.

Built for: Worldwide. Languages: English.

Checkr (BYOK) — Privacy Policy

Effective 24 October 2026. Unify Dynamics LLC ("we", "us"), Menlo Park, California.

What Checkr (BYOK) is. Checkr (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Checkr data: Read the status of your Checkr background check candidates, reports, invitations and packages (no personal identifiers) with your own secret API key. You bring your own Checkr Checkr secret API key (production, not the publishable key); the assistant sends it to us with each request.

BYOK key. The key you supply is used to make the one Checkr call you asked for. Our application does not store it, write it to a log, put it in a cache, or share it. It is sent only to api.checkr.com, over https, and is removed from any text we return to you or your assistant. We do not follow redirects with your key. If Checkr rejects it, we say so without repeating it.

What we receive. The arguments of each tool call, the BYOK key (for that call only), the technical headers needed to serve the request (an IP address or a client identifier supplied by the assistant) and standard server logs. What Checkr receives. The request we make on your behalf, including the key and the arguments, under Checkr's own terms and privacy policy. Checkr acts at your direction and is the only recipient of the data of your request besides our hosting provider.

What we return. The answer Checkr gives for your request, trimmed to the fields the tool documents. We do not keep it: it is returned to your assistant and not stored, cached or used to train anything.

What we do not do. We do not build a profile, sell or share personal information, or keep your Checkr data. Rate-limit counters (a client identifier and timestamps) are held in memory for at most 24 hours. Hosting access logs (IP addresses, request paths and status codes) are kept for up to 30 days for security and abuse prevention; our application adds no request headers or bodies to them.

Sub-processors. Checkr (the API you call with a BYOK key, at your direction). Hosting: Vercel (United States regions).

Your rights. Because we store no personal data beyond short-lived logs, requests to access, correct or delete data are usually satisfied automatically; you can still contact agent@connectorbay.com and we will respond within 30 days. Revoke your key at Checkr at any time to end all access.

Children. Checkr (BYOK) is a general-audience service operated by the adult using the assistant, under Checkr's own age rules.

Changes. We will post changes here with a new effective date.

Checkr (BYOK) — Terms of Service

Effective 24 October 2026. These terms govern use of the Checkr (BYOK) connector ("the Service") operated by Unify Dynamics LLC ("we", "us").

1. The Service. Checkr (BYOK) provides: Read the status of your Checkr background check candidates, reports, invitations and packages (no personal identifiers) with your own secret API key. It is accessed through an AI assistant or directly over MCP or HTTP, and is read-only.
2. Your own key, your own account. You must use your own Checkr credentials and only access data you are allowed to access. Checkr's terms apply to your use of Checkr; you are responsible for complying with them, including any rate limits and permitted uses. Do not share a key you do not own.
3. Independent. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Checkr. Checkr and its logos are trademarks of their owners and are used only to say which service the connector works with.
4. No advice, no guarantees. Output is the data Checkr returns, lightly trimmed; it may be incomplete, delayed or changed by Checkr. Check important facts at the source.
5. Read-only. The Service does not create, change, send or delete anything in your Checkr account.
6. Acceptable use. Automated use within the published rate limits is welcome. Do not use the Service to access data you are not entitled to, to circumvent Checkr's controls, or to attack any system.
7. Availability. The Service is provided "as is" without warranty. We may change, limit or discontinue it at any time; Checkr may change or end its API at any time.
8. Data. Our Privacy Policy describes what we process. In short: the BYOK key is used for the one call and not stored or logged.
9. Pro keys. Optional ConnectorBay Pro API keys are issued at our discretion and are separate from your Checkr key.
10. Liability. To the fullest extent permitted by law, Unify Dynamics LLC is not liable for any loss arising from use of or reliance on the Service, including any action Checkr takes on your account. Our total liability is limited to US $100.
11. Governing law. California law; venue in San Mateo County, California.
12. Contact. Unify Dynamics LLC · agent@connectorbay.com · https://connectorbay.com/byok-checkr

Checkr (BYOK) support

Email agent@connectorbay.com. We answer within two business days.

• MCP endpoint: https://byok-checkr.connectorbay.com/mcp
• REST API: https://byok-checkr.connectorbay.com/openapi.json
• Live status: https://byok-checkr.connectorbay.com/health

When you report a problem, include the question you asked your agent, roughly when, and which agent you used (for example Claude, ChatGPT or Gemini). Never send us passwords, account numbers or ID numbers. Checkr (BYOK) never asks for them.