# IXP feature availability

> Models that the features of the Extract node in UiPath Maestro Flow depend on, and how regional model availability affects which features you can use.

## Overview

Some features of the **Extract** node require a specific model, which can differ from the extraction model that you select for the node.

A feature is not enabled in a region where its required model cannot be supported, so feature availability can differ from one region to another even though IXP deploys to all production regions at the same time. If a feature described in this guide is missing from your tenant, the model it depends on might not be available in your region yet.

Use this page together with the following platform references:

* [AI features and model routing](https://docs.uipath.com/automation-cloud/automation-cloud/latest/admin-guide/ai-features-and-model-routing#ixp) - The models IXP uses, and the routing behavior per region when a model endpoint is not regionally available.
* [Data residency](https://docs.uipath.com/automation-cloud/automation-cloud/latest/admin-guide/data-residency-cloud) - Where your organization data is stored and processed.
* [Access and availability](https://docs.uipath.com/ixp/automation-cloud/latest/flow-user-guide/faq-access-and-availability) - The regions where IXP in Flow is available.

## Feature and model requirements

The following table lists the model each feature depends on:

Table 1. Models required by Extract node features

  
    
      Feature
      Required model
    
  
  
    
      Extraction model
      GPT-4o or Gemini 2.5 Flash, selectable per Extract node.Preview models that vary per region.
    
    
      Model-based attribution
      Gemini 2.5 Flash