Which Snitcher product do I need? Dashboard vs Spotter vs Radar vs IP2C vs API vs MCP

Snitcher is a few different products that all work from the same company-identification data.

Which one you need depends on one main thing: do you want a finished product you log into and use, or are you building visitor identification into your own software?

This guide walks you to the right one.

Do you want a finished Snitcher product, or are you building this into your own software?

The quick version, then a short description of each below:

For: marketing and sales teams who want to see which companies visit their site and act on it.

The main Snitcher product. You install the tracker, and you get a dashboard with company identification, segments, alerts, and CRM sync, no building required.

This is the right choice for the large majority of customers: lead follow-up, ABM against a target account list, lost-deal reactivation, and reporting on audience quality all live here.

Where to go next: How to install the Snitcher tracker, and the Lost-deal reactivation recipe for a popular example.

For: agencies and resellers who want to run Snitcher for their clients and earn commission, without building software.

Each client is their own Snitcher workspace and subscription, managed from a partner portal.

This is the route if you want a ready-made product to offer clients across their sites. It is not a rebranded single dashboard you build on, if you want to build visitor identification into your own product, see the embedded route below instead.

Where to go next: Snitcher Partner Program.

For: teams already using Dashboard who want company data available live on their own website, for personalisation or form enrichment.

Spotter is real-time, client-side company identification. It is a small piece of JavaScript that runs on your site and returns the identified company in the browser, so you can do things like show a visitor their own company logo, or write the identified company into a form submission.

It is included with Dashboard, needs the Snitcher tracker and authorised domains, and requires no API key. Identification is asynchronous and can be missing, so build for that, and note there is no exposed confidence score.

Where to go next: Getting Started with Spotter.

This is for companies putting Snitcher's identification infrastructure inside software they sell to their own customers. It has two layers, and which you need depends on whether you already collect website activity.

IP2C (IP-to-Company) resolves a visitor to a company. If you already collect visitor IP addresses yourself and only need the company-resolution step, IP2C alone is enough.

Radar is the tracking and event-collection layer. It collects website activity and streams events or completed sessions to your webhook; you then choose which sessions to enrich through IP2C.

If you need Snitcher to collect the website activity, or you want the higher match rate that comes from session-based identification rather than raw IP lookups, you want Radar plus IP2C.

A short way to hold it: Radar collects and organises website behaviour; IP2C resolves selected visitors to companies. You build the UI, workflows, billing, and integrations around them.

A quick check on whether this route fits you. A good embedded-product case has a real software product (or a funded near-term launch), customer websites or design partners, a technical owner, and a defined output.

Simply being able to call an API is not enough, if you are a marketing agency without a software product, the Partner/Agency route above is the better fit even if you could technically use the API.

IP2C agreements normally start at $10,000 per year. Radar has its own standalone pricing when used for raw tracking without the identification contract.

Pricing depends on volume and whether Snitcher attribution is displayed, so the exact commercials come from a conversation with sales.

Where to go next: IP to Company API and Radar. To get access, talk to sales.

For: customers who want their own Snitcher data in another internal tool or workflow.

Use the REST API to pull your data on demand, for example into your own reporting tool.

Use Webhooks to have Snitcher push configured events to any endpoint as they happen. A custom in-house CRM with no native integration can use either, though sending webhooks straight into a CRM without deduplication can create duplicate records, so treat it as a custom integration (often with middleware in between), not a native two-way sync.

On access: the REST API token follows the user and can reach the workspaces that user has access to. You do not need to request a key separately.

Where to go next: REST API and Webhooks.

For: teams who want to reach their Snitcher data from an AI assistant.

If you use an MCP-compatible AI assistant, you can connect it to your Snitcher workspace and ask questions or make changes in natural language, useful for retrospective analysis of your data, or reviewing and adjusting your ICP scorecard (with a confirmation step before it changes anything).

Reading and analysing your data through MCP does not consume Snitcher AI or reveal credits, only revealing a contact's email consumes reveal credits, exactly as it does in the app.

Where to go next: Connect your AI assistant to Snitcher (MCP).

So you can rule these out quickly:

If one of those is what you need, Snitcher is not the right tool for that job.