How it works
Start calling 6sense intelligence in three steps.
Use Cases
One API layer. Purpose-built for every GTM function.
See what success looks like.
Marketing, sales, and operations finally work from the same source of truth — the same signals, the same timing cues, and the same understanding of which accounts are actually ready.
The amount of work Email Agents do in a day would take someone on my team a week to do. It’s like having five more SDRs working simultaneously.
The intent data told us who to talk to. AI Email is what made actually talking to them possible, over months, without hiring anyone to do it.
Not having 6sense is like walking into a room with the lights off. How would you know where to look for the accounts that matter in the market? That’s what 6sense has brought to us.
Frequently asked questions.
It depends on the API. The Company Identification and Company Firmographics APIs require a 6sense Platform subscription. Lead Scoring requires the Advanced package. People Enrichment is an add-on that works with any Platform or Sales Intelligence subscription. Your account team can confirm what's included in your current agreement.
There are two credit pools: Company Identification credits (used only for the Company Identification API, one credit per matched IP) and Enrichment credits (shared across the Company Firmographics, Lead Scoring & Firmographics, and People Enrichment APIs). People Search and Lead Scoring don't consume credits. One useful benefit: once a record is enriched, you can re-export it for up to a year without consuming additional credits.
Go to Settings > API Token Management in the 6sense platform. 6sense recommends creating a unique token per integration or use case, this makes usage tracking and troubleshooting much cleaner. Tokens should be rotated every 90 days. For Segments API access, contact 6sense support directly.
All APIs enforce a baseline of 100 requests per minute. The People Enrichment API supports up to 20 queries per second, with batches of up to 25 contacts per call. If your use case requires higher limits, contact your CSM, limits can be adjusted.
They expose the same underlying intelligence. The REST APIs are for direct programmatic integration, CRM enrichment, scoring pipelines, custom applications. The MCP Server wraps that same intelligence in the Model Context Protocol so AI agents can call it as a named tool, with no custom connector required.
The API returns a company match status for every call: "Match" (a valid company was identified), "Non-actionable Match" (the IP resolved to a bot, host, or non-B2B entity), or "No Match." Non-actionable matches are flagged so you can filter them out of downstream workflows.
