IXM Explorer
Sign in at app.ixm.ai, paste your own accounts or search the whole graph by platform, filter, and export CSV within your plan.
The data
How the intelligence is made
When a company adopts a vendor, it leaves signals it publishes itself. IXM reads those signals for millions of companies, every month.
Coverage
Coverage
Millions of companies across 225 countries, thousands of vendors, dozens of data points each, re-read every month. Every count is a floor. See the coverage, freshness and depth of the graph.
Method
How a relationship enters the graph
Before a vendor will send mail, sign documents or log users in, the company has to set it up on its own domain. That setup leaves public signals: proofs of ownership, service routing, delegations.
IXM reads those signals on a schedule, matches them to thousands of vendor signatures, grades each one and keeps first-seen and last-seen dates. Public signals only: no logins, no crawling, no people’s names or contact lists.
One signal, end to end
From a public signal to a graded row
1The company adopts a vendor
acme.com · sets up AnthropicTurning the product on leaves a signal the company publishes itself. It is public by design.
2IXM observes and matches
signal → Anthropic signature · first seen · last seenScheduled reads across millions of companies; thousands of vendor signatures; dates kept.
3A graded row
acme.com · Anthropic · vendor verification · Verified · 2026-09-01Exported as CSV, searched in the app, or pushed to your CRM.
Confidence
Confidence grades
| Grade | Evidence | Typical use |
|---|---|---|
| Verified | A vendor-specific verification signal on the company's own domain | Displacement lists, TAM counts, diligence |
| Strong | The company routes a live service, such as mail, through the vendor | Ecosystem targeting, ABM audiences |
| Inferred | Secondary or historical evidence, or a signal last seen more than 90 days ago | Enrichment, with a human check |
Every export and API response carries the grade. Download a sample CSV (example data, real layout).
Schema
Data fields
| Field | Description |
|---|---|
| domain | Apex domain where the signal was observed (one row per domain) |
| platform | The platform matched, e.g. Anthropic, Salesforce, DocuSign |
| evidence | The kind of signal that matched: vendor verification · service routing · delegation |
| confidence | Verified (vendor-specific signal) · Strong (live service routed through the vendor) · Inferred (secondary evidence) |
| last_seen | Date of the most recent observation (ISO 8601) |
| platforms_all | Every other platform seen on the same domain (semicolon-separated) |
| email_platform | Mail provider, e.g. Google Workspace, Microsoft 365 |
| email_security | Authentication and anti-spoofing posture of the domain (present on platform exports) |
| hosting_country · asn | Location and network of the domain's primary web host |
| hq_country · size_band · industry | Enterprise data licence only, on request |
Delivery
Delivery formats
IXM API
REST API and MCP connector on Growth and above. JSON, documented at app.ixm.ai/api-docs/.
Salesforce and HubSpot
Push accounts into Salesforce or HubSpot through the API with the included setup guides, Growth and above.
Data licence
Snowflake share, S3 bucket, AWS Data Exchange; Parquet or CSV.
Refresh
Freshness
Every row carries its observation date. One-off lists are cut at order time; platform plans see updates as they land.
Limitations
What the data does not tell you
- A signal proves a relationship exists. It does not show seat count, contract value or usage.
- Signals can remain after a contract ends. Treat last-seen as an observation date, not a churn date.
- Some vendors leave signals we cannot observe, so we under-count them and say so in the vendor catalogue.
- A routing signal shows a vendor may act for the company. For marketing platforms that is strong evidence; for transactional relays it is weaker, and we grade accordingly.
- Company resolution is automated and audited on a sample before each release. Report an error and we fix it in the next refresh.
- first_seen is the date we first observed a signal. For relationships that existed before our first observation, it is the date of that first crawl, not the date the company adopted the vendor.
- One company may own several domains, and a domain may belong to an individual. We de-duplicate to companies and exclude domains that identify a person, and we publish the residual rate with every pack.