/
FAQ: New secure computing options for Meta Content Library API

FAQ: New secure computing options for Meta Content Library API

General questions

  1. What is changing for access to Meta Content Library API (MCL API)? 

Today, researchers can access Meta Content Library API on the secure computing platform operated by the Social Media Archive (SOMAR) at the Inter-university Consortium for Political and Social Research (ICPSR). Over the coming weeks, researchers will be able to choose between accessing the API on SOMAR’s secure computing platform, the Virtual Data Enclave, or on the Meta Secure Research Environment (formerly known as Researcher Platform).

 

  1. How will this change impact my access to the user interface for Meta Content Library? 

If you currently have access to the user interface for Meta Content Library, your access to the user interface will not be impacted.  

 

  1. Do these changes affect the application submission and review process for new applicants? What about for existing MCL API researchers who want to submit a new research agenda for review?

These changes do not affect the application submission or review process for Meta Content Library. Both new applicants and existing researchers with new project proposals are welcome to submit applications. When applying, the Meta Content Library application will now ask you to select one of the two platform options for API access. You may reference SOMAR’s application guide for more details.

Please keep in mind that the secure computing platform you select applies to all research agendas. Each individual must use only one platform.

 

  1. Is there a cost to use the SOMAR VDE or the Meta SRE?

The Meta SRE offers free computation.

Starting in January 2026, there will be a cost for users of the SOMAR VDE. These fees help ensure the continued sustainability and quality of ​S​OMAR services. The resources required to support the VDE - including computing infrastructure, storage, security, and staff time dedicated to VDE management and user support - represent significant ongoing costs. The charges allow SOMAR to maintain and improve the level of support and reliability you expect from our archive.

For Existing VDE Teams (per research team):
A monthly fee of 371 USD will be charged to your research team each month​ for the duration of your research project in the VDE.

For New VDE Teams (per research team):
A one-time fee of 1000 USD will be charged to your research team at the start ​of your project, as well as a charge of 371 USD each month for the duration of your research project in the VDE.

 

  1. I have additional questions about the platform options. Where can I reach out for support? 

If you have any additional questions on SOMAR’s VDE, please do not hesitate to reach out at somar-help@umich.edu. If you want to learn more about the Meta SRE, you can open a ticket through their support channel.

 

For researchers onboarded to the SOMAR Virtual Data Enclave

 

  1. What additional information can you provide about each of the two platform options so my research team and I can choose accordingly? 

Please reference the table below for detailed information on the SOMAR Virtual Data Enclave (VDE) and the Meta Secure Research Environment (SRE).

 

  1. Will the data available in Meta Content Library API remain the same regardless of which platform I choose?  

Yes. The full data scope of Meta Content Library API is available on both platforms.

 

  1. How will my platform selection impact my access to Meta Content Library API? 

If you choose to continue to use Meta Content Library API on the SOMAR VDE, your access to the API will not be impacted. 

If you opt to use Meta Content Library API on the Meta SRE, you will continue to have access to MCL API on the SOMAR VDE until early November. 

 

  1. How can I choose which platform I want to use and when is the deadline for making this decision? 

The Lead Researcher of your research team will need to opt in your team to use MCL API on the Meta SRE by filling out the emailed form by September 15. Forms submitted by collaborators will not be accepted. 

After the form is submitted, you will receive an automated reply from SOMAR with instructions on how your team can prepare code and data files that you want to transfer from the SOMAR VDE to Meta SRE.

If the Lead Researcher of a research team does not opt in to the Meta SRE by September 15, then the team will continue to access Meta Content Library API through the SOMAR VDE. 

 

  1. Our research team has decided to opt in to moving to the Meta Secure Research Environment. What happens next? 

September 15: This is the deadline to submit the form to record your platform decision. 

October 17: This is the deadline to prepare the code and data files you want to transfer to Meta, following the instructions you receive from SOMAR. 

November and beyond: This is the time period by which you will be able to access the Meta SRE and your transferred files. You will also be offboarded from the SOMAR VDE.

 

  1. If we opt into using Meta Secure Research Environment, can my research team and I transfer our files from SOMAR Virtual Data Enclave to Meta Secure Research Environment?

Yes, you will be able to transfer your code files and data from the SOMAR VDE to Meta SRE. You can bring in files of any format, including binary formats, code, models, images, etc. As a research team, you will have up to 330 GB of available storage for your transfer. 

If SOMAR has previously approved a machine learning model, you can also transfer this to the Meta SRE. 

 

  1. Can my research team (Lead Researcher and Collaborators) use Meta Content Library API on both the SOMAR Virtual Data Enclave and Meta Secure Research Environment?

No. You will only be able to access Meta Content Library API on one secure computing platform. 

All collaborators under a single Research Lead must use the same secure computing platform to access Meta Content Library API. 

 

  1. My research team missed/cannot make the September 15 deadline to opt into the Meta Secure Research Environment. What are our options if we want to change platforms at a later date? 

If you missed the September 15 deadline, you will have to wait until early November 2025 to switch platforms and must apply for access with Meta.

