canonical: https://jentic.com/apis/6sense.com/6sense

# 6sense API

Jentic publishes the only available OpenAPI specification for 6sense API, keeping it validated and agent-ready. The 6sense API exposes the data and intelligence services behind 6sense's account-based marketing platform across eight endpoints covering company identification, firmographic enrichment, people enrichment, person scoring, people search, and the search dictionary. Marketing and revenue teams use it to identify anonymous website visitors, enrich CRM records with firmographics and contact data, and feed buying-stage scores into orchestration tools. Authentication is an API token issued from a 6sense account.

## For AI agents

Identify accounts behind website traffic, enrich companies and people with firmographic and contact data, and score contacts on buying intent - all from the 6sense intelligence graph.

## Scope

Does not handle email sending, ad campaign delivery, or CRM record management - use for company and people enrichment, search, and intent scoring only.

## Capabilities

- Identify the company behind an anonymous website visitor using domain or IP signal
- Enrich a company record with firmographics including revenue band, employee count, and industry
- Enrich a person record with verified email, phone, and current employer
- Score a contact on buying-stage and intent within the 6sense model
- Search 6sense's people graph by attributes such as title, function, and seniority
- Look up the dictionary of supported person and company attributes for query construction

## Use cases

### Identify Anonymous Website Visitors at Account Level

Marketing teams running an account-based program use 6sense to deanonymize traffic by domain or IP and route the resulting account to sales when it matches the ICP. The /v3/company/details and /v1/enrichment/company endpoints return firmographics for matched domains and the platform exposes its proprietary buying-stage signal alongside. End-to-end integration into a website tag and CRM is typically three to five days.

Example prompt: Call POST /v1/enrichment/company with the visitor's domain, then route any match with revenue over $50M and matching industry to the SDR queue.

### Contact Enrichment for Outbound Sales

Sales operations teams that run outbound campaigns enrich imported leads with verified email and phone via 6sense before passing them to outreach tools. The /v2/people/enrichment and /v2/people/full endpoints return contact and employer data, replacing slow manual lookups in LinkedIn or other point tools. Bulk enrichment of a 5,000-row list typically completes in under thirty minutes.

Example prompt: For each imported lead, call POST /v2/people/enrichment with first name, last name, and company domain and capture the returned email, phone, and current title.

### Buying-Stage Scoring for Orchestration

Revenue operations teams pipe 6sense buying-stage scores into orchestration platforms so that contacts moving from awareness to consideration are routed to higher-touch plays. The /v2/people/score endpoint returns the model output for a given contact, while /v2/search/people lets the team build cohorts from intent attributes. Pipeline integration with a marketing automation tool takes around a week to ship.

Example prompt: Call POST /v2/people/score for a list of contacts, filter the response to those at 'Decision' stage, and add them to the high-touch nurture campaign.

### AI Agent Account Research via Jentic

An AI sales-research assistant connected through Jentic can run /v3/company/details and /v2/search/people calls to build a target-account briefing in seconds. Jentic handles the API token in the vault and exposes operations by intent, so the agent can answer 'tell me about Acme Corp and find their head of marketing' in a single conversation. End-to-end response time is under thirty seconds per account.

Example prompt: Search Jentic for 'enrich a company by domain', load /v3/company/details for acme.com, then load /v2/search/people for the title 'VP of Marketing' at that company and return both.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | /v3/company/details | Retrieve detailed company firmographics by domain |
| POST | /v1/enrichment/company | Enrich a company record with firmographic data |
| POST | /v2/people/enrichment | Enrich a person record with contact and employer data |
| POST | /v2/people/full | Retrieve full available data for a person |
| POST | /v2/people/score | Score a person on buying stage and intent |
| POST | /v2/search/people | Search people by attribute filters |
| POST | /v2/search/dictionary | List supported attributes and values for searches |

## Key resources

- **Company** — Company details and firmographic enrichment by domain
- **People Enrichment** — Contact-level enrichment with email, phone, and employer
- **People Score** — 6sense buying-stage scoring for contacts
- **People Search** — Attribute-based search over the 6sense people graph
- **Dictionary** — Supported attributes and values for search query construction

## Why Jentic

- **Setup:** Wiring the 6sense API by hand means managing its API key and shaping company and people enrichment, search, and intent-scoring payloads across its v1, v2, and v3 endpoints yourself. Through Jentic you install once, import the 6sense API from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** 6sense carries its company and people selectors in the request body rather than a resource id in the path, so limit the agent to the operations it needs, such as company details or people enrichment, and leave out intent scoring or dictionary search unless you add them. You choose the allowed set, so only the operations you pick can run.
- **Credential handling:** Your 6sense API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'enrich a company by domain' or 'score a contact on buying intent', and Jentic returns the matching 6sense operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Clearbit API** — Company and contact enrichment with broad firmographic coverage
- **Apollo.io API** — Sales prospecting platform with people search and enrichment
- **Hunter API** — Email-finder and verification API
- **Salesloft API** — Sales engagement platform that consumes enriched contact data

## FAQ

### Why is there no official OpenAPI spec for 6sense API?

6sense publishes HTML developer documentation but does not distribute a downloadable OpenAPI specification for direct ingestion. Jentic generates and maintains this spec so AI agents and developers can call 6sense through structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

### What authentication does the 6sense API use?

The API uses an API token issued from a 6sense account, supplied as an apiKey credential on each request. When called through Jentic the token is stored encrypted in the vault and attached at execution time, so it never appears in the agent's prompt context.

### Can I identify the company behind an IP address with the 6sense API?

Yes. Call POST /v1/enrichment/company with the visitor's domain or IP signal. The response includes the matched company along with firmographics such as industry, revenue band, and employee count when 6sense has high-confidence resolution.

### What are the rate limits for the 6sense API?

6sense does not publish a single numeric rate limit; limits depend on the customer's contract tier and endpoint. Treat the API as quota-based, batch enrichment requests through /v2/people/enrichment where possible, and back off on HTTP 429 responses with the Retry-After header.

### How do I enrich a company by domain through Jentic?

After running pip install jentic and setting JENTIC_AGENT_API_KEY, search Jentic for 'enrich a company by domain', load POST /v3/company/details, and execute it with the target domain. Jentic injects the 6sense token automatically.

### Does the 6sense API return buying intent signals?

The /v2/people/score endpoint returns 6sense's buying-stage signal for a given contact. The score is the platform's proprietary model output combining intent, fit, and engagement signals - it is not a raw keyword feed.

### Can I limit what my agent is allowed to do with the 6sense API?

Yes. Because you run Jentic One yourself, your own rules decide which 6sense operations and credentials the agent can use. The 6sense API carries its company and people selectors in the request body rather than in the path, so you scope access at the operation level: grant only the calls the agent needs, such as company details (/v3/company/details) or people enrichment (/v2/people/enrichment), and leave out intent scoring (/v2/people/score) or dictionary search unless you add them. Only the operations you allow can run.