One call per company
48 fields in JSON: platforms with grades and dates, email platform and gateway, posture, hosting, changes.
GTM engineers
A feed, not a dashboard.
REST API and MCP connector. JSON with platforms, grades and dates, for Clay, a warehouse or your own enrichment pipeline.
What you get
Built for GTM engineers
Claude reads the graph
The MCP connector lets Claude answer what an account runs, straight from the graph, inside your own agents.
Bulk when you need it
Full files and scheduled cuts to Snowflake or S3 under a data licence, when the API is not the right shape.
From the graph
The numbers behind it
Floors as of 2026-09. A floor, not a market total: IXM counts only companies whose public signals it has verified, and the graph grows every day.
48fields per company
2.9M+companies queryable
382K+changes in the last 30 days
1,300+vendor signatures
Worked example
From an API key to an enriched table
| Step | What you do | What comes back |
|---|---|---|
| 1 | Create a key on a Growth or Scale plan | Rate and daily limits set by plan |
| 2 | Call the company endpoint from Clay or your pipeline | JSON with platforms, grades, dates and posture |
| 3 | Poll the changes endpoint | Adoptions, removals and switches since your last run |
Delivered via:
REST API
MCP for Claude
Snowflake
S3
CSV
Questions
Before you start
What are the limits?
Requests per minute and per day are set by plan and shown in the app. The docs list current values and the MCP setup.
Is there a sandbox?
The free account lets you enrich up to 100 domains in the app. API keys start on Growth.
What does a change look like?
A company, a platform, a direction (adopted, removed, switched) and a date, so you can diff against your own store.
Trademarks belong to their owners. Vendor names identify the platform a company runs; they imply no endorsement.