Frequently asked questions — B2B identity graph & architecture.
Clear answers regarding GraphIQ.ai's entity resolution engine and native MCP agent integrations.
How does an Identity Graph differ from a standard B2B contact database?
Standard directories store data in flat, disconnected rows. GraphIQ.ai treats global business data as an interconnected knowledge network of 287M organizations, 393M people, and 2B+ news articles. Every legal entity name variant, international subsidiary, office location, or title change resolves back to a single canonical entity node.
What is your data update velocity?
GraphIQ.ai processes 300,000 to 400,000 news articles and signals daily and updates entity records continuously as new information arrives.
What is an MCP server, and how do our AI agents use it?
The Model Context Protocol (MCP) is an open standard. GraphIQ.ai hosts a native HTTP MCP server (https://app.graphiq.ai/mcp). This allows Claude, ChatGPT, Microsoft Copilot Studio, Cursor and any AI tool that supports remote MCP servers to query our 287M organization graph natively, grounding answers in resolved entities instead of scraped text.
What is GraphIQ.ai?
GraphIQ.ai is a B2B identity graph that resolves 287M organizations into structured, continuously updated data — employees, relationships, signals, and corporate hierarchies — accessible to your revenue team and AI agents through the product UI, API, and MCP server.
How does GraphIQ.ai connect to my CRM?
GraphIQ.ai operates as a headless data layer, prioritizing a Model Context Protocol (MCP) first engagement that streams relationship data directly to your AI workflows. GraphIQ.ai is delivered via the web UI, REST API and MCP server. Teams can enrich CRM records headlessly through the API or MCP. The team will confirm connector options on a demo.
How does GraphIQ.ai compare to ZoomInfo, Apollo, or Clay?
Unlike rigid, row-based legacy directories like ZoomInfo or Apollo, GraphIQ.ai is designed as a headless B2B knowledge graph built for native MCP and AI agent engagement. Rather than functioning as a surface-level workflow overlay, we serve as the primary underlying data layer, exposing transparently cited entity relationships directly to your stack.
What are the core use cases for your platform?
GraphIQ.ai primarily powers CRM data enrichment, outbound GTM prospecting, deep account intelligence, and market signal monitoring. It is also heavily utilized for vendor and supply-chain review and diversification, competitive benchmarking, and building custom internal data pipelines via our API.
Does GraphIQ.ai work with AI agents?
Yes. GraphIQ.ai exposes its identity graph via an MCP server (Model Context Protocol), giving Claude, ChatGPT, Microsoft Copilot Studio, Cursor and any remote MCP client structured B2B context to reason over — not flat-file exports.
What makes GraphIQ.ai a graph rather than a database?
A database stores flat rows of records. A graph resolves real-world entities — every company linked to its subsidiaries, employees, active signals, and industry connections through resolved graph edges. When you query GraphIQ.ai for Lucasfilm, you receive the full 153-entity corporate family tree, not an isolated row of text.
How is data kept current?
GraphIQ.ai processes signals daily — job change events, news, regulatory filings, active hiring postings, and relationship updates — across billions of data points in the graph, each drawn from public sources and carrying a confidence score. Every record reflects live state, not a stale quarterly batch refresh.
What interfaces does GraphIQ.ai support?
The web UI, REST API and MCP server. Claude, ChatGPT, Microsoft Copilot Studio, Cursor and other MCP clients can query the graph. The team will confirm connector options on a demo. MCP server access requires a paid MCP account.
How many organizations does GraphIQ.ai cover?
287M organizations as of current indexing. Coverage is global, with highest density in North America, Western Europe, and Asia-Pacific.
How often is the graph updated?
Continuously. GraphIQ.ai processes signals daily and updates entity records as new information arrives. There is no fixed batch-refresh cadence.
Can AI agents query the identity graph directly?
Yes, via the Model Context Protocol (MCP) server with a paid MCP account.
How many seed accounts do I need?
Minimum 3 to 5 resolved accounts. Seeds can be submitted as domain lists, CRM exports, or entity IDs.
Can I run lookalike discovery programmatically via the MCP server?
Yes. Ask your agent for companies similar to a set of anchor accounts, and it calls the MCP Organizations tools for you. Requires a paid MCP account.
Does lookalike matching update as new organizations enter the graph?
Yes. The identity graph processes 300,000 to 400,000 news articles and signals daily. New organizations matching your seed fingerprint surface automatically.
How do autonomous AI agents query the signal feed?
Through the MCP News tools, which return deduplicated coverage of a company with sentiment scores. Ask in plain English, or use the News monitoring playbook to track funding, M&A, launches and leadership changes across a set of companies.
Is our data connection restricted to specific LLM model providers or clients?
No. MCP is a provider-agnostic standard, so the server works with any AI tool that supports remote MCP servers. That includes Claude, ChatGPT, Microsoft Copilot Studio and Cursor.
What is the difference between the REST API and the MCP server?
REST for traditional integrations — ETL pipelines, batch enrichment. MCP for AI agents that need to query the graph as part of an active reasoning loop.
What makes Fingerprint Search different from keyword or boolean search?
Keyword and boolean search match against text strings. Fingerprint Search matches against a capability profile constructed from your plain-English description.
Can Fingerprint Search handle multi-dimensional queries?
Yes. The fingerprint parser decomposes compound queries into dimensional components — capability cluster, geographic constraint, organizational scale, corporate hierarchy position, and real-time signal filter.
How accurate is Fingerprint Search compared to legacy alternatives?
GraphIQ.ai programmatically caps immediate fingerprint matches to a couple of thousand companies at most, to keep every match tightly aligned with your query.
Why restrict matches instead of returning tens of thousands of records?
GraphIQ.ai limits initial semantic outputs to a couple of thousand highly resolved company entities because it forces maximum alignment with real-world capability footprints across our 287M organization graph.
Why is selecting GraphIQ.ai framed as an architectural choice rather than a traditional software purchase?
Traditional providers act as applications — SDRs use them for isolated profile lookups, creating fragmented data silos that decay quickly inside your CRM. GraphIQ.ai is an infrastructure layer. It synchronizes data modifications across your data warehouse, product applications, engineering workflows, and human pipelines simultaneously, ensuring your entire ecosystem moves from a single resolved system of record.
How does the graph architecture allow our business to grow without data friction?
As your organization scales into new verticals, launches product lines, or expands headcount, our graph responds elastically. You can provision data access for newly acquired teams, spin up internal automation codebases, or deploy autonomous AI agent loops on the same graph.
Which industries and teams can use the same GraphIQ.ai data layer simultaneously?
All of them — from the same architecture. Revenue operations teams use it for CRM enrichment and territory design. Sales and marketing teams use it for account-based prospecting. Developers and AI teams connect via REST or MCP for agent grounding. Government and defense procurement teams use it for supply chain mapping. Private equity and VC firms use it for proprietary deal sourcing. One data layer, zero duplication of infrastructure costs.
How do you handle hyper-niche verticals without standard NAICS codes?
We map company capabilities by evaluating real-time operational signatures — job description syntax, SEC filing annotations, product documentation keywords, and vendor registries.
Can we build and export custom micro-verticals via the API or MCP?
Yes. Delivered as clean, structured JSON-LD payloads — ready for your warehouse, CRM, or AI agent.
Can GraphIQ.ai replace ZoomInfo entirely?
For relationship-driven GTM — account hierarchies, lookalike discovery, and agent-ready data — yes. Some teams keep their current provider for some time while they get used to managing via relationships and not rows. We'll give you a straight answer for your use case.
What does "graph-native" actually change day to day?
Instead of exporting a list and stitching parent/child accounts together yourself, you ask the graph a question — "show every subsidiary of this account that's hiring" — and traverse the answer directly. Agents can do the same through the MCP server.
Is there a free way to try it before switching?
We offer a 2 week free trial — start at Try for Free or book a demo and the team will get you set up before you commit.
Can GraphIQ.ai replace Apollo entirely?
Partly. GraphIQ.ai replaces the data layer with a graph — but it isn't an outreach tool. If you rely on Apollo's built-in email and dialer, keep that and let GraphIQ.ai feed it better-targeted, relationship-aware accounts.
Is GraphIQ.ai a Clay competitor?
No. Clay orchestrates enrichment and automation across many sources; GraphIQ.ai is one of those sources — the graph-native one. They're designed to sit together, not replace each other.
How do I connect GraphIQ.ai to Clay?
Add it as an HTTP API enrichment in your Clay table, or call the GraphIQ.ai API from a Clay HTTP step. Authenticate with your API key and map a domain column as the input.
What fields can I pull into a Clay table?
The resolved entity ID, corporate hierarchy (parent and subsidiaries), people with titles drawn from public sources and a confidence score, and live signals such as hiring, funding, and M&A activity.
How is this different from normal enrichment?
Standard tools match on strings and append fields; GraphIQ.ai first resolves each record to a unique entity, so the data attaches to the right account — and its hierarchy — instead of a near-match.
Will it create duplicates?
The opposite. Entity resolution collapses existing duplicate records into a single canonical entity, each with a confidence score you can audit.
Which CRMs are supported?
Any CRM you can reach by API or through Clay. GraphIQ.ai returns resolved entities and fields you write back to your records.
What does “graph-weighted” mean?
Each account is scored not just on size, but on its position in the graph — family relationships, connected entities, and live signals — so a territory's weight reflects real opportunity, not a headcount proxy.
Can I keep my existing territory rules?
Yes. Layer graph weighting on top of your geo or segment rules to refine the model you already run — you don't have to start from scratch.
How often can we rebalance?
As often as you like. The underlying graph updates continuously, so re-running territory math is a query you can repeat every planning cycle — or more.
How deep does the hierarchy go?
As deep as the graph resolves — from global ultimate parents down to local subsidiaries and acquired brands, each represented as its own entity you can act on.
Can I run this on my whole customer list?
Yes. Pass your closed-won accounts and GraphIQ.ai returns the full corporate family for each, ranked by fit and signals — in the app, via API, or through the MCP server.
Does it stay current as companies restructure?
Yes — mergers, acquisitions, and corporate-family changes are ingested continuously, so new subsidiaries surface and stale links retire automatically.
What is the MCP server?
A Model Context Protocol endpoint that lets LLMs and agents call GraphIQ.ai directly — resolving entities and traversing the graph as native tools, with no export step in between.
Do I need Clay or a CRM to use it?
No. Agents can query the MCP server directly; Clay and your CRM are optional activation targets for whatever the agent resolves.
How do you prevent hallucinated connections?
The graph returns resolved entities with confidence scores and provenance, so agents act on resolved relationships instead of inferring them from raw text.
Still have a question?
Browse the technical docs or talk to our team directly.