# Slintel > Slintel was a B2B sales and market intelligence platform — company firmographics, > technographic installs, psychographics and buying-intent scores used by revenue teams > to prioritize accounts and time outreach. Founded in 2016 and backed by Accel and > Sequoia, Slintel was acquired by 6sense on 2021-10-05 and folded into the 6sense > Revenue AI platform. **Slintel no longer operates a developer surface of its own.** > This file is generated by API Evangelist from the catalog record and from live probes > run on 2026-08-14; it is not published by Slintel. ## Status - Brand status: acquired, retired into 6sense (announced 2021-10-05) - `https://slintel.com/` — HTTP 301 on every path to `https://6sense.com/platform/sales` - `https://www.slintel.com/` — HTTP 403 to automated clients (Cloudflare bot challenge) - `api.slintel.com`, `app.slintel.com` — DNS records survive, but the AWS load balancers they point at no longer resolve; both hosts are unreachable - No OpenAPI, AsyncAPI, GraphQL SDL, MCP server, agent card, `llms.txt`, `security.txt` or any other `/.well-known/` document is served by any Slintel host - No first-party SDK exists on npm, PyPI, RubyGems, crates.io, Packagist, NuGet or pkg.go.dev; there is no `slintel` GitHub organization ## Where the API went The programmatic surface that carried Slintel's data — company identification, firmographics, lead scoring and people/contact enrichment — is delivered today through 6sense, and is catalogued in this network under the `6sense` provider. - [6sense API reference](https://api.6sense.com/docs/): Company, Enrichment and People APIs - [6sense API overview](https://support.6sense.com/docs/6sense-api-overview): getting started, tokens, credits - [6sense support](https://support.6sense.com): help center - [6sense provider profile (API Evangelist)](https://apis.io/provider/6sense/): the full contract set, MCP server and artifacts Note: 6sense's own API reference does not mention Slintel. The 6sense APIs are published by 6sense and are scored as 6sense's; they are linked here as the successor surface, not claimed as Slintel's. ## This profile - [apis.yml](https://raw.githubusercontent.com/api-evangelist/slintel/refs/heads/main/apis.yml): the APIs.json record for Slintel - [lifecycle/slintel-lifecycle.yml](https://raw.githubusercontent.com/api-evangelist/slintel/refs/heads/main/lifecycle/slintel-lifecycle.yml): end-of-life record and acquisition evidence - [well-known/slintel-well-known.yml](https://raw.githubusercontent.com/api-evangelist/slintel/refs/heads/main/well-known/slintel-well-known.yml): the `/.well-known/` probe, recording a complete absence - [packages/slintel-packages.yml](https://raw.githubusercontent.com/api-evangelist/slintel/refs/heads/main/packages/slintel-packages.yml): the registry sweep, recording zero SDKs - [security/slintel-domain-security.yml](https://raw.githubusercontent.com/api-evangelist/slintel/refs/heads/main/security/slintel-domain-security.yml): TLS/DNSSEC/SPF/DMARC probe of slintel.com