> ## Documentation Index
> Fetch the complete documentation index at: https://docs.landing.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# European Union (EU)

export const adePythonLibrary = 'ade-python';

export const dpt2 = 'DPT-2';

export const dpt1 = 'DPT-1';

export const dpt = 'Document Pre-Trained Transformer';

export const companyName = 'LandingAI';

export const extract = 'ADE Extract';

export const parse = 'ADE Parse';

export const ade = 'Agentic Document Extraction';

{ade} is available in the European Union (EU) here: [https://va.eu-west-1.landing.ai/](https://va.eu-west-1.landing.ai/).

{ade} in the EU provides:

* **Data residency**: All data is stored and processed within the EU
* **GDPR compliance**: The EU-hosted version of {ade} is compliant with the General Data Protection Regulation (GDPR)
* **Regional performance**: Reduced latency for European users

## GDPR and Compliance

Refer to the resources below to learn more about GDPR and compliance.

<CardGroup cols={3}>
  <Card title="Single Sign-On (SSO)" icon="key" href="/ade/ade-sso">
    Enterprise plans support SSO via SAML 2.0 and OpenID Connect (OIDC), allowing your organization to manage access through your existing identity provider (IdP).
  </Card>

  <Card title="Trust Center" icon="shield-halved" href="https://trust.landing.ai/">
    The Trust Center is your central resource for accessing our security documentation, compliance reports, and real-time system status.
  </Card>

  <Card title="Security and Compliance" icon="lock" href="https://landing.ai/security-at-landingai">
    This page outlines our security posture, compliance with industry standards, and the measures we take to safeguard your data across our products and infrastructure.
  </Card>
</CardGroup>

## EU Pricing

For EU subscription plans and pricing, go to [Pricing & Billing](./ade-pricing#eu-pricing).

## Differences When Using the EU

Using {ade} in the EU works the same as the default US deployment, with only a few key differences outlined in this article:

* [Create an account](#create-an-account-in-the-eu): Use the EU URL
* [Get your API key](#get-your-api-key-for-the-eu): Use the EU URL
* [Call the API directly](#call-the-api-directly-in-the-eu): Use the EU endpoint
* [Use the library](#use-the-library-with-the-eu): Set the EU endpoint as an environment variable

### Create an Account in the EU

Create an account and access the Playground in the EU here: [https://va.eu-west-1.landing.ai/home](https://va.eu-west-1.landing.ai/home).

### Get Your API Key for the EU

To get your API key for the EU, go to [https://va.eu-west-1.landing.ai/settings/api-key](https://va.eu-west-1.landing.ai/settings/api-key).

Use this API key when using the library or calling the API directly in the EU.

API keys are deployment-specific. An API key created in the US will not work for the EU, and vice versa.

### Call the API Directly in the EU

To ensure your API calls are processed in the EU, replace the default base URL with the EU base URL:

**US:** `https://api.va.landing.ai`\
**EU:** `https://api.va.eu-west-1.landing.ai`

For example:

* US: `https://api.va.landing.ai/v1/ade/parse`
* EU: `https://api.va.eu-west-1.landing.ai/v1/ade/parse`

### Use the Library with the EU

To connect the library to the EU deployment, set the `environment` parameter to `eu` when initializing the client.

<CodeGroup>
  ```python Python theme={null}
  from landingai_ade import LandingAIADE

  client = LandingAIADE(
      environment="eu",
  )
  ```

  ```typescript TypeScript theme={null}
  import LandingAIADE from "landingai-ade";

  const client = new LandingAIADE({
    environment: "eu"
  });
  ```
</CodeGroup>