The transition process will also require more manual steps from you and your team—no direct file transfer from SOMAR to Meta will be available. You and your team will need to close out your SOMAR VDE project(s) by following SOMAR’s standard disclosure risk review and output vetting procedures for any research outputs you would like to export from the environment.

It is important to note that requests for output to be exported from the VDE need to be sent to SOMAR at least 10 business days ahead of a deadline to allow sufficient time for SOMAR staff to review and provide input to researchers. 

 

  1. I am a Lead Researcher. Do these changes impact my ability to add a collaborator to my approved research agenda? 

No. These changes do not impact your ability to add collaborators. Please have each of your collaborators submit a Collaborator Addition Request form.

 

For approved researchers in the process of onboarding to the SOMAR Virtual Data Enclave

 

  1. The Meta Content Library application for my research team has been approved, and we do not have a SOMAR VDE yet. Will we also be able to select a preferred platform option? 

Yes, you will be able to select which platform you will use to access MCL API. Please see the FAQ items below for the next steps. 

 

  1. Our research team has decided to continue to onboard to MCL API on SOMAR’s Virtual Data Enclave. What happens next? 

August 18 to October 17: The SOMAR team will have sent you an email asking about your API access. Please respond to that email so we know to onboard your team to SOMAR’s VDE.

The SOMAR team will create your VDE login credentials within 1 week of receiving your notice to continue with the SOMAR VDE. SOMAR will email you when your login credentials are created so you can set your own password.

SOMAR’s IT team will build your VDE instance. This takes 1-2 weeks.

When your team’s VDE is built, SOMAR will email you with API access instructions.

 

  1. Our research team has decided to opt into onboarding to Meta Secure Research Environment. What happens next? 

August 18 to October 17: The SOMAR team will have sent you an email asking about your Meta Content Library API access. Please respond to that email so we know you would like to use the Meta SRE.

November and beyond: This is the time period by which you will be able to access the Meta SRE.

 

Features of Meta Content Library API secure computing platform options

*Note that the features available on both platforms are subject to change. 

 

Feature

SOMAR Virtual Data Enclave 

Meta Secure Research Environment (formerly known as Researcher Platform)

Meta Content Library API data coverage

Platform/computation

  • Cloud-based data enclave accessed through a virtual desktop

  • R, RStudio, Python, JupyterLab, Jupyter Notebooks, and Stata available 

  • Browser-based computation on modified version of Jupyter within an Amazon WorkSpaces Secure Browser instance

  • R and Python available 

  • Stata [Launching Q4 ‘25] 

Available machine learning models

  • Machine learning models available by request

  • Models go through an ICPSR security review before upload to your VDE

  • Requested models must align with ICPSR’s LLM Policy

  • Download approved pre-trained machine learning models into your Jupyter environment from the Hugging Face® Hub

Available packages

  • Install Python packages from PyPI with pip 

  • Install R packages with CRAN

  • Install Python packages with pip

  • Install R packages with CRAN and conda

Available GPUs/CPU

  • Offers CPU and GPU instances

  • Free computation through December 31, 2025

  • Starting January 2026, costs per research team will be:

    • 371 USD per month of VDE usage

    • 1000 USD one-time fee for new VDE projects, due at project start (applies only to VDEs created in January 2026 or later)

  • Offers CPU and GPU instances 

  • Free computation 

Export of research outputs

  • Data disclosure review of all materials requested for export

  • Email somar-help@umich.edu to request an output review

  • Can approve code, graphs, figures, charts, tables, abstracts and summary statistics

  • Raw data export is not permitted

  • Automated export of scrubbed notebooks that contain files of code, graphs, figures, charts, and images (but not tables or summary statistics) 

  • Raw data export is not permitted

  • Data disclosure review capabilities [Launching Q4 ‘25] 

Code upload 

  • Code files can be uploaded by request, following a security review by SOMAR

  • Pasting of code into the environment from the outside is permitted 

Data deletion

  • Data that have been removed from Meta Content Library (e.g., deleted posts) are required to be deleted every 180 days

  • Researchers delete respective data from their notebooks and certify their execution of deletion to SOMAR

  • This deletion requirement does not apply to researchers with approved research projects that contribute to the detection, identification, and understanding of systemic risks in the European Union

 

  • Meta will effectuate user data deletion on researchers’ Jupyter notebooks every month. Removal of output cells and local files takes place automatically on the 1st of every month

  • If you opt into transitioning to Meta Secure Research Environment (SRE), the data deletion will apply to your transferred files from the SOMAR VDE. In early November, you will be able to access your transferred files on Meta SRE, and December 1st will be when data deletion will take place

  • This deletion requirement does not apply to researchers with approved research agendas that contribute to the detection, identification, and understanding of systemic risks in the European Union

Collaboration for research teams

  • Research teams receive one enclave instance to facilitate collaboration

  • Individuals receive their own home directories

  • Any file can be accessed and shared among team members

  • Members of a research team can collaborate and share notebooks/files using a shared folder, but the Jupyter lab instances are individual. [Launching Q4 ‘25]