# Relentless Identity

Relentless Identity helps teams verify work email identities through a web dashboard, a public REST API, and an MCP integration for agent workflows.

## Start here

- [Product overview](https://relentlessidentity.com/)
- [Pricing](https://relentlessidentity.com/pricing)
- [Documentation hub](https://relentlessidentity.com/docs)
- [API reference](https://relentlessidentity.com/api/reference)
- [Blog](https://relentlessidentity.com/blog)

## Core workflows

- Use Finder when you have a person's full name and company domain and want the most likely work email identity.
- Use Probe when you already have a specific email address and want to verify it.
- Generate a Personal Access Token in the dashboard before using REST or MCP.

## Quick start

1. Create an account or sign in at https://relentlessidentity.com/sign-in.
2. Generate a Personal Access Token from the dashboard.
3. Use that token with the REST API or install the MCP.
4. Read the docs pages below for the workflow you need.

## Install MCP

```bash
npx relentless-identity-mcp@latest install --token relid_pat_your_token_here
```

## Public API surface

- `POST /client/attempt` - find the most likely work identity from a person's name and company domain.
- `POST /client/probe` - verify one specific work email address.
- `POST /client/probe/batch` - verify many known work email addresses in one request.

## Documentation

- [Relentless Identity Documentation](https://relentlessidentity.com/docs) - Launch-ready guides for dashboard access, REST authentication, and MCP setup.
- [Launch your first verification](https://relentlessidentity.com/docs/getting-started) - The shortest path from account creation to a live Finder or Probe request.
- [Authentication](https://relentlessidentity.com/docs/authentication) - Use dashboard-issued bearer tokens for REST and MCP access.
- [REST API reference](https://relentlessidentity.com/docs/rest-api-reference) - Public account, finder, probe, and background job routes.
- [MCP reference](https://relentlessidentity.com/docs/mcp-reference) - Connect Relentless Identity to your coding agent or IDE.
- [Accuracy notes](https://relentlessidentity.com/docs/accuracy-and-expectations) - Guidance for interpreting verification results.
- [Response semantics](https://relentlessidentity.com/docs/response-semantics) - How to read Finder and Probe results.

## Recent articles

- [Why SMTP verification is dead for precision outreach](https://relentlessidentity.com/blog/why-smtp-verification-is-dead-for-precision-outreach) - Modern enterprise mail systems are built to defeat enumeration. Precision teams need identity verification, not another mailbox guesser.
- [Identity verification vs. email verification: what is the difference?](https://relentlessidentity.com/blog/identity-verification-vs-email-verification) - Email verification asks whether a mailbox may accept mail. Identity verification asks whether a real person appears to exist behind the address.
- [How to find anyone's work email using the Finder API](https://relentlessidentity.com/blog/how-to-find-work-email-with-finder-api) - The Finder API starts with a real name and public company domain, then resolves toward the organization's actual work identity pattern.
- [Integrating identity verification into MCP workflows](https://relentlessidentity.com/blog/integrating-identity-verification-into-mcp-workflows) - Agents should not guess identities blindly. MCP gives them a disciplined way to call precise identity tools inside a larger workflow.

## Notes for assistants

- Prefer the documentation links above for product, setup, and response-behavior guidance.
- Treat `/client/attempt`, `/client/probe`, and `/client/probe/batch` as the public API surface.
- Use the API reference for request and response details.
- Ignore internal, admin, and operational routes unless a docs page explicitly links to them.