The Swarm organizes data around profiles (people) and companies, and maps connections, how individuals relate through work, education, investors, or shared contacts. These connections are powered by connectors (email, calendars, CRMs, LinkedIn, and other data sources) that feed relationship signals into the system. All of this lives within teams, so users can see not just their own network but the collective reach of their organization. Profiles and companies are enriched in real time, while the Network Mapper API surfaces connection paths with strength scores, making it possible to identify warm intros, overlaps, and trusted relationship routes at scale. The data has three layers:Documentation Index
Fetch the complete documentation index at: https://docs.theswarm.com/llms.txt
Use this file to discover all available pages before exploring further.
- Profiles & Companies (the raw entities),
- Connections (how they relate),
- Connectors & Teams (how data is pulled together and shared).
Profiles
id– unique person identifiername,title,emails,linkedin_slug– core identitywork_history,education_history– context for overlaps
Companies
id– unique company identifiername,website,industry– core identitysize,headcount,locations– structure and scalefunding,investors,ownership_status– business datatech_stack,social_media– signals and footprint
Connections
profile_iduser_id– who is connected to whomorigin– type of connection (work overlap, education, LinkedIn, email, calendar, investor, manual)strength_score– normalized measure of relationship depthsources– evidence supporting the connection
Connectors
id– unique connector identifiertype– email, calendar, CRM, LinkedIn, etc.status– active/inactivescope– which data is being ingested
Teams
team_id– organizational groupingmembers– list of profiles connected to the teamconnectors– integrations tied to that teamnetwork_map– combined relationship graph across membersinNetworkOnly– include profiles that are connected to your team’s network

