99.4%
of records matched a customer’s own database, audited across 10,000,000 rows
Bonus
Optimized for AI agents
Plug in our MCP server. Your agents pull supply and pay per result themselves.
→
MCP
Send your contact list. We check each person against the live page and flag who moved.
People change jobs every single month, and nothing in your CRM moves when they do. Deals stall because the champion left, and outreach that names the old company goes straight to delete.
We read each contact’s live public page in about 0.2 seconds and hand back who changed jobs. You can run it on your own cadence: daily, weekly, monthly, or before every campaign.
Get 3,000 free creditsPaste URLs, upload a CSV, or hit the batch endpoint. The free 3,000 credits every month cover your first run.
| INPUT URL | CURRENT COMPANY | CHANGED |
|---|---|---|
| /in/satyanadella | Microsoft | false |
| /in/williamhgates | Gates Foundation | false |
| /in/… | exists_not_public | flagged, free |
| /in/… | not_resolvable | flagged, free |
The numbers on the left are not our benchmark. An enterprise customer ran them against their own 400M-record database before buying.
Batch results land on your webhook, so a flagged move becomes a CRM update, a Slack ping, or the first line of a congratulations email. Your stack, your play.
Plug in our MCP server. Your agents pull supply and pay per result themselves.
→
MCP
We read public, logged-out pages, with no accounts and no fake profiles. Logged-out, public-only collection has repeatedly defeated computer-fraud and contract claims. The vendors that got shut down were logging in, and we never do.
LinkedIn only notifies existing connections, and only when the person posts about it. The reliable way is to re-check the profiles you care about on your own schedule and alert on what changed. One credit per successful check.
You still get an answer. The response says whether the profile is live, private, or gone, and a check that comes back not accessible costs nothing.
Yes. POST up to 100 URLs to the batch endpoint for an instant response, or up to 10,000 with a webhook and we deliver the results to your endpoint when the run finishes. Loop batches for bigger lists.
A refresh check does not. When a move is worth acting on, call type=profile with email=true, which adds a work email plus a verified, pattern-likely, or unknown status where one can be found. Same billing, one credit per successful call.
A refresh check catches company moves. For a title change inside the same company, call type=profile, which returns the current title from the public page. Same billing, one credit per successful call.
Every check reads the live public page at the moment you ask, not a stored copy. Checks come back in about 0.2 seconds.
