import { Aside, Code } from '@astrojs/starlight/components';

Connect Claude or ChatGPT to your account so you can ask it to start a verification, check on an applicant, or pull a report, without opening the dashboard yourself. This is the interactive path: you sign in and authorize the assistant the same way you would sign in to the dashboard. There is no API key to create and no credential to paste.

Unlike the connections covered in the [Integrations overview](/guides/integrations), which trigger verifications automatically from another system, this connector is interactive: you or your teammates drive it directly from a conversation with the assistant.

## Get your connector URL

Every account has its own connector URL, tied to the region your account was created in. You need the **Owner** or **Admin** role to view it.

Open **Developers → AI connector** and copy the URL shown there.

Always copy your own account's URL from the dashboard. Do not reuse one from a screenshot, a teammate, or another region: the two live regional addresses look similar but only one belongs to your account.

<Code
  code={`https://mcp.us.checktiv.com/mcp\nhttps://mcp.eu.checktiv.com/mcp`}
  lang="text"
/>

<Aside type="tip" title="Used the wrong region by mistake?">
You are not stuck. If you add a connector URL for the wrong region, the sign-in page tells you which region that address belongs to and gives you the correct URL for your account. Follow that link and try connecting again.
</Aside>

## Add it to Claude or ChatGPT

### Claude

Open **Customize → Connectors**, select **Add**, then **Add custom connector**. On a Team or Enterprise plan, an organization owner adds it once under **Organization settings → Connectors** instead, and members then connect to it from their own **Customize → Connectors**.

Paste the connector URL you copied above and select **Add**. There are no OAuth credentials to fill in: the connector registers itself the first time you connect it.

### ChatGPT

Open **Settings → Connectors** and choose **Create**. Give it a name, for example "Checktiv," paste the connector URL you copied above, and leave the authentication method on its default. On a Business or Enterprise workspace, a workspace admin may need to turn on custom connectors first.

## Sign in and authorize

The first time you use the connector, the assistant opens a sign-in page for your account. Sign in the same way you do for the dashboard, then approve access for your organization. The assistant can then use the tools below for as long as your session stays valid; if it expires, you are asked to sign in again automatically.

## What the assistant can do

Once connected, the assistant works with your account through the same tools available at your role and plan:

- **Applicants**: add a new applicant (`create_applicant`), look up an applicant's details (`get_applicant`), or update them (`update_applicant`).
- **Verifications**: start a verification (`create_session`), check its status and results (`get_session`), cancel one in progress (`cancel_session`), approve or decline one under manual review (`sessions_manual_review`), or pull its full report (`get_session_report`).
- **Workflow templates**: create (`create_workflow_template`), look up (`get_workflow_template`), or update (`update_workflow_template`) a saved set of checks.
- **Group links**: list your group links (`list_links`), create one (`create_link`), or turn one on or off (`update_link_status`).
- **Billing**: check your credit balance, grants, and subscription state (`get_wallet`).
- **Compliance**: open a data subject access or erasure request for an applicant (`create_data_subject_request`).

Every tool is limited by your role and your plan; the assistant only sees what you are allowed to use. Ask it to run `list_available_capabilities` at any time to see what your plan currently allows and what upgrading would unlock.

<Aside type="tip" title="Building your own integration?">
The same connector also accepts an API key instead of an interactive sign-in, so your own application can call it directly and scope each call to one of your sub-accounts. See [Create an API key](/developers/api-keys) to set one up.
</Aside>

## Related

- [Integrations overview](/guides/integrations)
- [Create an API key](/developers/api-keys)
- [Glossary](/glossary)