From 9e1dae074603287162b9bcf43a2ce56d4f4da0c8 Mon Sep 17 00:00:00 2001
From: tonykipkemboi <iamtonykipkemboi@gmail.com>
Date: Wed, 1 Oct 2025 14:11:23 -0400
Subject: [PATCH] docs: parity for all translations

---
 README.md                                     |  28 +--
 docs/docs.json                                |   7 +-
 docs/en/api-reference/introduction.mdx        |  12 +-
 docs/en/changelog.mdx                         |  78 ++++++++
 docs/en/concepts/agents.mdx                   |   2 +-
 docs/en/concepts/cli.mdx                      |  24 +--
 docs/en/concepts/event-listener.mdx           |   2 +-
 docs/en/concepts/tasks.mdx                    |   2 +-
 docs/en/concepts/tools.mdx                    |   2 +-
 docs/en/enterprise/features/rbac.mdx          |   8 +-
 .../features/tools-and-integrations.mdx       |   8 +-
 docs/en/enterprise/features/traces.mdx        |   6 +-
 .../enterprise/features/webhook-streaming.mdx |   2 +-
 .../enterprise/guides/automation-triggers.mdx |   6 +-
 .../enterprise/guides/azure-openai-setup.mdx  |   6 +-
 docs/en/enterprise/guides/build-crew.mdx      |   2 +-
 docs/en/enterprise/guides/deploy-crew.mdx     |  16 +-
 .../enterprise/guides/enable-crew-studio.mdx  |  12 +-
 docs/en/enterprise/guides/gmail-trigger.mdx   |   4 +-
 .../guides/google-calendar-trigger.mdx        |   2 +-
 .../guides/google-drive-trigger.mdx           |   2 +-
 docs/en/enterprise/guides/hubspot-trigger.mdx |  14 +-
 docs/en/enterprise/guides/kickoff-crew.mdx    |   8 +-
 .../guides/microsoft-teams-trigger.mdx        |   2 +-
 .../en/enterprise/guides/onedrive-trigger.mdx |   2 +-
 docs/en/enterprise/guides/outlook-trigger.mdx |   2 +-
 .../guides/react-component-export.mdx         |   4 +-
 .../enterprise/guides/salesforce-trigger.mdx  |   6 +-
 docs/en/enterprise/guides/team-management.mdx |  10 +-
 docs/en/enterprise/guides/tool-repository.mdx |  12 +-
 docs/en/enterprise/guides/update-crew.mdx     |   8 +-
 .../enterprise/guides/webhook-automation.mdx  |   8 +-
 docs/en/enterprise/guides/zapier-trigger.mdx  |  20 +-
 docs/en/enterprise/integrations/asana.mdx     |   4 +-
 docs/en/enterprise/integrations/box.mdx       |   4 +-
 docs/en/enterprise/integrations/clickup.mdx   |   4 +-
 docs/en/enterprise/integrations/github.mdx    |   4 +-
 docs/en/enterprise/integrations/gmail.mdx     |   4 +-
 .../integrations/google_calendar.mdx          |   4 +-
 .../enterprise/integrations/google_sheets.mdx |   4 +-
 docs/en/enterprise/integrations/hubspot.mdx   |   4 +-
 docs/en/enterprise/integrations/jira.mdx      |   4 +-
 docs/en/enterprise/integrations/linear.mdx    |   4 +-
 docs/en/enterprise/integrations/notion.mdx    |   4 +-
 .../en/enterprise/integrations/salesforce.mdx |   2 +-
 docs/en/enterprise/integrations/shopify.mdx   |   2 +-
 docs/en/enterprise/integrations/slack.mdx     |   2 +-
 docs/en/enterprise/integrations/stripe.mdx    |   2 +-
 docs/en/enterprise/integrations/zendesk.mdx   |   2 +-
 docs/en/enterprise/introduction.mdx           |   8 +-
 .../resources/frequently-asked-questions.mdx  |   2 +-
 docs/en/index.mdx                             | 107 ++++++++++
 docs/en/installation.mdx                      |   2 +-
 docs/en/learn/human-input-on-execution.mdx    |   2 +-
 docs/en/learn/llm-selection-guide.mdx         |   4 +-
 docs/en/quickstart.mdx                        |  14 +-
 docs/enterprise-api.base.yaml                 |  12 +-
 docs/enterprise-api.en.yaml                   |  12 +-
 docs/enterprise-api.ko.yaml                   |   2 +-
 docs/enterprise-api.pt-BR.yaml                |  12 +-
 docs/ko/api-reference/introduction.mdx        |   8 +-
 docs/ko/changelog.mdx                         |  78 ++++++++
 docs/ko/concepts/agents.mdx                   |   2 +-
 docs/ko/concepts/cli.mdx                      |  22 +-
 docs/ko/concepts/event-listener.mdx           |   2 +-
 docs/ko/enterprise/features/integrations.mdx  | 180 -----------------
 docs/ko/enterprise/features/rbac.mdx          |   6 +-
 .../enterprise/features/tool-repository.mdx   | 107 ----------
 .../features/tools-and-integrations.mdx       |   4 +-
 docs/ko/enterprise/features/traces.mdx        |   4 +-
 .../enterprise/features/webhook-streaming.mdx |   2 +-
 .../enterprise/guides/automation-triggers.mdx |   6 +-
 .../enterprise/guides/azure-openai-setup.mdx  |   6 +-
 docs/ko/enterprise/guides/build-crew.mdx      |   2 +-
 docs/ko/enterprise/guides/deploy-crew.mdx     |  14 +-
 .../enterprise/guides/enable-crew-studio.mdx  |  12 +-
 docs/ko/enterprise/guides/gmail-trigger.mdx   |  85 ++++++++
 .../guides/google-calendar-trigger.mdx        |  65 ++++++
 .../guides/google-drive-trigger.mdx           |  61 ++++++
 docs/ko/enterprise/guides/hubspot-trigger.mdx |  14 +-
 docs/ko/enterprise/guides/kickoff-crew.mdx    |   8 +-
 .../guides/microsoft-teams-trigger.mdx        |  52 +++++
 .../ko/enterprise/guides/onedrive-trigger.mdx |  53 +++++
 docs/ko/enterprise/guides/outlook-trigger.mdx |  52 +++++
 .../guides/react-component-export.mdx         |   4 +-
 .../enterprise/guides/salesforce-trigger.mdx  |   6 +-
 docs/ko/enterprise/guides/team-management.mdx |  10 +-
 docs/ko/enterprise/guides/tool-repository.mdx |   8 +-
 docs/ko/enterprise/guides/update-crew.mdx     |   8 +-
 .../enterprise/guides/webhook-automation.mdx  |   8 +-
 docs/ko/enterprise/guides/zapier-trigger.mdx  |  20 +-
 docs/ko/enterprise/integrations/asana.mdx     |   4 +-
 docs/ko/enterprise/integrations/box.mdx       |   4 +-
 docs/ko/enterprise/integrations/clickup.mdx   |   4 +-
 docs/ko/enterprise/integrations/github.mdx    |   4 +-
 docs/ko/enterprise/integrations/gmail.mdx     |   4 +-
 .../integrations/google_calendar.mdx          |   4 +-
 .../enterprise/integrations/google_sheets.mdx |   4 +-
 docs/ko/enterprise/integrations/hubspot.mdx   |   4 +-
 docs/ko/enterprise/integrations/jira.mdx      |   4 +-
 docs/ko/enterprise/integrations/linear.mdx    |   4 +-
 docs/ko/enterprise/integrations/notion.mdx    |   4 +-
 .../ko/enterprise/integrations/salesforce.mdx |   2 +-
 docs/ko/enterprise/integrations/shopify.mdx   |   2 +-
 docs/ko/enterprise/integrations/slack.mdx     |   2 +-
 docs/ko/enterprise/integrations/stripe.mdx    |   2 +-
 docs/ko/enterprise/integrations/zendesk.mdx   |   2 +-
 docs/ko/enterprise/introduction.mdx           |   6 +-
 .../resources/frequently-asked-questions.mdx  |   2 +-
 docs/ko/installation.mdx                      |   2 +-
 docs/ko/learn/human-input-on-execution.mdx    |   2 +-
 docs/ko/learn/llm-selection-guide.mdx         |   4 +-
 docs/ko/observability/truefoundry.mdx         | 147 ++++++++++++++
 docs/ko/quickstart.mdx                        |  14 +-
 .../cloud-storage/bedrockinvokeagenttool.mdx  | 188 ------------------
 docs/ko/tools/tool-integrations/overview.mdx  |  31 +++
 docs/pt-BR/api-reference/introduction.mdx     |  12 +-
 docs/pt-BR/changelog.mdx                      |  78 ++++++++
 docs/pt-BR/concepts/agents.mdx                |   2 +-
 docs/pt-BR/concepts/cli.mdx                   |  22 +-
 docs/pt-BR/concepts/event-listener.mdx        |   2 +-
 docs/pt-BR/concepts/tasks.mdx                 |   2 +-
 docs/pt-BR/concepts/tools.mdx                 |   2 +-
 .../enterprise/features/integrations.mdx      | 180 -----------------
 docs/pt-BR/enterprise/features/rbac.mdx       |   8 +-
 .../features/tools-and-integrations.mdx       |   4 +-
 docs/pt-BR/enterprise/features/traces.mdx     |   6 +-
 .../enterprise/features/webhook-streaming.mdx |   2 +-
 .../enterprise/guides/automation-triggers.mdx |   6 +-
 .../enterprise/guides/azure-openai-setup.mdx  |   4 +-
 docs/pt-BR/enterprise/guides/build-crew.mdx   |   2 +-
 docs/pt-BR/enterprise/guides/deploy-crew.mdx  |  16 +-
 .../enterprise/guides/enable-crew-studio.mdx  |  12 +-
 .../pt-BR/enterprise/guides/gmail-trigger.mdx |  85 ++++++++
 .../guides/google-calendar-trigger.mdx        |  65 ++++++
 .../guides/google-drive-trigger.mdx           |  61 ++++++
 .../enterprise/guides/hubspot-trigger.mdx     |  14 +-
 docs/pt-BR/enterprise/guides/kickoff-crew.mdx |   8 +-
 .../guides/microsoft-teams-trigger.mdx        |  52 +++++
 .../enterprise/guides/onedrive-trigger.mdx    |  53 +++++
 .../enterprise/guides/outlook-trigger.mdx     |  52 +++++
 .../guides/react-component-export.mdx         |   4 +-
 .../enterprise/guides/salesforce-trigger.mdx  |   6 +-
 .../enterprise/guides/team-management.mdx     |  10 +-
 .../enterprise/guides/tool-repository.mdx     |   8 +-
 docs/pt-BR/enterprise/guides/update-crew.mdx  |   8 +-
 .../enterprise/guides/webhook-automation.mdx  |   8 +-
 .../enterprise/guides/zapier-trigger.mdx      |  20 +-
 docs/pt-BR/enterprise/integrations/asana.mdx  |   4 +-
 docs/pt-BR/enterprise/integrations/box.mdx    |   4 +-
 .../pt-BR/enterprise/integrations/clickup.mdx |   4 +-
 docs/pt-BR/enterprise/integrations/github.mdx |   4 +-
 docs/pt-BR/enterprise/integrations/gmail.mdx  |   4 +-
 .../integrations/google_calendar.mdx          |   4 +-
 .../enterprise/integrations/google_sheets.mdx |   4 +-
 .../pt-BR/enterprise/integrations/hubspot.mdx |   4 +-
 docs/pt-BR/enterprise/integrations/jira.mdx   |   4 +-
 docs/pt-BR/enterprise/integrations/linear.mdx |   4 +-
 docs/pt-BR/enterprise/integrations/notion.mdx |   4 +-
 .../enterprise/integrations/salesforce.mdx    |   2 +-
 .../pt-BR/enterprise/integrations/shopify.mdx |   2 +-
 docs/pt-BR/enterprise/integrations/slack.mdx  |   2 +-
 docs/pt-BR/enterprise/integrations/stripe.mdx |   2 +-
 .../pt-BR/enterprise/integrations/zendesk.mdx |   2 +-
 docs/pt-BR/enterprise/introduction.mdx        |   8 +-
 .../resources/frequently-asked-questions.mdx  |   2 +-
 docs/pt-BR/installation.mdx                   |   2 +-
 docs/pt-BR/learn/human-input-on-execution.mdx |   2 +-
 docs/pt-BR/learn/llm-selection-guide.mdx      |   4 +-
 docs/pt-BR/observability/neatlogs.mdx         | 134 +++++++++++++
 docs/pt-BR/quickstart.mdx                     |  14 +-
 .../tools/automation/zapieractionstool.mdx    |  59 ++++++
 .../cloud-storage/bedrockinvokeagenttool.mdx  | 188 ------------------
 .../database-data/mongodbvectorsearchtool.mdx | 169 ++++++++++++++++
 .../database-data/singlestoresearchtool.mdx   |  62 ++++++
 docs/pt-BR/tools/file-document/ocrtool.mdx    |  90 +++++++++
 .../file-document/pdf-text-writing-tool.mdx   |  77 +++++++
 .../tools/search-research/arxivpapertool.mdx  | 113 +++++++++++
 .../search-research/databricks-query-tool.mdx |  81 ++++++++
 .../serpapi-googlesearchtool.mdx              |  66 ++++++
 .../serpapi-googleshoppingtool.mdx            |  62 ++++++
 .../search-research/tavilyextractortool.mdx   | 140 +++++++++++++
 .../search-research/tavilysearchtool.mdx      | 125 ++++++++++++
 .../tools/tool-integrations/overview.mdx      |  31 +++
 .../tools/web-scraping/brightdata-tools.mdx   | 112 +++++++++++
 .../web-scraping/serperscrapewebsitetool.mdx  | 101 ++++++++++
 .../generate_crewai_automation_tool/README.md |   2 +-
 .../generate_crewai_automation_tool.py        |  10 +-
 lib/crewai-tools/tool.specs.json              |  10 +-
 lib/crewai/README.md                          |  28 +--
 .../crewai/agents/agent_builder/base_agent.py |   4 +-
 .../src/crewai/cli/authentication/main.py     |   4 +-
 lib/crewai/src/crewai/cli/cli.py              |   4 +-
 lib/crewai/src/crewai/cli/config.py           |   2 +-
 lib/crewai/src/crewai/cli/enterprise/main.py  |   2 +-
 .../cli/authentication/test_auth_main.py      |   4 +-
 196 files changed, 3167 insertions(+), 1330 deletions(-)
 create mode 100644 docs/en/index.mdx
 delete mode 100644 docs/ko/enterprise/features/integrations.mdx
 delete mode 100644 docs/ko/enterprise/features/tool-repository.mdx
 create mode 100644 docs/ko/enterprise/guides/gmail-trigger.mdx
 create mode 100644 docs/ko/enterprise/guides/google-calendar-trigger.mdx
 create mode 100644 docs/ko/enterprise/guides/google-drive-trigger.mdx
 create mode 100644 docs/ko/enterprise/guides/microsoft-teams-trigger.mdx
 create mode 100644 docs/ko/enterprise/guides/onedrive-trigger.mdx
 create mode 100644 docs/ko/enterprise/guides/outlook-trigger.mdx
 create mode 100644 docs/ko/observability/truefoundry.mdx
 delete mode 100644 docs/ko/tools/cloud-storage/bedrockinvokeagenttool.mdx
 create mode 100644 docs/ko/tools/tool-integrations/overview.mdx
 delete mode 100644 docs/pt-BR/enterprise/features/integrations.mdx
 create mode 100644 docs/pt-BR/enterprise/guides/gmail-trigger.mdx
 create mode 100644 docs/pt-BR/enterprise/guides/google-calendar-trigger.mdx
 create mode 100644 docs/pt-BR/enterprise/guides/google-drive-trigger.mdx
 create mode 100644 docs/pt-BR/enterprise/guides/microsoft-teams-trigger.mdx
 create mode 100644 docs/pt-BR/enterprise/guides/onedrive-trigger.mdx
 create mode 100644 docs/pt-BR/enterprise/guides/outlook-trigger.mdx
 create mode 100644 docs/pt-BR/observability/neatlogs.mdx
 create mode 100644 docs/pt-BR/tools/automation/zapieractionstool.mdx
 delete mode 100644 docs/pt-BR/tools/cloud-storage/bedrockinvokeagenttool.mdx
 create mode 100644 docs/pt-BR/tools/database-data/mongodbvectorsearchtool.mdx
 create mode 100644 docs/pt-BR/tools/database-data/singlestoresearchtool.mdx
 create mode 100644 docs/pt-BR/tools/file-document/ocrtool.mdx
 create mode 100644 docs/pt-BR/tools/file-document/pdf-text-writing-tool.mdx
 create mode 100644 docs/pt-BR/tools/search-research/arxivpapertool.mdx
 create mode 100644 docs/pt-BR/tools/search-research/databricks-query-tool.mdx
 create mode 100644 docs/pt-BR/tools/search-research/serpapi-googlesearchtool.mdx
 create mode 100644 docs/pt-BR/tools/search-research/serpapi-googleshoppingtool.mdx
 create mode 100644 docs/pt-BR/tools/search-research/tavilyextractortool.mdx
 create mode 100644 docs/pt-BR/tools/search-research/tavilysearchtool.mdx
 create mode 100644 docs/pt-BR/tools/tool-integrations/overview.mdx
 create mode 100644 docs/pt-BR/tools/web-scraping/brightdata-tools.mdx
 create mode 100644 docs/pt-BR/tools/web-scraping/serperscrapewebsitetool.mdx

diff --git a/README.md b/README.md
index 3d3eb3324..a448e6355 100644
--- a/README.md
+++ b/README.md
@@ -62,9 +62,9 @@
 With over 100,000 developers certified through our community courses at [learn.crewai.com](https://learn.crewai.com), CrewAI is rapidly becoming the
 standard for enterprise-ready AI automation.
 
-# CrewAI Enterprise Suite
+# CrewAI AMP Suite
 
-CrewAI Enterprise Suite is a comprehensive bundle tailored for organizations that require secure, scalable, and easy-to-manage agent-driven automation.
+CrewAI AMP Suite is a comprehensive bundle tailored for organizations that require secure, scalable, and easy-to-manage agent-driven automation.
 
 You can try one part of the suite the [Crew Control Plane for free](https://app.crewai.com)
 
@@ -76,9 +76,9 @@ You can try one part of the suite the [Crew Control Plane for free](https://app.
 - **Advanced Security**: Built-in robust security and compliance measures ensuring safe deployment and management.
 - **Actionable Insights**: Real-time analytics and reporting to optimize performance and decision-making.
 - **24/7 Support**: Dedicated enterprise support to ensure uninterrupted operation and quick resolution of issues.
-- **On-premise and Cloud Deployment Options**: Deploy CrewAI Enterprise on-premise or in the cloud, depending on your security and compliance requirements.
+- **On-premise and Cloud Deployment Options**: Deploy CrewAI AMP on-premise or in the cloud, depending on your security and compliance requirements.
 
-CrewAI Enterprise is designed for enterprises seeking a powerful, reliable solution to transform complex business processes into efficient,
+CrewAI AMP is designed for enterprises seeking a powerful, reliable solution to transform complex business processes into efficient,
 intelligent automations.
 
 ## Table of contents
@@ -674,9 +674,9 @@ CrewAI is released under the [MIT License](https://github.com/crewAIInc/crewAI/b
 
 ### Enterprise Features
 
-- [What additional features does CrewAI Enterprise offer?](#q-what-additional-features-does-crewai-enterprise-offer)
-- [Is CrewAI Enterprise available for cloud and on-premise deployments?](#q-is-crewai-enterprise-available-for-cloud-and-on-premise-deployments)
-- [Can I try CrewAI Enterprise for free?](#q-can-i-try-crewai-enterprise-for-free)
+- [What additional features does CrewAI AMP offer?](#q-what-additional-features-does-crewai-amp-offer)
+- [Is CrewAI AMP available for cloud and on-premise deployments?](#q-is-crewai-amp-available-for-cloud-and-on-premise-deployments)
+- [Can I try CrewAI AMP for free?](#q-can-i-try-crewai-amp-for-free)
 
 ### Q: What exactly is CrewAI?
 
@@ -732,17 +732,17 @@ A: Check out practical examples in the [CrewAI-examples repository](https://gith
 
 A: Contributions are warmly welcomed! Fork the repository, create your branch, implement your changes, and submit a pull request. See the Contribution section of the README for detailed guidelines.
 
-### Q: What additional features does CrewAI Enterprise offer?
+### Q: What additional features does CrewAI AMP offer?
 
-A: CrewAI Enterprise provides advanced features such as a unified control plane, real-time observability, secure integrations, advanced security, actionable insights, and dedicated 24/7 enterprise support.
+A: CrewAI AMP provides advanced features such as a unified control plane, real-time observability, secure integrations, advanced security, actionable insights, and dedicated 24/7 enterprise support.
 
-### Q: Is CrewAI Enterprise available for cloud and on-premise deployments?
+### Q: Is CrewAI AMP available for cloud and on-premise deployments?
 
-A: Yes, CrewAI Enterprise supports both cloud-based and on-premise deployment options, allowing enterprises to meet their specific security and compliance requirements.
+A: Yes, CrewAI AMP supports both cloud-based and on-premise deployment options, allowing enterprises to meet their specific security and compliance requirements.
 
-### Q: Can I try CrewAI Enterprise for free?
+### Q: Can I try CrewAI AMP for free?
 
-A: Yes, you can explore part of the CrewAI Enterprise Suite by accessing the [Crew Control Plane](https://app.crewai.com) for free.
+A: Yes, you can explore part of the CrewAI AMP Suite by accessing the [Crew Control Plane](https://app.crewai.com) for free.
 
 ### Q: Does CrewAI support fine-tuning or training custom models?
 
@@ -762,7 +762,7 @@ A: CrewAI is highly scalable, supporting simple automations and large-scale ente
 
 ### Q: Does CrewAI offer debugging and monitoring tools?
 
-A: Yes, CrewAI Enterprise includes advanced debugging, tracing, and real-time observability features, simplifying the management and troubleshooting of your automations.
+A: Yes, CrewAI AMP includes advanced debugging, tracing, and real-time observability features, simplifying the management and troubleshooting of your automations.
 
 ### Q: What programming languages does CrewAI support?
 
diff --git a/docs/docs.json b/docs/docs.json
index ad73b94b5..abb15751e 100644
--- a/docs/docs.json
+++ b/docs/docs.json
@@ -287,6 +287,7 @@
                   "en/learn/force-tool-output-as-result",
                   "en/learn/hierarchical-process",
                   "en/learn/human-input-on-execution",
+                  "en/learn/human-in-the-loop",
                   "en/learn/kickoff-async",
                   "en/learn/kickoff-for-each",
                   "en/learn/llm-connections",
@@ -303,7 +304,7 @@
             ]
           },
           {
-            "tab": "Enterprise",
+            "tab": "AMP",
             "icon": "briefcase",
             "groups": [
               {
@@ -695,6 +696,7 @@
                   "pt-BR/learn/force-tool-output-as-result",
                   "pt-BR/learn/hierarchical-process",
                   "pt-BR/learn/human-input-on-execution",
+                  "pt-BR/learn/human-in-the-loop",
                   "pt-BR/learn/kickoff-async",
                   "pt-BR/learn/kickoff-for-each",
                   "pt-BR/learn/llm-connections",
@@ -711,7 +713,7 @@
             ]
           },
           {
-            "tab": "Enterprise",
+            "tab": "AMP",
             "icon": "briefcase",
             "groups": [
               {
@@ -1108,6 +1110,7 @@
                   "ko/learn/force-tool-output-as-result",
                   "ko/learn/hierarchical-process",
                   "ko/learn/human-input-on-execution",
+                  "ko/learn/human-in-the-loop",
                   "ko/learn/kickoff-async",
                   "ko/learn/kickoff-for-each",
                   "ko/learn/llm-connections",
diff --git a/docs/en/api-reference/introduction.mdx b/docs/en/api-reference/introduction.mdx
index 3ee25b14a..5085f2333 100644
--- a/docs/en/api-reference/introduction.mdx
+++ b/docs/en/api-reference/introduction.mdx
@@ -1,19 +1,19 @@
 ---
 title: "Introduction"
-description: "Complete reference for the CrewAI Enterprise REST API"
+description: "Complete reference for the CrewAI AMP REST API"
 icon: "code"
 mode: "wide"
 ---
 
-# CrewAI Enterprise API
+# CrewAI AMP API
 
-Welcome to the CrewAI Enterprise API reference. This API allows you to programmatically interact with your deployed crews, enabling integration with your applications, workflows, and services.
+Welcome to the CrewAI AMP API reference. This API allows you to programmatically interact with your deployed crews, enabling integration with your applications, workflows, and services.
 
 ## Quick Start
 
 <Steps>
   <Step title="Get Your API Credentials">
-    Navigate to your crew's detail page in the CrewAI Enterprise dashboard and copy your Bearer Token from the Status tab.
+    Navigate to your crew's detail page in the CrewAI AMP dashboard and copy your Bearer Token from the Status tab.
   </Step>
   
   <Step title="Discover Required Inputs">
@@ -46,7 +46,7 @@ curl -H "Authorization: Bearer YOUR_CREW_TOKEN" \
 | **User Bearer Token** | User-scoped access | Limited permissions, suitable for user-specific operations |
 
 <Tip>
-You can find both token types in the Status tab of your crew's detail page in the CrewAI Enterprise dashboard.
+You can find both token types in the Status tab of your crew's detail page in the CrewAI AMP dashboard.
 </Tip>
 
 ## Base URL
@@ -82,7 +82,7 @@ The API uses standard HTTP status codes:
 ## Interactive Testing
 
 <Info>
-**Why no "Send" button?** Since each CrewAI Enterprise user has their own unique crew URL, we use **reference mode** instead of an interactive playground to avoid confusion. This shows you exactly what the requests should look like without non-functional send buttons.
+**Why no "Send" button?** Since each CrewAI AMP user has their own unique crew URL, we use **reference mode** instead of an interactive playground to avoid confusion. This shows you exactly what the requests should look like without non-functional send buttons.
 </Info>
 
 Each endpoint page shows you:
diff --git a/docs/en/changelog.mdx b/docs/en/changelog.mdx
index 64674c71d..afaa97f88 100644
--- a/docs/en/changelog.mdx
+++ b/docs/en/changelog.mdx
@@ -4,6 +4,84 @@ description: "Product updates, improvements, and bug fixes for CrewAI"
 icon: "clock"
 mode: "wide"
 ---
+<Update label="Sep 30, 2025">
+  ## v1.0.0a1
+
+  [View release on GitHub](https://github.com/crewAIInc/crewAI/releases/tag/1.0.0a1)
+
+  ## What's Changed
+
+  ### Core Improvements & Fixes
+  - Fixed permission handling for `actions` in agent configuration
+  - Updated CI workflows and release publishing to support the new monorepo structure
+  - Bumped Python support to 3.13 and refreshed workspace metadata
+
+  ### New Features & Enhancements
+  - Added `apps` and `actions` attributes to `Agent` for richer runtime control
+  - Merged the `crewai-tools` repository into the main workspace (monorepo)
+  - Bumped all packages to 1.0.0a1 to mark the alpha milestone
+
+  ### Cleanup & Infrastructure
+  - Delivered a new CI pipeline with version pinning and publishing strategy
+  - Unified internal code to manage multiple packages coherently
+
+</Update>
+
+<Update label="Sep 26, 2025">
+  ## v0.201.1
+
+  [View release on GitHub](https://github.com/crewAIInc/crewAI/releases/tag/0.201.1)
+
+  ## What's Changed
+
+  ### Core Improvements & Fixes
+  - Renamed Watson embedding provider to `watsonx` and refreshed environment variable prefixes
+  - Added ChromaDB compatibility for `watsonx` and `voyageai` embedding providers
+
+  ### Cleanup & Deprecations
+  - Standardized environment variable prefixes for all embedding providers
+  - Bumped CrewAI to 0.201.1 and updated internal dependencies
+
+</Update>
+
+<Update label="Sep 24, 2025">
+  ## v0.201.0
+
+  [View release on GitHub](https://github.com/crewAIInc/crewAI/releases/tag/0.201.0)
+
+  ## What's Changed
+
+  ### Core Improvements & Fixes
+  - Made the `ready` parameter optional in `_create_reasoning_plan`
+  - Fixed nested config handling for embedder configuration
+  - Added `batch_size` support to avoid token limit errors
+  - Corrected Quickstart documentation directory naming
+  - Resolved test duration cache issues and event exports
+  - Added fallback logic to crew settings
+
+  ### New Features & Enhancements
+  - Introduced thread-safe platform context management
+  - Added `crewai uv` wrapper command to run `uv` from the CLI
+  - Enabled marking traces as failed for observability workflows
+  - Added custom embedding types and provider migration support
+  - Upgraded ChromaDB to v1.1.0 with compatibility fixes and type improvements
+  - Added Pydantic-compatible import validation and reorganized dependency groups
+
+  ### Documentation & Guides
+  - Updated changelog coverage for recent releases (0.193.x series)
+  - Documented metadata support for LLM Guardrail events
+  - Added guidance for fallback behavior and configuration visibility
+
+  ### Cleanup & Deprecations
+  - Resolved Ruff and MyPy issues across modules
+  - Improved type annotations and consolidated utilities
+  - Deprecated legacy utilities in favor of Pydantic-compatible imports
+
+  ### Contributors
+  - @qizwiz (first contribution)
+
+</Update>
+
 
 <Update label="Sep 20, 2025">
   ## v0.193.2
diff --git a/docs/en/concepts/agents.mdx b/docs/en/concepts/agents.mdx
index c5d99983e..2f26a5699 100644
--- a/docs/en/concepts/agents.mdx
+++ b/docs/en/concepts/agents.mdx
@@ -20,7 +20,7 @@ Think of an agent as a specialized team member with specific skills, expertise,
 </Tip>
 
 <Note type="info" title="Enterprise Enhancement: Visual Agent Builder">
-CrewAI Enterprise includes a Visual Agent Builder that simplifies agent creation and configuration without writing code. Design your agents visually and test them in real-time.
+CrewAI AMP includes a Visual Agent Builder that simplifies agent creation and configuration without writing code. Design your agents visually and test them in real-time.
 
 ![Visual Agent Builder Screenshot](/images/enterprise/crew-studio-interface.png)
 
diff --git a/docs/en/concepts/cli.mdx b/docs/en/concepts/cli.mdx
index 272f0946c..0e50054bc 100644
--- a/docs/en/concepts/cli.mdx
+++ b/docs/en/concepts/cli.mdx
@@ -5,7 +5,7 @@ icon: terminal
 mode: "wide"
 ---
 
-<Warning>Since release 0.140.0, CrewAI Enterprise started a process of migrating their login provider. As such, the authentication flow via CLI was updated. Users that use Google to login, or that created their account after July 3rd, 2025 will be unable to log in with older versions of the `crewai` library.</Warning>
+<Warning>Since release 0.140.0, CrewAI AMP started a process of migrating their login provider. As such, the authentication flow via CLI was updated. Users that use Google to login, or that created their account after July 3rd, 2025 will be unable to log in with older versions of the `crewai` library.</Warning>
 
 ## Overview
 
@@ -186,9 +186,9 @@ def crew(self) -> Crew:
 
 ### 10. Deploy
 
-Deploy the crew or flow to [CrewAI Enterprise](https://app.crewai.com).
+Deploy the crew or flow to [CrewAI AMP](https://app.crewai.com).
 
-- **Authentication**: You need to be authenticated to deploy to CrewAI Enterprise.
+- **Authentication**: You need to be authenticated to deploy to CrewAI AMP.
     You can login or create an account with:
     ```shell Terminal
     crewai login
@@ -203,7 +203,7 @@ Deploy the crew or flow to [CrewAI Enterprise](https://app.crewai.com).
 
 ### 11. Organization Management
 
-Manage your CrewAI Enterprise organizations.
+Manage your CrewAI AMP organizations.
 
 ```shell Terminal
 crewai org [COMMAND] [OPTIONS]
@@ -227,17 +227,17 @@ crewai org switch <organization_id>
 ```
 
 <Note>
-You must be authenticated to CrewAI Enterprise to use these organization management commands.
+You must be authenticated to CrewAI AMP to use these organization management commands.
 </Note>
 
 - **Create a deployment** (continued):
     - Links the deployment to the corresponding remote GitHub repository (it usually detects this automatically).
 
-- **Deploy the Crew**: Once you are authenticated, you can deploy your crew or flow to CrewAI Enterprise.
+- **Deploy the Crew**: Once you are authenticated, you can deploy your crew or flow to CrewAI AMP.
     ```shell Terminal
     crewai deploy push
     ```
-    - Initiates the deployment process on the CrewAI Enterprise platform.
+    - Initiates the deployment process on the CrewAI AMP platform.
     - Upon successful initiation, it will output the Deployment created successfully! message along with the Deployment Name and a unique Deployment ID (UUID).
 
 - **Deployment Status**: You can check the status of your deployment with:
@@ -262,7 +262,7 @@ You must be authenticated to CrewAI Enterprise to use these organization managem
     ```shell Terminal
     crewai deploy remove
     ```
-    This deletes the deployment from the CrewAI Enterprise platform.
+    This deletes the deployment from the CrewAI AMP platform.
 
 - **Help Command**: You can get help with the CLI with:
     ```shell Terminal
@@ -270,7 +270,7 @@ You must be authenticated to CrewAI Enterprise to use these organization managem
     ```
     This shows the help message for the CrewAI Deploy CLI.
 
-Watch this video tutorial for a step-by-step demonstration of deploying your crew to [CrewAI Enterprise](http://app.crewai.com) using the CLI.
+Watch this video tutorial for a step-by-step demonstration of deploying your crew to [CrewAI AMP](http://app.crewai.com) using the CLI.
 
 <iframe
   className="w-full aspect-video rounded-xl"
@@ -283,7 +283,7 @@ Watch this video tutorial for a step-by-step demonstration of deploying your cre
 
 ### 11. Login
 
-Authenticate with CrewAI Enterprise using a secure device code flow (no email entry required).
+Authenticate with CrewAI AMP using a secure device code flow (no email entry required).
 
 ```shell Terminal
 crewai login
@@ -354,7 +354,7 @@ crewai config reset
 
 #### Available Configuration Parameters
 
-- `enterprise_base_url`: Base URL of the CrewAI Enterprise instance
+- `enterprise_base_url`: Base URL of the CrewAI AMP instance
 - `oauth2_provider`: OAuth2 provider used for authentication (e.g., workos, okta, auth0)
 - `oauth2_audience`: OAuth2 audience value, typically used to identify the target API or resource
 - `oauth2_client_id`: OAuth2 client ID issued by the provider, used during authentication requests
@@ -370,7 +370,7 @@ crewai config list
 Example output:
 | Setting             | Value                    | Description                                                 |
 | :------------------ | :----------------------- | :---------------------------------------------------------- |
-| enterprise_base_url | https://app.crewai.com   | Base URL of the CrewAI Enterprise instance                  |
+| enterprise_base_url | https://app.crewai.com   | Base URL of the CrewAI AMP instance                  |
 | org_name            | Not set                  | Name of the currently active organization                   |
 | org_uuid            | Not set                  | UUID of the currently active organization                   |
 | oauth2_provider     | workos                   | OAuth2 provider (e.g., workos, okta, auth0)                 |
diff --git a/docs/en/concepts/event-listener.mdx b/docs/en/concepts/event-listener.mdx
index 33550139d..69c65c230 100644
--- a/docs/en/concepts/event-listener.mdx
+++ b/docs/en/concepts/event-listener.mdx
@@ -20,7 +20,7 @@ CrewAI uses an event bus architecture to emit events throughout the execution li
 When specific actions occur in CrewAI (like a Crew starting execution, an Agent completing a task, or a tool being used), the system emits corresponding events. You can register handlers for these events to execute custom code when they occur.
 
 <Note type="info" title="Enterprise Enhancement: Prompt Tracing">
-CrewAI Enterprise provides a built-in Prompt Tracing feature that leverages the event system to track, store, and visualize all prompts, completions, and associated metadata. This provides powerful debugging capabilities and transparency into your agent operations.
+CrewAI AMP provides a built-in Prompt Tracing feature that leverages the event system to track, store, and visualize all prompts, completions, and associated metadata. This provides powerful debugging capabilities and transparency into your agent operations.
 
 ![Prompt Tracing Dashboard](/images/enterprise/traces-overview.png)
 
diff --git a/docs/en/concepts/tasks.mdx b/docs/en/concepts/tasks.mdx
index 395f9c008..3a8334bb1 100644
--- a/docs/en/concepts/tasks.mdx
+++ b/docs/en/concepts/tasks.mdx
@@ -14,7 +14,7 @@ Tasks provide all necessary details for execution, such as a description, the ag
 Tasks within CrewAI can be collaborative, requiring multiple agents to work together. This is managed through the task properties and orchestrated by the Crew's process, enhancing teamwork and efficiency.
 
 <Note type="info" title="Enterprise Enhancement: Visual Task Builder">
-CrewAI Enterprise includes a Visual Task Builder in Crew Studio that simplifies complex task creation and chaining. Design your task flows visually and test them in real-time without writing code.
+CrewAI AMP includes a Visual Task Builder in Crew Studio that simplifies complex task creation and chaining. Design your task flows visually and test them in real-time without writing code.
 
 ![Task Builder Screenshot](/images/enterprise/crew-studio-interface.png)
 
diff --git a/docs/en/concepts/tools.mdx b/docs/en/concepts/tools.mdx
index e23d2478e..41dbe2706 100644
--- a/docs/en/concepts/tools.mdx
+++ b/docs/en/concepts/tools.mdx
@@ -17,7 +17,7 @@ This includes tools from the [CrewAI Toolkit](https://github.com/joaomdmoura/cre
 enabling everything from simple searches to complex interactions and effective teamwork among agents.
 
 <Note type="info" title="Enterprise Enhancement: Tools Repository">
-CrewAI Enterprise provides a comprehensive Tools Repository with pre-built integrations for common business systems and APIs. Deploy agents with enterprise tools in minutes instead of days.
+CrewAI AMP provides a comprehensive Tools Repository with pre-built integrations for common business systems and APIs. Deploy agents with enterprise tools in minutes instead of days.
 
 The Enterprise Tools Repository includes:
 - Pre-built connectors for popular enterprise systems
diff --git a/docs/en/enterprise/features/rbac.mdx b/docs/en/enterprise/features/rbac.mdx
index c6271c4a2..0305ed22b 100644
--- a/docs/en/enterprise/features/rbac.mdx
+++ b/docs/en/enterprise/features/rbac.mdx
@@ -7,10 +7,10 @@ mode: "wide"
 
 ## Overview
 
-RBAC in CrewAI Enterprise enables secure, scalable access management through a combination of organization‑level roles and automation‑level visibility controls.
+RBAC in CrewAI AMP enables secure, scalable access management through a combination of organization‑level roles and automation‑level visibility controls.
 
 <Frame>
-  <img src="/images/enterprise/users_and_roles.png" alt="RBAC overview in CrewAI Enterprise" />
+  <img src="/images/enterprise/users_and_roles.png" alt="RBAC overview in CrewAI AMP" />
   
 </Frame>
 
@@ -28,7 +28,7 @@ You can configure users and roles in Settings → Roles.
 
 <Steps>
   <Step title="Open Roles settings">
-    Go to <b>Settings → Roles</b> in CrewAI Enterprise.
+    Go to <b>Settings → Roles</b> in CrewAI AMP.
   </Step>
   <Step title="Choose a role type">
     Use a predefined role (<b>Owner</b>, <b>Member</b>) or click <b>Create role</b> to define a custom one.
@@ -93,7 +93,7 @@ The organization owner always has access. In private mode, only whitelisted user
 </Tip>
 
 <Frame>
-  <img src="/images/enterprise/visibility.png" alt="Automation Visibility settings in CrewAI Enterprise" />
+  <img src="/images/enterprise/visibility.png" alt="Automation Visibility settings in CrewAI AMP" />
   
 </Frame>
 
diff --git a/docs/en/enterprise/features/tools-and-integrations.mdx b/docs/en/enterprise/features/tools-and-integrations.mdx
index 5da5699ce..530dec425 100644
--- a/docs/en/enterprise/features/tools-and-integrations.mdx
+++ b/docs/en/enterprise/features/tools-and-integrations.mdx
@@ -188,10 +188,10 @@ Tools & Integrations is the central hub for connecting third‑party apps and ma
 
   ## Internal Tools
 
-  Create custom tools locally, publish them on CrewAI Enterprise Tool Repository and use them in your agents. 
+  Create custom tools locally, publish them on CrewAI AMP Tool Repository and use them in your agents. 
 
   <Tip>
-  Before running the commands below, make sure you log in to your CrewAI Enterprise account by running this command: 
+  Before running the commands below, make sure you log in to your CrewAI AMP account by running this command: 
     ```bash
     crewai login
     ```
@@ -209,13 +209,13 @@ Tools & Integrations is the central hub for connecting third‑party apps and ma
       ```
     </Step>
     <Step title="Publish">
-      Publish the tool to the CrewAI Enterprise Tool Repository.
+      Publish the tool to the CrewAI AMP Tool Repository.
       ```bash
       crewai tool publish
       ```
     </Step>
     <Step title="Install">
-      Install the tool from the CrewAI Enterprise Tool Repository.
+      Install the tool from the CrewAI AMP Tool Repository.
       ```bash
       crewai tool install your-tool
       ```
diff --git a/docs/en/enterprise/features/traces.mdx b/docs/en/enterprise/features/traces.mdx
index bb281bae3..aba3fdf7a 100644
--- a/docs/en/enterprise/features/traces.mdx
+++ b/docs/en/enterprise/features/traces.mdx
@@ -11,7 +11,7 @@ Traces provide comprehensive visibility into your crew executions, helping you m
 
 ## What are Traces?
 
-Traces in CrewAI Enterprise are detailed execution records that capture every aspect of your crew's operation, from initial inputs to final outputs. They record:
+Traces in CrewAI AMP are detailed execution records that capture every aspect of your crew's operation, from initial inputs to final outputs. They record:
 
 - Agent thoughts and reasoning
 - Task execution details
@@ -28,7 +28,7 @@ Traces in CrewAI Enterprise are detailed execution records that capture every as
 
 <Steps>
   <Step title="Navigate to the Traces Tab">
-    Once in your CrewAI Enterprise dashboard, click on the **Traces** to view all execution records.
+    Once in your CrewAI AMP dashboard, click on the **Traces** to view all execution records.
   </Step>
   
   <Step title="Select an Execution">
@@ -153,5 +153,5 @@ CrewAI batches trace uploads to reduce overhead on high-volume runs:
 This yields more stable tracing under load while preserving detailed task/agent telemetry.
 
 <Card title="Need Help?" icon="headset" href="mailto:support@crewai.com">
-  Contact our support team for assistance with trace analysis or any other CrewAI Enterprise features.
+  Contact our support team for assistance with trace analysis or any other CrewAI AMP features.
 </Card>
\ No newline at end of file
diff --git a/docs/en/enterprise/features/webhook-streaming.mdx b/docs/en/enterprise/features/webhook-streaming.mdx
index e47eb2b99..777f401ae 100644
--- a/docs/en/enterprise/features/webhook-streaming.mdx
+++ b/docs/en/enterprise/features/webhook-streaming.mdx
@@ -8,7 +8,7 @@ mode: "wide"
 ## Overview
 
 Enterprise Event Streaming lets you receive real-time webhook updates about your crews and flows deployed to 
-CrewAI Enterprise, such as model calls, tool usage, and flow steps.
+CrewAI AMP, such as model calls, tool usage, and flow steps.
 
 ## Usage
 
diff --git a/docs/en/enterprise/guides/automation-triggers.mdx b/docs/en/enterprise/guides/automation-triggers.mdx
index 64cb95786..3f6b45b97 100644
--- a/docs/en/enterprise/guides/automation-triggers.mdx
+++ b/docs/en/enterprise/guides/automation-triggers.mdx
@@ -1,11 +1,11 @@
 ---
 title: "Triggers Overview"
-description: "Understand how CrewAI Enterprise triggers work, how to manage them, and where to find integration-specific playbooks"
+description: "Understand how CrewAI AMP triggers work, how to manage them, and where to find integration-specific playbooks"
 icon: "face-smile"
 mode: "wide"
 ---
 
-CrewAI Enterprise triggers connect your automations to real-time events across the tools your teams already use. Instead of polling systems or relying on manual kickoffs, triggers listen for changes—new emails, calendar updates, CRM status changes—and immediately launch the crew or flow you specify.
+CrewAI AMP triggers connect your automations to real-time events across the tools your teams already use. Instead of polling systems or relying on manual kickoffs, triggers listen for changes—new emails, calendar updates, CRM status changes—and immediately launch the crew or flow you specify.
 
 <Frame>
   ![Automation Triggers Overview](/images/enterprise/crew_connectors.png)
@@ -250,6 +250,6 @@ def delegate_to_crew(self, crewai_trigger_payload: dict = None):
 
 Automation triggers transform your CrewAI deployments into responsive, event-driven systems that can seamlessly integrate with your existing business processes and tools.
 
-<Card title="CrewAI Enterprise Trigger Examples" href="https://github.com/crewAIInc/crewai-enterprise-trigger-examples" icon="github">
+<Card title="CrewAI AMP Trigger Examples" href="https://github.com/crewAIInc/crewai-enterprise-trigger-examples" icon="github">
     Check them out on GitHub!
 </Card>
\ No newline at end of file
diff --git a/docs/en/enterprise/guides/azure-openai-setup.mdx b/docs/en/enterprise/guides/azure-openai-setup.mdx
index 6754208f7..6d1b206ae 100644
--- a/docs/en/enterprise/guides/azure-openai-setup.mdx
+++ b/docs/en/enterprise/guides/azure-openai-setup.mdx
@@ -19,8 +19,8 @@ This guide walks you through connecting Azure OpenAI with Crew Studio for seamle
             </Frame>
     </Step>
 
-    <Step title="Configure CrewAI Enterprise Connection">
-        4. In another tab, open `CrewAI Enterprise > LLM Connections`. Name your LLM Connection, select Azure as the provider, and choose the same model you selected in Azure.
+    <Step title="Configure CrewAI AMP Connection">
+        4. In another tab, open `CrewAI AMP > LLM Connections`. Name your LLM Connection, select Azure as the provider, and choose the same model you selected in Azure.
         5. On the same page, add environment variables from step 3:
             - One named `AZURE_DEPLOYMENT_TARGET_URL` (using the Target URI). The URL should look like this: https://your-deployment.openai.azure.com/openai/deployments/gpt-4o/chat/completions?api-version=2024-08-01-preview
             - Another named `AZURE_API_KEY` (using the Key).
@@ -28,7 +28,7 @@ This guide walks you through connecting Azure OpenAI with Crew Studio for seamle
     </Step>
 
     <Step title="Set Default Configuration">
-        7. In `CrewAI Enterprise > Settings > Defaults > Crew Studio LLM Settings`, set the new LLM Connection and model as defaults.
+        7. In `CrewAI AMP > Settings > Defaults > Crew Studio LLM Settings`, set the new LLM Connection and model as defaults.
     </Step>
 
     <Step title="Configure Network Access">
diff --git a/docs/en/enterprise/guides/build-crew.mdx b/docs/en/enterprise/guides/build-crew.mdx
index 774b7891e..38ea95853 100644
--- a/docs/en/enterprise/guides/build-crew.mdx
+++ b/docs/en/enterprise/guides/build-crew.mdx
@@ -7,7 +7,7 @@ mode: "wide"
 
 ## Overview
 
-[CrewAI Enterprise](https://app.crewai.com) streamlines the process of **creating**, **deploying**, and **managing** your AI agents in production environments.
+[CrewAI AMP](https://app.crewai.com) streamlines the process of **creating**, **deploying**, and **managing** your AI agents in production environments.
 
 ## Getting Started
 
diff --git a/docs/en/enterprise/guides/deploy-crew.mdx b/docs/en/enterprise/guides/deploy-crew.mdx
index 7d7d7ef1c..c017bd4db 100644
--- a/docs/en/enterprise/guides/deploy-crew.mdx
+++ b/docs/en/enterprise/guides/deploy-crew.mdx
@@ -1,12 +1,12 @@
 ---
 title: "Deploy Crew"
-description: "Deploying a Crew on CrewAI Enterprise"
+description: "Deploying a Crew on CrewAI AMP"
 icon: "rocket"
 mode: "wide"
 ---
 
 <Note>
-After creating a crew locally or through Crew Studio, the next step is deploying it to the CrewAI Enterprise platform. This guide covers multiple deployment methods to help you choose the best approach for your workflow.
+After creating a crew locally or through Crew Studio, the next step is deploying it to the CrewAI AMP platform. This guide covers multiple deployment methods to help you choose the best approach for your workflow.
 </Note>
 
 ## Prerequisites
@@ -39,10 +39,10 @@ The CLI provides the fastest way to deploy locally developed crews to the Enterp
   </Step>
 
   <Step title="Authenticate with the Enterprise Platform">
-    First, you need to authenticate your CLI with the CrewAI Enterprise platform:
+    First, you need to authenticate your CLI with the CrewAI AMP platform:
 
     ```bash
-    # If you already have a CrewAI Enterprise account, or want to create one:
+    # If you already have a CrewAI AMP account, or want to create one:
     crewai login
     ```
 
@@ -124,7 +124,7 @@ The CrewAI CLI offers several commands to manage your deployments:
 
 ## Option 2: Deploy Directly via Web Interface
 
-You can also deploy your crews directly through the CrewAI Enterprise web interface by connecting your GitHub account. This approach doesn't require using the CLI on your local machine.
+You can also deploy your crews directly through the CrewAI AMP web interface by connecting your GitHub account. This approach doesn't require using the CLI on your local machine.
 
 <Steps>
 
@@ -134,9 +134,9 @@ You can also deploy your crews directly through the CrewAI Enterprise web interf
 
   </Step>
 
-  <Step title="Connecting GitHub to CrewAI Enterprise">
+  <Step title="Connecting GitHub to CrewAI AMP">
 
-    1. Log in to [CrewAI Enterprise](https://app.crewai.com)
+    1. Log in to [CrewAI AMP](https://app.crewai.com)
     2. Click on the button "Connect GitHub"
 
     <Frame>
@@ -190,7 +190,7 @@ You can also deploy your crews directly through the CrewAI Enterprise web interf
 ## ⚠️ Environment Variable Security Requirements
 
 <Warning>
-**Important**: CrewAI Enterprise has security restrictions on environment variable names that can cause deployment failures if not followed.
+**Important**: CrewAI AMP has security restrictions on environment variable names that can cause deployment failures if not followed.
 </Warning>
 
 ### Blocked Environment Variable Patterns
diff --git a/docs/en/enterprise/guides/enable-crew-studio.mdx b/docs/en/enterprise/guides/enable-crew-studio.mdx
index 328cad261..1153da80b 100644
--- a/docs/en/enterprise/guides/enable-crew-studio.mdx
+++ b/docs/en/enterprise/guides/enable-crew-studio.mdx
@@ -1,6 +1,6 @@
 ---
 title: "Enable Crew Studio"
-description: "Enabling Crew Studio on CrewAI Enterprise"
+description: "Enabling Crew Studio on CrewAI AMP"
 icon: "comments"
 mode: "wide"
 ---
@@ -24,7 +24,7 @@ With Crew Studio, you can:
 - Select appropriate tools
 - Configure necessary inputs
 - Generate downloadable code for customization
-- Deploy directly to the CrewAI Enterprise platform
+- Deploy directly to the CrewAI AMP platform
 
 ## Configuration Steps
 
@@ -32,7 +32,7 @@ Before you can start using Crew Studio, you need to configure your LLM connectio
 
 <Steps>
   <Step title="Set Up LLM Connection">
-    Go to the **LLM Connections** tab in your CrewAI Enterprise dashboard and create a new LLM connection.
+    Go to the **LLM Connections** tab in your CrewAI AMP dashboard and create a new LLM connection.
 
     <Note>
       Feel free to use any LLM provider you want that is supported by CrewAI.
@@ -82,7 +82,7 @@ Now that you've configured your LLM connection and default settings, you're read
 
 <Steps>
   <Step title="Access Studio">
-    Navigate to the **Studio** section in your CrewAI Enterprise dashboard.
+    Navigate to the **Studio** section in your CrewAI AMP dashboard.
   </Step>
   
   <Step title="Start a Conversation">
@@ -110,7 +110,7 @@ Now that you've configured your LLM connection and default settings, you're read
     Once you're satisfied with the configuration, you can:
     
     - Download the generated code for local customization
-    - Deploy the crew directly to the CrewAI Enterprise platform
+    - Deploy the crew directly to the CrewAI AMP platform
     - Modify the configuration and regenerate the crew
   </Step>
   
@@ -162,6 +162,6 @@ Here's a typical workflow for creating a crew with Crew Studio:
 </Steps>
 
 <Card title="Need Help?" icon="headset" href="mailto:support@crewai.com">
-  Contact our support team for assistance with Crew Studio or any other CrewAI Enterprise features.
+  Contact our support team for assistance with Crew Studio or any other CrewAI AMP features.
 </Card>
 
diff --git a/docs/en/enterprise/guides/gmail-trigger.mdx b/docs/en/enterprise/guides/gmail-trigger.mdx
index 1f23ff94e..2caefc045 100644
--- a/docs/en/enterprise/guides/gmail-trigger.mdx
+++ b/docs/en/enterprise/guides/gmail-trigger.mdx
@@ -15,7 +15,7 @@ Use the Gmail Trigger to kick off your deployed crews when Gmail events happen i
 
 ## Enabling the Gmail Trigger
 
-1. Open your deployment in CrewAI Enterprise
+1. Open your deployment in CrewAI AMP
 2. Go to the **Triggers** tab
 3. Locate **Gmail** and switch the toggle to enable
 
@@ -55,7 +55,7 @@ The Gmail payload will be available via the standard context mechanisms. See the
 
 ### Sample payloads & crews
 
-The [CrewAI Enterprise Trigger Examples repository](https://github.com/crewAIInc/crewai-enterprise-trigger-examples/tree/main/gmail) includes:
+The [CrewAI AMP Trigger Examples repository](https://github.com/crewAIInc/crewai-enterprise-trigger-examples/tree/main/gmail) includes:
 
 - `new-email-payload-1.json` / `new-email-payload-2.json` — production-style new message alerts with matching crews in `new-email-crew.py`
 - `thread-updated-sample-1.json` — follow-up messages on an existing thread, processed by `gmail-alert-crew.py`
diff --git a/docs/en/enterprise/guides/google-calendar-trigger.mdx b/docs/en/enterprise/guides/google-calendar-trigger.mdx
index 2db3b7c17..cf2d32471 100644
--- a/docs/en/enterprise/guides/google-calendar-trigger.mdx
+++ b/docs/en/enterprise/guides/google-calendar-trigger.mdx
@@ -15,7 +15,7 @@ Use the Google Calendar trigger to launch automations whenever calendar events c
 
 ## Enabling the Google Calendar Trigger
 
-1. Open your deployment in CrewAI Enterprise
+1. Open your deployment in CrewAI AMP
 2. Go to the **Triggers** tab
 3. Locate **Google Calendar** and switch the toggle to enable
 
diff --git a/docs/en/enterprise/guides/google-drive-trigger.mdx b/docs/en/enterprise/guides/google-drive-trigger.mdx
index a32050620..19c10837b 100644
--- a/docs/en/enterprise/guides/google-drive-trigger.mdx
+++ b/docs/en/enterprise/guides/google-drive-trigger.mdx
@@ -15,7 +15,7 @@ Trigger your automations when files are created, updated, or removed in Google D
 
 ## Enabling the Google Drive Trigger
 
-1. Open your deployment in CrewAI Enterprise
+1. Open your deployment in CrewAI AMP
 2. Go to the **Triggers** tab
 3. Locate **Google Drive** and switch the toggle to enable
 
diff --git a/docs/en/enterprise/guides/hubspot-trigger.mdx b/docs/en/enterprise/guides/hubspot-trigger.mdx
index 22d41d98e..e4c783b19 100644
--- a/docs/en/enterprise/guides/hubspot-trigger.mdx
+++ b/docs/en/enterprise/guides/hubspot-trigger.mdx
@@ -5,22 +5,22 @@ icon: "hubspot"
 mode: "wide"
 ---
 
-This guide provides a step-by-step process to set up HubSpot triggers for CrewAI Enterprise, enabling you to initiate crews directly from HubSpot Workflows.
+This guide provides a step-by-step process to set up HubSpot triggers for CrewAI AMP, enabling you to initiate crews directly from HubSpot Workflows.
 
 ## Prerequisites
 
-- A CrewAI Enterprise account
+- A CrewAI AMP account
 - A HubSpot account with the [HubSpot Workflows](https://knowledge.hubspot.com/workflows/create-workflows) feature
 
 ## Setup Steps
 
 <Steps>
-    <Step title="Connect your HubSpot account with CrewAI Enterprise">
-        - Log in to your `CrewAI Enterprise account > Triggers`
+    <Step title="Connect your HubSpot account with CrewAI AMP">
+        - Log in to your `CrewAI AMP account > Triggers`
         - Select `HubSpot` from the list of available triggers
-        - Choose the HubSpot account you want to connect with CrewAI Enterprise
-        - Follow the on-screen prompts to authorize CrewAI Enterprise access to your HubSpot account
-        - A confirmation message will appear once HubSpot is successfully connected with CrewAI Enterprise
+        - Choose the HubSpot account you want to connect with CrewAI AMP
+        - Follow the on-screen prompts to authorize CrewAI AMP access to your HubSpot account
+        - A confirmation message will appear once HubSpot is successfully connected with CrewAI AMP
     </Step>
     <Step title="Create a HubSpot Workflow">
         - Log in to your `HubSpot account > Automations > Workflows > New workflow`
diff --git a/docs/en/enterprise/guides/kickoff-crew.mdx b/docs/en/enterprise/guides/kickoff-crew.mdx
index 243c2375f..ec049acd0 100644
--- a/docs/en/enterprise/guides/kickoff-crew.mdx
+++ b/docs/en/enterprise/guides/kickoff-crew.mdx
@@ -1,19 +1,19 @@
 ---
 title: "Kickoff Crew"
-description: "Kickoff a Crew on CrewAI Enterprise"
+description: "Kickoff a Crew on CrewAI AMP"
 icon: "flag-checkered"
 mode: "wide"
 ---
 
 ## Overview
 
-Once you've deployed your crew to the CrewAI Enterprise platform, you can kickoff executions through the web interface or the API. This guide covers both approaches.
+Once you've deployed your crew to the CrewAI AMP platform, you can kickoff executions through the web interface or the API. This guide covers both approaches.
 
 ## Method 1: Using the Web Interface
 
 ### Step 1: Navigate to Your Deployed Crew
 
-1. Log in to [CrewAI Enterprise](https://app.crewai.com)
+1. Log in to [CrewAI AMP](https://app.crewai.com)
 2. Click on the crew name from your projects list
 3. You'll be taken to the crew's detail page
 
@@ -83,7 +83,7 @@ Once execution is complete:
 
 ## Method 2: Using the API
 
-You can also kickoff crews programmatically using the CrewAI Enterprise REST API.
+You can also kickoff crews programmatically using the CrewAI AMP REST API.
 
 ### Authentication
 
diff --git a/docs/en/enterprise/guides/microsoft-teams-trigger.mdx b/docs/en/enterprise/guides/microsoft-teams-trigger.mdx
index 9267131ea..10878af40 100644
--- a/docs/en/enterprise/guides/microsoft-teams-trigger.mdx
+++ b/docs/en/enterprise/guides/microsoft-teams-trigger.mdx
@@ -15,7 +15,7 @@ Use the Microsoft Teams trigger to start automations whenever a new chat is crea
 
 ## Enabling the Microsoft Teams Trigger
 
-1. Open your deployment in CrewAI Enterprise
+1. Open your deployment in CrewAI AMP
 2. Go to the **Triggers** tab
 3. Locate **Microsoft Teams** and switch the toggle to enable
 
diff --git a/docs/en/enterprise/guides/onedrive-trigger.mdx b/docs/en/enterprise/guides/onedrive-trigger.mdx
index 78edfe4b3..51de175db 100644
--- a/docs/en/enterprise/guides/onedrive-trigger.mdx
+++ b/docs/en/enterprise/guides/onedrive-trigger.mdx
@@ -15,7 +15,7 @@ Start automations when files change inside OneDrive. You can generate audit summ
 
 ## Enabling the OneDrive Trigger
 
-1. Open your deployment in CrewAI Enterprise
+1. Open your deployment in CrewAI AMP
 2. Go to the **Triggers** tab
 3. Locate **OneDrive** and switch the toggle to enable
 
diff --git a/docs/en/enterprise/guides/outlook-trigger.mdx b/docs/en/enterprise/guides/outlook-trigger.mdx
index ff2fd98d7..21bda5407 100644
--- a/docs/en/enterprise/guides/outlook-trigger.mdx
+++ b/docs/en/enterprise/guides/outlook-trigger.mdx
@@ -15,7 +15,7 @@ Automate responses when Outlook delivers a new message or when an event is remov
 
 ## Enabling the Outlook Trigger
 
-1. Open your deployment in CrewAI Enterprise
+1. Open your deployment in CrewAI AMP
 2. Go to the **Triggers** tab
 3. Locate **Outlook** and switch the toggle to enable
 
diff --git a/docs/en/enterprise/guides/react-component-export.mdx b/docs/en/enterprise/guides/react-component-export.mdx
index 8e811b2ee..f899477a3 100644
--- a/docs/en/enterprise/guides/react-component-export.mdx
+++ b/docs/en/enterprise/guides/react-component-export.mdx
@@ -1,11 +1,11 @@
 ---
 title: "React Component Export"
-description: "Learn how to export and integrate CrewAI Enterprise React components into your applications"
+description: "Learn how to export and integrate CrewAI AMP React components into your applications"
 icon: "react"
 mode: "wide"
 ---
 
-This guide explains how to export CrewAI Enterprise crews as React components and integrate them into your own applications.
+This guide explains how to export CrewAI AMP crews as React components and integrate them into your own applications.
 
 ## Exporting a React Component
 
diff --git a/docs/en/enterprise/guides/salesforce-trigger.mdx b/docs/en/enterprise/guides/salesforce-trigger.mdx
index 50d4e75ea..5d2443c6b 100644
--- a/docs/en/enterprise/guides/salesforce-trigger.mdx
+++ b/docs/en/enterprise/guides/salesforce-trigger.mdx
@@ -5,7 +5,7 @@ icon: "salesforce"
 mode: "wide"
 ---
 
-CrewAI Enterprise can be triggered from Salesforce to automate customer relationship management workflows and enhance your sales operations.
+CrewAI AMP can be triggered from Salesforce to automate customer relationship management workflows and enhance your sales operations.
 
 ## Overview
 
@@ -31,7 +31,7 @@ Salesforce is a leading customer relationship management (CRM) platform that hel
 
 To set up Salesforce triggers:
 
-1. **Contact Support**: Reach out to CrewAI Enterprise support for assistance with Salesforce trigger setup
+1. **Contact Support**: Reach out to CrewAI AMP support for assistance with Salesforce trigger setup
 2. **Review Requirements**: Ensure you have the necessary Salesforce permissions and API access
 3. **Configure Connection**: Work with the support team to establish the connection between CrewAI and your Salesforce instance
 4. **Test Triggers**: Verify the triggers work correctly with your specific use cases
@@ -47,4 +47,4 @@ Common Salesforce + CrewAI trigger scenarios include:
 
 ## Next Steps
 
-For detailed setup instructions and advanced configuration options, please contact CrewAI Enterprise support who can provide tailored guidance for your specific Salesforce environment and business needs. 
+For detailed setup instructions and advanced configuration options, please contact CrewAI AMP support who can provide tailored guidance for your specific Salesforce environment and business needs. 
diff --git a/docs/en/enterprise/guides/team-management.mdx b/docs/en/enterprise/guides/team-management.mdx
index 38de46490..0cf6daabe 100644
--- a/docs/en/enterprise/guides/team-management.mdx
+++ b/docs/en/enterprise/guides/team-management.mdx
@@ -1,17 +1,17 @@
 ---
 title: "Team Management"
-description: "Learn how to invite and manage team members in your CrewAI Enterprise organization"
+description: "Learn how to invite and manage team members in your CrewAI AMP organization"
 icon: "users"
 mode: "wide"
 ---
 
-As an administrator of a CrewAI Enterprise account, you can easily invite new team members to join your organization. This guide will walk you through the process step-by-step.
+As an administrator of a CrewAI AMP account, you can easily invite new team members to join your organization. This guide will walk you through the process step-by-step.
 
 ## Inviting Team Members
 
 <Steps>
     <Step title="Access the Settings Page">
-        - Log in to your CrewAI Enterprise account
+        - Log in to your CrewAI AMP account
         - Look for the gear icon (⚙️) in the top right corner of the dashboard
         - Click on the gear icon to access the **Settings** page:
             <Frame caption="Settings page">
@@ -43,7 +43,7 @@ You can add roles to your team members to control their access to different part
 
 <Steps>
     <Step title="Access the Settings Page">
-        - Log in to your CrewAI Enterprise account
+        - Log in to your CrewAI AMP account
         - Look for the gear icon (⚙️) in the top right corner of the dashboard
         - Click on the gear icon to access the **Settings** page:
             <Frame>
@@ -85,4 +85,4 @@ You can add roles to your team members to control their access to different part
 - **Invitation Acceptance**: Invited members will need to accept the invitation to join your organization
 - **Email Notifications**: You may want to inform your team members to check their email (including spam folders) for the invitation
 
-By following these steps, you can easily expand your team and collaborate more effectively within your CrewAI Enterprise organization. 
\ No newline at end of file
+By following these steps, you can easily expand your team and collaborate more effectively within your CrewAI AMP organization. 
\ No newline at end of file
diff --git a/docs/en/enterprise/guides/tool-repository.mdx b/docs/en/enterprise/guides/tool-repository.mdx
index 3707d99eb..0e9c8f287 100644
--- a/docs/en/enterprise/guides/tool-repository.mdx
+++ b/docs/en/enterprise/guides/tool-repository.mdx
@@ -20,11 +20,11 @@ The repository is not a version control system. Use Git to track code changes an
 
 Before using the Tool Repository, ensure you have:
 
-- A [CrewAI Enterprise](https://app.crewai.com) account
+- A [CrewAI AMP](https://app.crewai.com) account
 - [CrewAI CLI](https://docs.crewai.com/concepts/cli#cli) installed
 - uv>=0.5.0 installed. Check out [how to upgrade](https://docs.astral.sh/uv/getting-started/installation/#upgrading-uv)
 - [Git](https://git-scm.com) installed and configured
-- Access permissions to publish or install tools in your CrewAI Enterprise organization
+- Access permissions to publish or install tools in your CrewAI AMP organization
 
 ## Installing Tools
 
@@ -54,11 +54,11 @@ researcher = Agent(
 
 ## Adding other packages after installing a tool
 
-After installing a tool from the CrewAI Enterprise Tool Repository, you need to use the `crewai uv` command to add other packages to your project.
+After installing a tool from the CrewAI AMP Tool Repository, you need to use the `crewai uv` command to add other packages to your project.
 Using pure `uv` commands will fail due to authentication to tool repository being handled by the CLI. By using the `crewai uv` command, you can add other packages to your project without having to worry about authentication.
 Any `uv` command can be used with the `crewai uv` command, making it a powerful tool for managing your project's dependencies without the hassle of managing authentication through environment variables or other methods.
 
-Say that you have installed a custom tool from the CrewAI Enterprise Tool Repository called "my-tool":
+Say that you have installed a custom tool from the CrewAI AMP Tool Repository called "my-tool":
 
 ```bash
 crewai tool install my-tool
@@ -131,7 +131,7 @@ crewai tool publish
 
 To delete a tool:
 
-1. Go to [CrewAI Enterprise](https://app.crewai.com)
+1. Go to [CrewAI AMP](https://app.crewai.com)
 2. Navigate to **Tools**
 3. Select the tool
 4. Click **Delete**
@@ -146,7 +146,7 @@ Every published version undergoes automated security checks, and are only availa
 
 You can check the security check status of a tool at:
 
-`CrewAI Enterprise > Tools > Your Tool > Versions`
+`CrewAI AMP > Tools > Your Tool > Versions`
 
 <Card title="Need Help?" icon="headset" href="mailto:support@crewai.com">
   Contact our support team for assistance with API integration or troubleshooting.
diff --git a/docs/en/enterprise/guides/update-crew.mdx b/docs/en/enterprise/guides/update-crew.mdx
index b6aa9f74b..0bff60216 100644
--- a/docs/en/enterprise/guides/update-crew.mdx
+++ b/docs/en/enterprise/guides/update-crew.mdx
@@ -1,12 +1,12 @@
 ---
 title: "Update Crew"
-description: "Updating a Crew on CrewAI Enterprise"
+description: "Updating a Crew on CrewAI AMP"
 icon: "pencil"
 mode: "wide"
 ---
 
 <Note>
-After deploying your crew to CrewAI Enterprise, you may need to make updates to the code, security settings, or configuration. 
+After deploying your crew to CrewAI AMP, you may need to make updates to the code, security settings, or configuration. 
 This guide explains how to perform these common update operations.
 </Note>
 
@@ -23,7 +23,7 @@ There are several reasons you might want to update your crew deployment:
 
 When you've pushed new commits to your GitHub repository and want to update your deployment:
 
-1. Navigate to your crew in the CrewAI Enterprise platform
+1. Navigate to your crew in the CrewAI AMP platform
 2. Click on the `Re-deploy` button on your crew details page
 
 <Frame>
@@ -36,7 +36,7 @@ This will trigger an update that you can track using the progress bar. The syste
 
 If you need to generate a new bearer token (for example, if you suspect the current token might have been compromised):
 
-1. Navigate to your crew in the CrewAI Enterprise platform
+1. Navigate to your crew in the CrewAI AMP platform
 2. Find the `Bearer Token` section
 3. Click the `Reset` button next to your current token
 
diff --git a/docs/en/enterprise/guides/webhook-automation.mdx b/docs/en/enterprise/guides/webhook-automation.mdx
index 2228b95ef..cb0af912c 100644
--- a/docs/en/enterprise/guides/webhook-automation.mdx
+++ b/docs/en/enterprise/guides/webhook-automation.mdx
@@ -1,17 +1,17 @@
 ---
 title: "Webhook Automation"
-description: "Automate CrewAI Enterprise workflows using webhooks with platforms like ActivePieces, Zapier, and Make.com"
+description: "Automate CrewAI AMP workflows using webhooks with platforms like ActivePieces, Zapier, and Make.com"
 icon: "webhook"
 mode: "wide"
 ---
 
-CrewAI Enterprise allows you to automate your workflow using webhooks. This article will guide you through the process of setting up and using webhooks to kickoff your crew execution, with a focus on integration with ActivePieces, a workflow automation platform similar to Zapier and Make.com.
+CrewAI AMP allows you to automate your workflow using webhooks. This article will guide you through the process of setting up and using webhooks to kickoff your crew execution, with a focus on integration with ActivePieces, a workflow automation platform similar to Zapier and Make.com.
 
 ## Setting Up Webhooks
 
 <Steps>
     <Step title="Accessing the Kickoff Interface">
-        - Navigate to the CrewAI Enterprise dashboard
+        - Navigate to the CrewAI AMP dashboard
         - Look for the `/kickoff` section, which is used to start the crew execution
             <Frame>
                 <img src="/images/enterprise/kickoff-interface.png" alt="Kickoff Interface" />
@@ -44,7 +44,7 @@ CrewAI Enterprise allows you to automate your workflow using webhooks. This arti
         3. Add an HTTP action step
             - Set the action to `Send HTTP request`
             - Use `POST` as the method
-            - Set the URL to your CrewAI Enterprise kickoff endpoint
+            - Set the URL to your CrewAI AMP kickoff endpoint
             - Add necessary headers (e.g., `Bearer Token`)
                 <Frame>
                     <img src="/images/enterprise/activepieces-headers.png" alt="ActivePieces Headers" />
diff --git a/docs/en/enterprise/guides/zapier-trigger.mdx b/docs/en/enterprise/guides/zapier-trigger.mdx
index d308a63bb..0c0e10cdf 100644
--- a/docs/en/enterprise/guides/zapier-trigger.mdx
+++ b/docs/en/enterprise/guides/zapier-trigger.mdx
@@ -5,11 +5,11 @@ icon: "bolt"
 mode: "wide"
 ---
 
-This guide will walk you through the process of setting up Zapier triggers for CrewAI Enterprise, allowing you to automate workflows between CrewAI Enterprise and other applications.
+This guide will walk you through the process of setting up Zapier triggers for CrewAI AMP, allowing you to automate workflows between CrewAI AMP and other applications.
 
 ## Prerequisites
 
-- A CrewAI Enterprise account
+- A CrewAI AMP account
 - A Zapier account
 - A Slack account (for this specific example)
 
@@ -32,7 +32,7 @@ This guide will walk you through the process of setting up Zapier triggers for C
         - Connect your Slack account if you haven't already.
     </Step>
 
-    <Step title="Configure the CrewAI Enterprise Action">
+    <Step title="Configure the CrewAI AMP Action">
         - Add a new action step to your Zap.
         - Choose CrewAI+ as your action app and Kickoff as the Action Event
 
@@ -41,8 +41,8 @@ This guide will walk you through the process of setting up Zapier triggers for C
         </Frame>
     </Step>
 
-    <Step title="Connect your CrewAI Enterprise account">
-        - Connect your CrewAI Enterprise account.
+    <Step title="Connect your CrewAI AMP account">
+        - Connect your CrewAI AMP account.
         - Select the appropriate Crew for your workflow.
 
         <Frame>
@@ -51,8 +51,8 @@ This guide will walk you through the process of setting up Zapier triggers for C
         - Configure the inputs for the Crew using the data from the Slack message.
     </Step>
 
-    <Step title="Format the CrewAI Enterprise Output">
-        - Add another action step to format the text output from CrewAI Enterprise.
+    <Step title="Format the CrewAI AMP Output">
+        - Add another action step to format the text output from CrewAI AMP.
         - Use Zapier's formatting tools to convert the Markdown output to HTML.
 
         <Frame>
@@ -67,7 +67,7 @@ This guide will walk you through the process of setting up Zapier triggers for C
         - Add a final action step to send the formatted output via email.
         - Choose your preferred email service (e.g., Gmail, Outlook).
         - Configure the email details, including recipient, subject, and body.
-        - Insert the formatted CrewAI Enterprise output into the email body.
+        - Insert the formatted CrewAI AMP output into the email body.
 
         <Frame>
             <img src="/images/enterprise/zapier-7.png" alt="Zapier 7" />
@@ -97,8 +97,8 @@ This guide will walk you through the process of setting up Zapier triggers for C
 
 ## Tips for Success
 
-- Ensure that your CrewAI Enterprise inputs are correctly mapped from the Slack message.
+- Ensure that your CrewAI AMP inputs are correctly mapped from the Slack message.
 - Test your Zap thoroughly before turning it on to catch any potential issues.
 - Consider adding error handling steps to manage potential failures in the workflow.
 
-By following these steps, you'll have successfully set up Zapier triggers for CrewAI Enterprise, allowing for automated workflows triggered by Slack messages and resulting in email notifications with CrewAI Enterprise output. 
\ No newline at end of file
+By following these steps, you'll have successfully set up Zapier triggers for CrewAI AMP, allowing for automated workflows triggered by Slack messages and resulting in email notifications with CrewAI AMP output. 
\ No newline at end of file
diff --git a/docs/en/enterprise/integrations/asana.mdx b/docs/en/enterprise/integrations/asana.mdx
index 34d989498..5e5a2ea46 100644
--- a/docs/en/enterprise/integrations/asana.mdx
+++ b/docs/en/enterprise/integrations/asana.mdx
@@ -13,7 +13,7 @@ Enable your agents to manage tasks, projects, and team coordination through Asan
 
 Before using the Asana integration, ensure you have:
 
-- A [CrewAI Enterprise](https://app.crewai.com) account with an active subscription
+- A [CrewAI AMP](https://app.crewai.com) account with an active subscription
 - An Asana account with appropriate permissions
 - Connected your Asana account through the [Integrations page](https://app.crewai.com/crewai_plus/connectors)
 
@@ -21,7 +21,7 @@ Before using the Asana integration, ensure you have:
 
 ### 1. Connect Your Asana Account
 
-1. Navigate to [CrewAI Enterprise Integrations](https://app.crewai.com/crewai_plus/connectors)
+1. Navigate to [CrewAI AMP Integrations](https://app.crewai.com/crewai_plus/connectors)
 2. Find **Asana** in the Authentication Integrations section
 3. Click **Connect** and complete the OAuth flow
 4. Grant the necessary permissions for task and project management
diff --git a/docs/en/enterprise/integrations/box.mdx b/docs/en/enterprise/integrations/box.mdx
index de51cd532..472788505 100644
--- a/docs/en/enterprise/integrations/box.mdx
+++ b/docs/en/enterprise/integrations/box.mdx
@@ -13,7 +13,7 @@ Enable your agents to manage files, folders, and documents through Box. Upload f
 
 Before using the Box integration, ensure you have:
 
-- A [CrewAI Enterprise](https://app.crewai.com) account with an active subscription
+- A [CrewAI AMP](https://app.crewai.com) account with an active subscription
 - A Box account with appropriate permissions
 - Connected your Box account through the [Integrations page](https://app.crewai.com/crewai_plus/connectors)
 
@@ -21,7 +21,7 @@ Before using the Box integration, ensure you have:
 
 ### 1. Connect Your Box Account
 
-1. Navigate to [CrewAI Enterprise Integrations](https://app.crewai.com/crewai_plus/connectors)
+1. Navigate to [CrewAI AMP Integrations](https://app.crewai.com/crewai_plus/connectors)
 2. Find **Box** in the Authentication Integrations section
 3. Click **Connect** and complete the OAuth flow
 4. Grant the necessary permissions for file and folder management
diff --git a/docs/en/enterprise/integrations/clickup.mdx b/docs/en/enterprise/integrations/clickup.mdx
index 7704fcc3e..a8549f72a 100644
--- a/docs/en/enterprise/integrations/clickup.mdx
+++ b/docs/en/enterprise/integrations/clickup.mdx
@@ -13,7 +13,7 @@ Enable your agents to manage tasks, projects, and productivity workflows through
 
 Before using the ClickUp integration, ensure you have:
 
-- A [CrewAI Enterprise](https://app.crewai.com) account with an active subscription
+- A [CrewAI AMP](https://app.crewai.com) account with an active subscription
 - A ClickUp account with appropriate permissions
 - Connected your ClickUp account through the [Integrations page](https://app.crewai.com/crewai_plus/connectors)
 
@@ -21,7 +21,7 @@ Before using the ClickUp integration, ensure you have:
 
 ### 1. Connect Your ClickUp Account
 
-1. Navigate to [CrewAI Enterprise Integrations](https://app.crewai.com/crewai_plus/connectors)
+1. Navigate to [CrewAI AMP Integrations](https://app.crewai.com/crewai_plus/connectors)
 2. Find **ClickUp** in the Authentication Integrations section
 3. Click **Connect** and complete the OAuth flow
 4. Grant the necessary permissions for task and project management
diff --git a/docs/en/enterprise/integrations/github.mdx b/docs/en/enterprise/integrations/github.mdx
index 5c30d330f..2e439b96c 100644
--- a/docs/en/enterprise/integrations/github.mdx
+++ b/docs/en/enterprise/integrations/github.mdx
@@ -13,7 +13,7 @@ Enable your agents to manage repositories, issues, and releases through GitHub.
 
 Before using the GitHub integration, ensure you have:
 
-- A [CrewAI Enterprise](https://app.crewai.com) account with an active subscription
+- A [CrewAI AMP](https://app.crewai.com) account with an active subscription
 - A GitHub account with appropriate repository permissions
 - Connected your GitHub account through the [Integrations page](https://app.crewai.com/crewai_plus/connectors)
 
@@ -21,7 +21,7 @@ Before using the GitHub integration, ensure you have:
 
 ### 1. Connect Your GitHub Account
 
-1. Navigate to [CrewAI Enterprise Integrations](https://app.crewai.com/crewai_plus/connectors)
+1. Navigate to [CrewAI AMP Integrations](https://app.crewai.com/crewai_plus/connectors)
 2. Find **GitHub** in the Authentication Integrations section
 3. Click **Connect** and complete the OAuth flow
 4. Grant the necessary permissions for repository and issue management
diff --git a/docs/en/enterprise/integrations/gmail.mdx b/docs/en/enterprise/integrations/gmail.mdx
index f2e870d7f..594ece22f 100644
--- a/docs/en/enterprise/integrations/gmail.mdx
+++ b/docs/en/enterprise/integrations/gmail.mdx
@@ -13,7 +13,7 @@ Enable your agents to manage emails, contacts, and drafts through Gmail. Send em
 
 Before using the Gmail integration, ensure you have:
 
-- A [CrewAI Enterprise](https://app.crewai.com) account with an active subscription
+- A [CrewAI AMP](https://app.crewai.com) account with an active subscription
 - A Gmail account with appropriate permissions
 - Connected your Gmail account through the [Integrations page](https://app.crewai.com/crewai_plus/connectors)
 
@@ -21,7 +21,7 @@ Before using the Gmail integration, ensure you have:
 
 ### 1. Connect Your Gmail Account
 
-1. Navigate to [CrewAI Enterprise Integrations](https://app.crewai.com/crewai_plus/connectors)
+1. Navigate to [CrewAI AMP Integrations](https://app.crewai.com/crewai_plus/connectors)
 2. Find **Gmail** in the Authentication Integrations section
 3. Click **Connect** and complete the OAuth flow
 4. Grant the necessary permissions for email and contact management
diff --git a/docs/en/enterprise/integrations/google_calendar.mdx b/docs/en/enterprise/integrations/google_calendar.mdx
index a9bca43e8..01eb8a031 100644
--- a/docs/en/enterprise/integrations/google_calendar.mdx
+++ b/docs/en/enterprise/integrations/google_calendar.mdx
@@ -13,7 +13,7 @@ Enable your agents to manage calendar events, schedules, and availability throug
 
 Before using the Google Calendar integration, ensure you have:
 
-- A [CrewAI Enterprise](https://app.crewai.com) account with an active subscription
+- A [CrewAI AMP](https://app.crewai.com) account with an active subscription
 - A Google account with Google Calendar access
 - Connected your Google account through the [Integrations page](https://app.crewai.com/crewai_plus/connectors)
 
@@ -21,7 +21,7 @@ Before using the Google Calendar integration, ensure you have:
 
 ### 1. Connect Your Google Account
 
-1. Navigate to [CrewAI Enterprise Integrations](https://app.crewai.com/crewai_plus/connectors)
+1. Navigate to [CrewAI AMP Integrations](https://app.crewai.com/crewai_plus/connectors)
 2. Find **Google Calendar** in the Authentication Integrations section
 3. Click **Connect** and complete the OAuth flow
 4. Grant the necessary permissions for calendar and contact access
diff --git a/docs/en/enterprise/integrations/google_sheets.mdx b/docs/en/enterprise/integrations/google_sheets.mdx
index 7ae78fd27..9ccad0d33 100644
--- a/docs/en/enterprise/integrations/google_sheets.mdx
+++ b/docs/en/enterprise/integrations/google_sheets.mdx
@@ -13,7 +13,7 @@ Enable your agents to manage spreadsheet data through Google Sheets. Read rows,
 
 Before using the Google Sheets integration, ensure you have:
 
-- A [CrewAI Enterprise](https://app.crewai.com) account with an active subscription
+- A [CrewAI AMP](https://app.crewai.com) account with an active subscription
 - A Google account with Google Sheets access
 - Connected your Google account through the [Integrations page](https://app.crewai.com/crewai_plus/connectors)
 - Spreadsheets with proper column headers for data operations
@@ -22,7 +22,7 @@ Before using the Google Sheets integration, ensure you have:
 
 ### 1. Connect Your Google Account
 
-1. Navigate to [CrewAI Enterprise Integrations](https://app.crewai.com/crewai_plus/connectors)
+1. Navigate to [CrewAI AMP Integrations](https://app.crewai.com/crewai_plus/connectors)
 2. Find **Google Sheets** in the Authentication Integrations section
 3. Click **Connect** and complete the OAuth flow
 4. Grant the necessary permissions for spreadsheet access
diff --git a/docs/en/enterprise/integrations/hubspot.mdx b/docs/en/enterprise/integrations/hubspot.mdx
index a97bd6dc5..e3aeda8ab 100644
--- a/docs/en/enterprise/integrations/hubspot.mdx
+++ b/docs/en/enterprise/integrations/hubspot.mdx
@@ -13,7 +13,7 @@ Enable your agents to manage companies and contacts within HubSpot. Create new r
 
 Before using the HubSpot integration, ensure you have:
 
-- A [CrewAI Enterprise](https://app.crewai.com) account with an active subscription.
+- A [CrewAI AMP](https://app.crewai.com) account with an active subscription.
 - A HubSpot account with appropriate permissions.
 - Connected your HubSpot account through the [Integrations page](https://app.crewai.com/crewai_plus/connectors).
 
@@ -21,7 +21,7 @@ Before using the HubSpot integration, ensure you have:
 
 ### 1. Connect Your HubSpot Account
 
-1. Navigate to [CrewAI Enterprise Integrations](https://app.crewai.com/crewai_plus/connectors).
+1. Navigate to [CrewAI AMP Integrations](https://app.crewai.com/crewai_plus/connectors).
 2. Find **HubSpot** in the Authentication Integrations section.
 3. Click **Connect** and complete the OAuth flow.
 4. Grant the necessary permissions for company and contact management.
diff --git a/docs/en/enterprise/integrations/jira.mdx b/docs/en/enterprise/integrations/jira.mdx
index 53827f300..1eedb8fb9 100644
--- a/docs/en/enterprise/integrations/jira.mdx
+++ b/docs/en/enterprise/integrations/jira.mdx
@@ -13,7 +13,7 @@ Enable your agents to manage issues, projects, and workflows through Jira. Creat
 
 Before using the Jira integration, ensure you have:
 
-- A [CrewAI Enterprise](https://app.crewai.com) account with an active subscription
+- A [CrewAI AMP](https://app.crewai.com) account with an active subscription
 - A Jira account with appropriate project permissions
 - Connected your Jira account through the [Integrations page](https://app.crewai.com/crewai_plus/connectors)
 
@@ -21,7 +21,7 @@ Before using the Jira integration, ensure you have:
 
 ### 1. Connect Your Jira Account
 
-1. Navigate to [CrewAI Enterprise Integrations](https://app.crewai.com/crewai_plus/connectors)
+1. Navigate to [CrewAI AMP Integrations](https://app.crewai.com/crewai_plus/connectors)
 2. Find **Jira** in the Authentication Integrations section
 3. Click **Connect** and complete the OAuth flow
 4. Grant the necessary permissions for issue and project management
diff --git a/docs/en/enterprise/integrations/linear.mdx b/docs/en/enterprise/integrations/linear.mdx
index 844ca0a88..875c64808 100644
--- a/docs/en/enterprise/integrations/linear.mdx
+++ b/docs/en/enterprise/integrations/linear.mdx
@@ -13,7 +13,7 @@ Enable your agents to manage issues, projects, and development workflows through
 
 Before using the Linear integration, ensure you have:
 
-- A [CrewAI Enterprise](https://app.crewai.com) account with an active subscription
+- A [CrewAI AMP](https://app.crewai.com) account with an active subscription
 - A Linear account with appropriate workspace permissions
 - Connected your Linear account through the [Integrations page](https://app.crewai.com/crewai_plus/connectors)
 
@@ -21,7 +21,7 @@ Before using the Linear integration, ensure you have:
 
 ### 1. Connect Your Linear Account
 
-1. Navigate to [CrewAI Enterprise Integrations](https://app.crewai.com/crewai_plus/connectors)
+1. Navigate to [CrewAI AMP Integrations](https://app.crewai.com/crewai_plus/connectors)
 2. Find **Linear** in the Authentication Integrations section
 3. Click **Connect** and complete the OAuth flow
 4. Grant the necessary permissions for issue and project management
diff --git a/docs/en/enterprise/integrations/notion.mdx b/docs/en/enterprise/integrations/notion.mdx
index 76a0a6c8b..5fb1afaf0 100644
--- a/docs/en/enterprise/integrations/notion.mdx
+++ b/docs/en/enterprise/integrations/notion.mdx
@@ -13,7 +13,7 @@ Enable your agents to manage pages, databases, and content through Notion. Creat
 
 Before using the Notion integration, ensure you have:
 
-- A [CrewAI Enterprise](https://app.crewai.com) account with an active subscription
+- A [CrewAI AMP](https://app.crewai.com) account with an active subscription
 - A Notion account with appropriate workspace permissions
 - Connected your Notion account through the [Integrations page](https://app.crewai.com/crewai_plus/connectors)
 
@@ -21,7 +21,7 @@ Before using the Notion integration, ensure you have:
 
 ### 1. Connect Your Notion Account
 
-1. Navigate to [CrewAI Enterprise Integrations](https://app.crewai.com/crewai_plus/connectors)
+1. Navigate to [CrewAI AMP Integrations](https://app.crewai.com/crewai_plus/connectors)
 2. Find **Notion** in the Authentication Integrations section
 3. Click **Connect** and complete the OAuth flow
 4. Grant the necessary permissions for page and database management
diff --git a/docs/en/enterprise/integrations/salesforce.mdx b/docs/en/enterprise/integrations/salesforce.mdx
index 6e3fb3e7b..38fec82d2 100644
--- a/docs/en/enterprise/integrations/salesforce.mdx
+++ b/docs/en/enterprise/integrations/salesforce.mdx
@@ -13,7 +13,7 @@ Enable your agents to manage customer relationships, sales processes, and data t
 
 Before using the Salesforce integration, ensure you have:
 
-- A [CrewAI Enterprise](https://app.crewai.com) account with an active subscription
+- A [CrewAI AMP](https://app.crewai.com) account with an active subscription
 - A Salesforce account with appropriate permissions
 - Connected your Salesforce account through the [Integrations page](https://app.crewai.com/integrations)
 
diff --git a/docs/en/enterprise/integrations/shopify.mdx b/docs/en/enterprise/integrations/shopify.mdx
index 7d68c99a7..671570bfe 100644
--- a/docs/en/enterprise/integrations/shopify.mdx
+++ b/docs/en/enterprise/integrations/shopify.mdx
@@ -13,7 +13,7 @@ Enable your agents to manage e-commerce operations through Shopify. Handle custo
 
 Before using the Shopify integration, ensure you have:
 
-- A [CrewAI Enterprise](https://app.crewai.com) account with an active subscription
+- A [CrewAI AMP](https://app.crewai.com) account with an active subscription
 - A Shopify store with appropriate admin permissions
 - Connected your Shopify store through the [Integrations page](https://app.crewai.com/integrations)
 
diff --git a/docs/en/enterprise/integrations/slack.mdx b/docs/en/enterprise/integrations/slack.mdx
index 78960f11d..ee1a17fc2 100644
--- a/docs/en/enterprise/integrations/slack.mdx
+++ b/docs/en/enterprise/integrations/slack.mdx
@@ -13,7 +13,7 @@ Enable your agents to manage team communication through Slack. Send messages, se
 
 Before using the Slack integration, ensure you have:
 
-- A [CrewAI Enterprise](https://app.crewai.com) account with an active subscription
+- A [CrewAI AMP](https://app.crewai.com) account with an active subscription
 - A Slack workspace with appropriate permissions
 - Connected your Slack workspace through the [Integrations page](https://app.crewai.com/integrations)
 
diff --git a/docs/en/enterprise/integrations/stripe.mdx b/docs/en/enterprise/integrations/stripe.mdx
index d5b75a61a..cd25f1c5c 100644
--- a/docs/en/enterprise/integrations/stripe.mdx
+++ b/docs/en/enterprise/integrations/stripe.mdx
@@ -13,7 +13,7 @@ Enable your agents to manage payments, subscriptions, and customer billing throu
 
 Before using the Stripe integration, ensure you have:
 
-- A [CrewAI Enterprise](https://app.crewai.com) account with an active subscription
+- A [CrewAI AMP](https://app.crewai.com) account with an active subscription
 - A Stripe account with appropriate API permissions
 - Connected your Stripe account through the [Integrations page](https://app.crewai.com/integrations)
 
diff --git a/docs/en/enterprise/integrations/zendesk.mdx b/docs/en/enterprise/integrations/zendesk.mdx
index eea4edfce..b7b025679 100644
--- a/docs/en/enterprise/integrations/zendesk.mdx
+++ b/docs/en/enterprise/integrations/zendesk.mdx
@@ -13,7 +13,7 @@ Enable your agents to manage customer support operations through Zendesk. Create
 
 Before using the Zendesk integration, ensure you have:
 
-- A [CrewAI Enterprise](https://app.crewai.com) account with an active subscription
+- A [CrewAI AMP](https://app.crewai.com) account with an active subscription
 - A Zendesk account with appropriate API permissions
 - Connected your Zendesk account through the [Integrations page](https://app.crewai.com/integrations)
 
diff --git a/docs/en/enterprise/introduction.mdx b/docs/en/enterprise/introduction.mdx
index 7fb894cc1..8ff205071 100644
--- a/docs/en/enterprise/introduction.mdx
+++ b/docs/en/enterprise/introduction.mdx
@@ -1,5 +1,5 @@
 ---
-title: "CrewAI Enterprise"
+title: "CrewAI AMP"
 description: "Deploy, monitor, and scale your AI agent workflows"
 icon: "globe"
 mode: "wide"
@@ -7,13 +7,13 @@ mode: "wide"
 
 ## Introduction
 
-CrewAI Enterprise provides a platform for deploying, monitoring, and scaling your crews and agents in a production environment.
+CrewAI AMP provides a platform for deploying, monitoring, and scaling your crews and agents in a production environment.
 
 <Frame>
-  <img src="/images/enterprise/crewai-enterprise-dashboard.png" alt="CrewAI Enterprise Dashboard" />
+  <img src="/images/enterprise/crewai-enterprise-dashboard.png" alt="CrewAI AMP Dashboard" />
 </Frame>
 
-CrewAI Enterprise extends the power of the open-source framework with features designed for production deployments, collaboration, and scalability. Deploy your crews to a managed infrastructure and monitor their execution in real-time.
+CrewAI AMP extends the power of the open-source framework with features designed for production deployments, collaboration, and scalability. Deploy your crews to a managed infrastructure and monitor their execution in real-time.
 
 ## Key Features
 
diff --git a/docs/en/enterprise/resources/frequently-asked-questions.mdx b/docs/en/enterprise/resources/frequently-asked-questions.mdx
index 890c11fc5..1253d7eef 100644
--- a/docs/en/enterprise/resources/frequently-asked-questions.mdx
+++ b/docs/en/enterprise/resources/frequently-asked-questions.mdx
@@ -1,6 +1,6 @@
 ---
 title: FAQs
-description: "Frequently asked questions about CrewAI Enterprise"
+description: "Frequently asked questions about CrewAI AMP"
 icon: "circle-question"
 mode: "wide"
 ---
diff --git a/docs/en/index.mdx b/docs/en/index.mdx
new file mode 100644
index 000000000..4cb870c48
--- /dev/null
+++ b/docs/en/index.mdx
@@ -0,0 +1,107 @@
+---
+title: "CrewAI Documentation"
+description: "Build collaborative AI agents, crews, and flows — production ready from day one."
+icon: "house"
+mode: "wide"
+---
+
+import { SearchBar } from "@mintlify/components";
+
+<div
+  style={{
+    display: 'flex',
+    flexDirection: 'column',
+    alignItems: 'center',
+    gap: 20,
+    textAlign: 'center',
+    padding: '48px 24px',
+    borderRadius: 16,
+    background: 'linear-gradient(180deg, rgba(235,102,88,0.12) 0%, rgba(201,76,60,0.08) 100%)',
+    border: '1px solid rgba(235,102,88,0.18)'
+  }}
+>
+  <img src="/images/crew_only_logo.png" alt="CrewAI" width="250" height="100" />
+  <div style={{ maxWidth: 720 }}>
+    <h1 style={{ marginBottom: 12 }}>Ship multi‑agent systems with confidence</h1>
+    <p style={{ color: 'var(--mint-text-2)' }}>
+      Design agents, orchestrate crews, and automate flows with guardrails, memory, knowledge, and observability baked in.
+    </p>
+  </div>
+
+  <div style={{ display: 'flex', flexWrap: 'wrap', gap: 12, justifyContent: 'center' }}>
+    <a className="button button-primary" href="/en/quickstart">Get started</a>
+    <a className="button" href="/en/changelog">View changelog</a>
+    <a className="button" href="/en/api-reference/introduction">API Reference</a>
+  </div>
+
+</div>
+
+<div style={{ marginTop: 32 }} />
+
+## Get started
+
+<CardGroup cols={3}>
+  <Card title="Introduction" href="/en/introduction" icon="sparkles">
+    Overview of CrewAI concepts, architecture, and what you can build with agents, crews, and flows.
+  </Card>
+  <Card title="Installation" href="/en/installation" icon="wrench">
+    Install via `uv`, configure API keys, and set up the CLI for local development.
+  </Card>
+  <Card title="Quickstart" href="/en/quickstart" icon="rocket">
+    Spin up your first crew in minutes. Learn the core runtime, project layout, and dev loop.
+  </Card>
+</CardGroup>
+
+## Build the basics
+
+<CardGroup cols={3}>
+  <Card title="Agents" href="/en/concepts/agents" icon="users">
+    Compose agents with tools, memory, knowledge, and structured outputs using Pydantic. Includes templates and best practices.
+  </Card>
+  <Card title="Flows" href="/en/concepts/flows" icon="arrow-progress">
+    Orchestrate start/listen/router steps, manage state, persist execution, and resume long-running workflows.
+  </Card>
+  <Card title="Tasks & Processes" href="/en/concepts/tasks" icon="check">
+    Define sequential, hierarchical, or hybrid processes with guardrails, callbacks, and human-in-the-loop triggers.
+  </Card>
+</CardGroup>
+
+## Enterprise journey
+
+<CardGroup cols={3}>
+  <Card title="Deploy automations" href="/en/enterprise/features/automations" icon="server">
+    Manage environments, redeploy safely, and monitor live runs directly from the Enterprise console.
+  </Card>
+  <Card title="Triggers & Flows" href="/en/enterprise/guides/automation-triggers" icon="bolt">
+    Connect Gmail, Slack, Salesforce, and more. Pass trigger payloads into crews and flows automatically.
+  </Card>
+  <Card title="Team management" href="/en/enterprise/guides/team-management" icon="users-gear">
+    Invite teammates, configure RBAC, and control access to production automations.
+  </Card>
+</CardGroup>
+
+## What’s new
+
+<CardGroup cols={2}>
+  <Card title="Triggers overview" href="/en/enterprise/guides/automation-triggers" icon="sparkles">
+    Unified overview for Gmail, Drive, Outlook, Teams, OneDrive, HubSpot, and more — now with sample payloads and crews.
+  </Card>
+  <Card title="Integration tools" href="/en/tools/integration/overview" icon="plug">
+    Call existing CrewAI automations or Amazon Bedrock Agents directly from your crews using the updated integration toolkit.
+  </Card>
+</CardGroup>
+
+<Callout title="Explore real-world patterns" icon="github">
+  Browse the <a href="/en/examples/cookbooks">examples and cookbooks</a> for end-to-end reference implementations across agents, flows, and enterprise automations.
+</Callout>
+
+## Stay connected
+
+<CardGroup cols={2}>
+  <Card title="Star us on GitHub" href="https://github.com/crewAIInc/crewAI" icon="star">
+    If CrewAI helps you ship faster, give us a star and share your builds with the community.
+  </Card>
+  <Card title="Join the community" href="https://community.crewai.com" icon="comments">
+    Ask questions, showcase workflows, and request features alongside other builders.
+  </Card>
+</CardGroup>
diff --git a/docs/en/installation.mdx b/docs/en/installation.mdx
index 26b5d1dd6..96f04d853 100644
--- a/docs/en/installation.mdx
+++ b/docs/en/installation.mdx
@@ -167,7 +167,7 @@ We recommend using the `YAML` template scaffolding for a structured approach to
 <Note type="info">
 For teams and organizations, CrewAI offers enterprise deployment options that eliminate setup complexity:
 
-### CrewAI Enterprise (SaaS)
+### CrewAI AMP (SaaS)
 - Zero installation required - just sign up for free at [app.crewai.com](https://app.crewai.com)
 - Automatic updates and maintenance
 - Managed infrastructure and scaling
diff --git a/docs/en/learn/human-input-on-execution.mdx b/docs/en/learn/human-input-on-execution.mdx
index b8b19f013..c920b07cd 100644
--- a/docs/en/learn/human-input-on-execution.mdx
+++ b/docs/en/learn/human-input-on-execution.mdx
@@ -1,7 +1,7 @@
 ---
 title: Human Input on Execution
 description: Integrating CrewAI with human input during execution in complex decision-making processes and leveraging the full capabilities of the agent's attributes and tools.
-icon: user-check
+icon: user-plus
 mode: "wide"
 ---
 
diff --git a/docs/en/learn/llm-selection-guide.mdx b/docs/en/learn/llm-selection-guide.mdx
index 3250178fc..e58d880a3 100644
--- a/docs/en/learn/llm-selection-guide.mdx
+++ b/docs/en/learn/llm-selection-guide.mdx
@@ -394,7 +394,7 @@ Rather than repeating the strategic framework, here's a tactical checklist for i
   
   <Step title="Validate with Enterprise Testing" icon="test-tube">
     **Once you deploy your agents to production:**
-    - Use [CrewAI Enterprise platform](https://app.crewai.com) to A/B test your model selections
+    - Use [CrewAI AMP platform](https://app.crewai.com) to A/B test your model selections
     - Run multiple iterations with real inputs to measure consistency and performance
     - Compare cost vs. performance across your optimized setup
     - Share results with your team for collaborative decision-making
@@ -541,7 +541,7 @@ Focus on understanding your requirements first, then select models that best mat
 
 ### Enterprise-Grade Model Validation
 
-For teams serious about optimizing their LLM selection, the **CrewAI Enterprise platform** provides sophisticated testing capabilities that go far beyond basic CLI testing. The platform enables comprehensive model evaluation that helps you make data-driven decisions about your LLM strategy.
+For teams serious about optimizing their LLM selection, the **CrewAI AMP platform** provides sophisticated testing capabilities that go far beyond basic CLI testing. The platform enables comprehensive model evaluation that helps you make data-driven decisions about your LLM strategy.
 
 <Frame>
   ![Enterprise Testing Interface](/images/enterprise/enterprise-testing.png)
diff --git a/docs/en/quickstart.mdx b/docs/en/quickstart.mdx
index 75f6264e8..910a3dbaf 100644
--- a/docs/en/quickstart.mdx
+++ b/docs/en/quickstart.mdx
@@ -209,9 +209,9 @@ Follow the steps below to get Crewing! 🚣‍♂️
   </Step>
 
   <Step title="Enterprise Alternative: Create in Crew Studio">
-  For CrewAI Enterprise users, you can create the same crew without writing code:
+  For CrewAI AMP users, you can create the same crew without writing code:
 
-  1. Log in to your CrewAI Enterprise account (create a free account at [app.crewai.com](https://app.crewai.com))
+  1. Log in to your CrewAI AMP account (create a free account at [app.crewai.com](https://app.crewai.com))
   2. Open Crew Studio
   3. Type what is the automation you're trying to build
   4. Create your tasks visually and connect them in sequence
@@ -219,8 +219,8 @@ Follow the steps below to get Crewing! 🚣‍♂️
 
   ![Crew Studio Quickstart](/images/enterprise/crew-studio-interface.png)
 
-  <Card title="Try CrewAI Enterprise" icon="rocket" href="https://app.crewai.com">
-    Start your free account at CrewAI Enterprise
+  <Card title="Try CrewAI AMP" icon="rocket" href="https://app.crewai.com">
+    Start your free account at CrewAI AMP
   </Card>
   </Step>
   <Step title="View your final report">
@@ -340,9 +340,9 @@ email_summarizer_task:
 
 ## Deploying Your Crew
 
-The easiest way to deploy your crew to production is through [CrewAI Enterprise](http://app.crewai.com).
+The easiest way to deploy your crew to production is through [CrewAI AMP](http://app.crewai.com).
 
-Watch this video tutorial for a step-by-step demonstration of deploying your crew to [CrewAI Enterprise](http://app.crewai.com) using the CLI.
+Watch this video tutorial for a step-by-step demonstration of deploying your crew to [CrewAI AMP](http://app.crewai.com) using the CLI.
 
 <iframe
   className="w-full aspect-video rounded-xl"
@@ -359,7 +359,7 @@ Watch this video tutorial for a step-by-step demonstration of deploying your cre
     icon="rocket"
     href="http://app.crewai.com"
   >
-    Get started with CrewAI Enterprise and deploy your crew in a production environment with just a few clicks.
+    Get started with CrewAI AMP and deploy your crew in a production environment with just a few clicks.
   </Card>
   <Card
     title="Join the Community"
diff --git a/docs/enterprise-api.base.yaml b/docs/enterprise-api.base.yaml
index 457ea22bb..7d09c2f06 100644
--- a/docs/enterprise-api.base.yaml
+++ b/docs/enterprise-api.base.yaml
@@ -1,12 +1,12 @@
 openapi: 3.0.3
 info:
-  title: CrewAI Enterprise API
+  title: CrewAI AMP API
   description: |
-    REST API for interacting with your deployed CrewAI crews on CrewAI Enterprise.
+    REST API for interacting with your deployed CrewAI crews on CrewAI AMP.
     
     ## Getting Started
     
-    1. **Find your crew URL**: Get your unique crew URL from the CrewAI Enterprise dashboard
+    1. **Find your crew URL**: Get your unique crew URL from the CrewAI AMP dashboard
     2. **Copy examples**: Use the code examples from each endpoint page as templates
     3. **Replace placeholders**: Update URLs and tokens with your actual values
     4. **Test with your tools**: Use cURL, Postman, or your preferred API client
@@ -18,7 +18,7 @@ info:
     - **Bearer Token**: Organization-level token for full crew operations
     - **User Bearer Token**: User-scoped token for individual access with limited permissions
     
-    You can find your bearer tokens in the Status tab of your crew's detail page in the CrewAI Enterprise dashboard.
+    You can find your bearer tokens in the Status tab of your crew's detail page in the CrewAI AMP dashboard.
     
     ## Reference Documentation
     
@@ -43,7 +43,7 @@ info:
     url: https://crewai.com
 servers:
   - url: https://your-actual-crew-name.crewai.com
-    description: Replace with your actual deployed crew URL from the CrewAI Enterprise dashboard
+    description: Replace with your actual deployed crew URL from the CrewAI AMP dashboard
   - url: https://my-travel-crew.crewai.com
     description: Example travel planning crew (replace with your URL)
   - url: https://content-creation-crew.crewai.com
@@ -284,7 +284,7 @@ components:
       description: |
         **📋 Reference Documentation** - *The tokens shown in examples are placeholders for reference only.*
         
-        Use your actual Bearer Token or User Bearer Token from the CrewAI Enterprise dashboard for real API calls.
+        Use your actual Bearer Token or User Bearer Token from the CrewAI AMP dashboard for real API calls.
         
         **Bearer Token**: Organization-level access for full crew operations
         **User Bearer Token**: User-scoped access with limited permissions
diff --git a/docs/enterprise-api.en.yaml b/docs/enterprise-api.en.yaml
index 645601eae..6c16c3688 100644
--- a/docs/enterprise-api.en.yaml
+++ b/docs/enterprise-api.en.yaml
@@ -1,12 +1,12 @@
 openapi: 3.0.3
 info:
-  title: CrewAI Enterprise API
+  title: CrewAI AMP API
   description: |
-    REST API for interacting with your deployed CrewAI crews on CrewAI Enterprise.
+    REST API for interacting with your deployed CrewAI crews on CrewAI AMP.
     
     ## Getting Started
     
-    1. **Find your crew URL**: Get your unique crew URL from the CrewAI Enterprise dashboard
+    1. **Find your crew URL**: Get your unique crew URL from the CrewAI AMP dashboard
     2. **Copy examples**: Use the code examples from each endpoint page as templates
     3. **Replace placeholders**: Update URLs and tokens with your actual values
     4. **Test with your tools**: Use cURL, Postman, or your preferred API client
@@ -18,7 +18,7 @@ info:
     - **Bearer Token**: Organization-level token for full crew operations
     - **User Bearer Token**: User-scoped token for individual access with limited permissions
     
-    You can find your bearer tokens in the Status tab of your crew's detail page in the CrewAI Enterprise dashboard.
+    You can find your bearer tokens in the Status tab of your crew's detail page in the CrewAI AMP dashboard.
     
     ## Reference Documentation
     
@@ -43,7 +43,7 @@ info:
     url: https://crewai.com
 servers:
   - url: https://your-actual-crew-name.crewai.com
-    description: Replace with your actual deployed crew URL from the CrewAI Enterprise dashboard
+    description: Replace with your actual deployed crew URL from the CrewAI AMP dashboard
   - url: https://my-travel-crew.crewai.com
     description: Example travel planning crew (replace with your URL)
   - url: https://content-creation-crew.crewai.com
@@ -284,7 +284,7 @@ components:
       description: |
         **📋 Reference Documentation** - *The tokens shown in examples are placeholders for reference only.*
         
-        Use your actual Bearer Token or User Bearer Token from the CrewAI Enterprise dashboard for real API calls.
+        Use your actual Bearer Token or User Bearer Token from the CrewAI AMP dashboard for real API calls.
         
         **Bearer Token**: Organization-level access for full crew operations
         **User Bearer Token**: User-scoped access with limited permissions
diff --git a/docs/enterprise-api.ko.yaml b/docs/enterprise-api.ko.yaml
index da0b6c23f..98cf31a8a 100644
--- a/docs/enterprise-api.ko.yaml
+++ b/docs/enterprise-api.ko.yaml
@@ -2,7 +2,7 @@ openapi: 3.0.3
 info:
   title: CrewAI 엔터프라이즈 API
   description: |
-    CrewAI Enterprise에 배포된 crew와 상호작용하기 위한 REST API입니다.
+    CrewAI AMP에 배포된 crew와 상호작용하기 위한 REST API입니다.
     
     ## 시작하기
     1. **Crew URL 확인**: 대시보드에서 고유한 crew URL을 확인하세요
diff --git a/docs/enterprise-api.pt-BR.yaml b/docs/enterprise-api.pt-BR.yaml
index 77c9e4644..d5a8e6cf5 100644
--- a/docs/enterprise-api.pt-BR.yaml
+++ b/docs/enterprise-api.pt-BR.yaml
@@ -1,12 +1,12 @@
 openapi: 3.0.3
 info:
-  title: CrewAI Enterprise API
+  title: CrewAI AMP API
   description: |
-    REST API para interagir com suas crews implantadas no CrewAI Enterprise.
+    REST API para interagir com suas crews implantadas no CrewAI AMP.
     
     ## Introdução
     
-    1. **Encontre a URL da sua crew**: Obtenha sua URL única no painel do CrewAI Enterprise
+    1. **Encontre a URL da sua crew**: Obtenha sua URL única no painel do CrewAI AMP
     2. **Copie os exemplos**: Use os exemplos de cada endpoint como modelo
     3. **Substitua os placeholders**: Atualize URLs e tokens com seus valores reais
     4. **Teste com suas ferramentas**: Use cURL, Postman ou seu cliente preferido
@@ -18,7 +18,7 @@ info:
     - **Bearer Token**: Token em nível de organização para operações completas
     - **User Bearer Token**: Token com escopo de usuário com permissões limitadas
     
-    Você encontra os tokens na aba Status da sua crew no painel do CrewAI Enterprise.
+    Você encontra os tokens na aba Status da sua crew no painel do CrewAI AMP.
     
     ## Documentação de Referência
     
@@ -43,7 +43,7 @@ info:
     url: https://crewai.com
 servers:
   - url: https://your-actual-crew-name.crewai.com
-    description: Substitua pela URL real da sua crew no painel do CrewAI Enterprise
+    description: Substitua pela URL real da sua crew no painel do CrewAI AMP
 security:
   - BearerAuth: []
 paths:
@@ -163,7 +163,7 @@ components:
       scheme: bearer
       description: |
         **📋 Referência** - *Os tokens mostrados são apenas exemplos.*
-        Use seus tokens reais do painel do CrewAI Enterprise.
+        Use seus tokens reais do painel do CrewAI AMP.
 
   schemas:
     ExecutionRunning:
diff --git a/docs/ko/api-reference/introduction.mdx b/docs/ko/api-reference/introduction.mdx
index d53fad853..fb7e747b0 100644
--- a/docs/ko/api-reference/introduction.mdx
+++ b/docs/ko/api-reference/introduction.mdx
@@ -1,6 +1,6 @@
 ---
 title: "소개"
-description: "CrewAI Enterprise REST API에 대한 완벽한 참고 자료"
+description: "CrewAI AMP REST API에 대한 완벽한 참고 자료"
 icon: "code"
 mode: "wide"
 ---
@@ -13,7 +13,7 @@ CrewAI 엔터프라이즈 API 참고 자료에 오신 것을 환영합니다. 
 
 <Steps>
   <Step title="API 자격 증명 받기">
-    CrewAI Enterprise 대시보드에서 자신의 crew 상세 페이지로 이동하여 Status 탭에서 Bearer Token을 복사하세요.
+    CrewAI AMP 대시보드에서 자신의 crew 상세 페이지로 이동하여 Status 탭에서 Bearer Token을 복사하세요.
   </Step>
   
   <Step title="필수 입력값 확인하기">
@@ -46,7 +46,7 @@ curl -H "Authorization: Bearer YOUR_CREW_TOKEN" \
 | **User Bearer Token** | 사용자 범위 접근 | 제한된 권한, 사용자별 작업에 적합 |
 
 <Tip>
-두 토큰 유형 모두 CrewAI Enterprise 대시보드의 crew 상세 페이지 Status 탭에서 확인할 수 있습니다.
+두 토큰 유형 모두 CrewAI AMP 대시보드의 crew 상세 페이지 Status 탭에서 확인할 수 있습니다.
 </Tip>
 
 ## 기본 URL
@@ -82,7 +82,7 @@ API는 표준 HTTP 상태 코드를 사용합니다:
 ## 인터랙티브 테스트
 
 <Info>
-**왜 "전송" 버튼이 없나요?** 각 CrewAI Enterprise 사용자는 고유한 crew URL을 가지므로, 혼동을 피하기 위해 인터랙티브 플레이그라운드 대신 **참조 모드**를 사용합니다. 이를 통해 비작동 전송 버튼 없이 요청이 어떻게 생겼는지 정확히 보여줍니다.
+**왜 "전송" 버튼이 없나요?** 각 CrewAI AMP 사용자는 고유한 crew URL을 가지므로, 혼동을 피하기 위해 인터랙티브 플레이그라운드 대신 **참조 모드**를 사용합니다. 이를 통해 비작동 전송 버튼 없이 요청이 어떻게 생겼는지 정확히 보여줍니다.
 </Info>
 
 각 엔드포인트 페이지에서는 다음을 확인할 수 있습니다:
diff --git a/docs/ko/changelog.mdx b/docs/ko/changelog.mdx
index 565c2dd83..82fdab475 100644
--- a/docs/ko/changelog.mdx
+++ b/docs/ko/changelog.mdx
@@ -4,6 +4,84 @@ description: "CrewAI의 제품 업데이트, 개선 사항 및 버그 수정"
 icon: "clock"
 mode: "wide"
 ---
+<Update label="2025년 9월 30일">
+  ## v1.0.0a1
+
+  [GitHub 릴리스 보기](https://github.com/crewAIInc/crewAI/releases/tag/1.0.0a1)
+
+  ## 변경 사항
+
+  ### 핵심 개선 및 수정
+  - 에이전트 설정에서 `actions` 속성 권한 처리를 수정했습니다
+  - 새로운 모노레포 구조에 맞춰 CI 워크플로와 릴리스 프로세스를 업데이트했습니다
+  - Python 지원 버전을 3.13으로 올리고 워크스페이스 메타데이터를 갱신했습니다
+
+  ### 새로운 기능 및 향상
+  - 에이전트에 `apps`와 `actions` 속성을 추가하여 런타임 제어를 강화했습니다
+  - `crewai-tools` 저장소를 메인 워크스페이스에 통합하여 모노레포 구조를 도입했습니다
+  - 모든 패키지 버전을 1.0.0a1로 올려 알파 마일스톤을 표시했습니다
+
+  ### 정리 및 인프라
+  - 버전 고정과 배포 전략을 포함한 새로운 CI 파이프라인을 구축했습니다
+  - 다중 패키지 관리를 지원하도록 코드베이스를 통합했습니다
+
+</Update>
+
+<Update label="2025년 9월 26일">
+  ## v0.201.1
+
+  [GitHub 릴리스 보기](https://github.com/crewAIInc/crewAI/releases/tag/0.201.1)
+
+  ## 변경 사항
+
+  ### 핵심 개선 및 수정
+  - Watson 임베딩 프로바이더를 `watsonx`로 변경하고 환경 변수 접두사를 업데이트했습니다
+  - `watsonx`와 `voyageai` 프로바이더에 대한 ChromaDB 호환성을 추가했습니다
+
+  ### 정리 및 사용 중단
+  - 모든 임베딩 프로바이더의 환경 변수 접두사를 표준화했습니다
+  - CrewAI 버전을 0.201.1로 올리고 내부 의존성을 갱신했습니다
+
+</Update>
+
+<Update label="2025년 9월 24일">
+  ## v0.201.0
+
+  [GitHub 릴리스 보기](https://github.com/crewAIInc/crewAI/releases/tag/0.201.0)
+
+  ## 변경 사항
+
+  ### 핵심 개선 및 수정
+  - `_create_reasoning_plan`의 `ready` 매개변수를 선택 사항으로 변경했습니다
+  - 임베더 설정의 중첩된 구성 형식을 바로잡았습니다
+  - 토큰 한도 오류를 방지하기 위해 `batch_size` 매개변수를 지원합니다
+  - Quickstart 문서의 디렉터리 이름을 수정했습니다
+  - 테스트 시간 캐시 및 이벤트 내보내기 문제를 해결했습니다
+  - 크루 설정에 대한 폴백 로직을 추가했습니다
+
+  ### 새로운 기능 및 향상
+  - 플랫폼 컨텍스트를 스레드 안전하게 관리하도록 개선했습니다
+  - CLI에서 `uv`를 바로 실행할 수 있도록 `crewai uv` 래퍼 명령을 추가했습니다
+  - 관찰 워크플로에서 트레이스를 실패 상태로 표시할 수 있도록 지원했습니다
+  - 사용자 지정 임베딩 타입과 프로바이더 마이그레이션을 지원했습니다
+  - ChromaDB를 v1.1.0으로 업그레이드하고 호환성 및 타입 개선을 적용했습니다
+  - Pydantic 호환 임포트 검증을 도입하고 의존성 그룹을 재구성했습니다
+
+  ### 문서 및 가이드
+  - 최근 릴리스(0.193.x)의 변경 로그를 업데이트했습니다
+  - LLM Guardrail 이벤트 소스 메타데이터 지원을 문서화했습니다
+  - 폴백 동작과 구성 가시성에 대한 가이드를 추가했습니다
+
+  ### 정리 및 사용 중단
+  - 여러 모듈에서 Ruff 및 MyPy 문제를 해결했습니다
+  - 타입 주석을 개선하고 유틸리티를 통합했습니다
+  - Pydantic 호환 임포트를 사용하도록 기존 유틸리티를 대체했습니다
+
+  ### 기여자
+  - 신규 기여자: @qizwiz (첫 커밋)
+
+</Update>
+
 
 <Update label="2025년 9월 20일">
   ## v0.193.2
diff --git a/docs/ko/concepts/agents.mdx b/docs/ko/concepts/agents.mdx
index cad0aec1e..e10d98bde 100644
--- a/docs/ko/concepts/agents.mdx
+++ b/docs/ko/concepts/agents.mdx
@@ -20,7 +20,7 @@ CrewAI 프레임워크에서 `Agent`는 다음과 같은 역할을 수행하는
 </Tip>
 
 <Note type="info" title="엔터프라이즈 확장: 시각적 에이전트 빌더">
-CrewAI Enterprise에는 코드를 작성하지 않고도 에이전트 생성 및 구성을 간편하게 할 수 있는 시각적 에이전트 빌더가 포함되어 있습니다. 에이전트를 시각적으로 설계하고 실시간으로 테스트하세요.
+CrewAI AMP에는 코드를 작성하지 않고도 에이전트 생성 및 구성을 간편하게 할 수 있는 시각적 에이전트 빌더가 포함되어 있습니다. 에이전트를 시각적으로 설계하고 실시간으로 테스트하세요.
 
 ![Visual Agent Builder Screenshot](/images/enterprise/crew-studio-interface.png)
 
diff --git a/docs/ko/concepts/cli.mdx b/docs/ko/concepts/cli.mdx
index 7e8a3b9ea..761f7a24b 100644
--- a/docs/ko/concepts/cli.mdx
+++ b/docs/ko/concepts/cli.mdx
@@ -5,7 +5,7 @@ icon: terminal
 mode: "wide"
 ---
 
-<Warning>릴리즈 0.140.0부터 CrewAI Enterprise는 로그인 제공자 마이그레이션 프로세스를 시작했습니다. 이에 따라 CLI를 통한 인증 흐름이 업데이트되었습니다. Google을 통해 로그인하거나 2025년 7월 3일 이후에 계정을 생성한 사용자는 이전 버전의 `crewai` 라이브러리로는 로그인할 수 없습니다.</Warning>
+<Warning>릴리즈 0.140.0부터 CrewAI AMP는 로그인 제공자 마이그레이션 프로세스를 시작했습니다. 이에 따라 CLI를 통한 인증 흐름이 업데이트되었습니다. Google을 통해 로그인하거나 2025년 7월 3일 이후에 계정을 생성한 사용자는 이전 버전의 `crewai` 라이브러리로는 로그인할 수 없습니다.</Warning>
 
 ## 개요
 
@@ -186,9 +186,9 @@ def crew(self) -> Crew:
 
 ### 10. 배포
 
-crew 또는 flow를 [CrewAI Enterprise](https://app.crewai.com)에 배포하세요.
+crew 또는 flow를 [CrewAI AMP](https://app.crewai.com)에 배포하세요.
 
-- **인증**: CrewAI Enterprise에 배포하려면 인증이 필요합니다.
+- **인증**: CrewAI AMP에 배포하려면 인증이 필요합니다.
     아래 명령어로 로그인하거나 계정을 생성할 수 있습니다:
     ```shell Terminal
     crewai login
@@ -203,7 +203,7 @@ crew 또는 flow를 [CrewAI Enterprise](https://app.crewai.com)에 배포하세
 
 ### 11. 조직 관리
 
-CrewAI Enterprise 조직을 관리합니다.
+CrewAI AMP 조직을 관리합니다.
 
 ```shell Terminal
 crewai org [COMMAND] [OPTIONS]
@@ -227,17 +227,17 @@ crewai org switch <organization_id>
 ```
 
 <Note>
-이러한 조직 관리 명령어를 사용하려면 CrewAI Enterprise에 인증되어 있어야 합니다.
+이러한 조직 관리 명령어를 사용하려면 CrewAI AMP에 인증되어 있어야 합니다.
 </Note>
 
 - **배포 생성** (계속):
     - 배포를 해당 원격 GitHub 저장소에 연결합니다 (일반적으로 자동으로 감지됩니다).
 
-- **Crew 배포**: 인증이 완료되면 crew 또는 flow를 CrewAI Enterprise에 배포할 수 있습니다.
+- **Crew 배포**: 인증이 완료되면 crew 또는 flow를 CrewAI AMP에 배포할 수 있습니다.
     ```shell Terminal
     crewai deploy push
     ```
-    - CrewAI Enterprise 플랫폼에서 배포 프로세스를 시작합니다.
+    - CrewAI AMP 플랫폼에서 배포 프로세스를 시작합니다.
     - 성공적으로 시작되면, Deployment created successfully! 메시지와 함께 Deployment Name 및 고유한 Deployment ID(UUID)가 출력됩니다.
 
 - **배포 상태**: 배포 상태를 확인하려면 다음을 사용합니다:
@@ -262,7 +262,7 @@ crewai org switch <organization_id>
     ```shell Terminal
     crewai deploy remove
     ```
-    이 명령은 CrewAI Enterprise 플랫폼에서 배포를 삭제합니다.
+    이 명령은 CrewAI AMP 플랫폼에서 배포를 삭제합니다.
 
 - **도움말 명령어**: CLI에 대한 도움말을 보려면 다음을 사용합니다:
     ```shell Terminal
@@ -270,7 +270,7 @@ crewai org switch <organization_id>
     ```
     이 명령은 CrewAI Deploy CLI에 대한 도움말 메시지를 표시합니다.
 
-CLI를 사용하여 [CrewAI Enterprise](http://app.crewai.com)에 crew를 배포하는 단계별 시연은 아래 비디오 튜토리얼을 참조하십시오.
+CLI를 사용하여 [CrewAI AMP](http://app.crewai.com)에 crew를 배포하는 단계별 시연은 아래 비디오 튜토리얼을 참조하십시오.
 
 <iframe
   className="w-full aspect-video rounded-xl"
@@ -336,7 +336,7 @@ crewai config reset
 
 #### 사용 가능한 구성 파라미터
 
-- `enterprise_base_url`: CrewAI Enterprise 인스턴스의 기본 URL
+- `enterprise_base_url`: CrewAI AMP 인스턴스의 기본 URL
 - `oauth2_provider`: 인증에 사용되는 OAuth2 공급자 (예: workos, okta, auth0)
 - `oauth2_audience`: OAuth2 audience 값으로, 일반적으로 대상 API 또는 리소스를 식별하는 데 사용됨
 - `oauth2_client_id`: 인증 요청 시 사용되는 공급자가 발급한 OAuth2 클라이언트 ID
@@ -353,7 +353,7 @@ crewai config list
 
 | 설정                 | 값                      | 설명                                                                 |
 | :------------------- | :---------------------- | :------------------------------------------------------------------- |
-| enterprise_base_url  | https://app.crewai.com | CrewAI Enterprise 인스턴스의 기본 URL                                |
+| enterprise_base_url  | https://app.crewai.com | CrewAI AMP 인스턴스의 기본 URL                                |
 | org_name             | Not set                 | 현재 활성화된 조직의 이름                                            |
 | org_uuid             | Not set                 | 현재 활성화된 조직의 UUID                                            |
 | oauth2_provider      | workos                  | 인증에 사용되는 OAuth2 제공자 (예: workos, okta, auth0)              |
diff --git a/docs/ko/concepts/event-listener.mdx b/docs/ko/concepts/event-listener.mdx
index 6dc870e2c..c6283b429 100644
--- a/docs/ko/concepts/event-listener.mdx
+++ b/docs/ko/concepts/event-listener.mdx
@@ -20,7 +20,7 @@ CrewAI는 실행 수명 주기 전반에 걸쳐 이벤트를 발생시키는 이
 CrewAI에서 특정 동작(예: Crew가 실행을 시작하거나 Agent가 task를 완료하거나 tool이 사용될 때)이 발생하면, 시스템은 해당 이벤트를 발생시킵니다. 이러한 이벤트에 대한 핸들러를 등록하여 해당 이벤트가 발생할 때 커스텀 코드를 실행할 수 있습니다.
 
 <Note type="info" title="Enterprise Enhancement: Prompt Tracing">
-CrewAI Enterprise는 event 시스템을 활용하여 모든 prompt, completion 및 관련 메타데이터를 추적, 저장 및 시각화하는 내장 Prompt Tracing 기능을 제공합니다. 이 기능을 통해 agent 운영에 대한 강력한 디버깅 기능과 투명성을 얻을 수 있습니다.
+CrewAI AMP는 event 시스템을 활용하여 모든 prompt, completion 및 관련 메타데이터를 추적, 저장 및 시각화하는 내장 Prompt Tracing 기능을 제공합니다. 이 기능을 통해 agent 운영에 대한 강력한 디버깅 기능과 투명성을 얻을 수 있습니다.
 
 ![Prompt Tracing Dashboard](/images/enterprise/traces-overview.png)
 
diff --git a/docs/ko/enterprise/features/integrations.mdx b/docs/ko/enterprise/features/integrations.mdx
deleted file mode 100644
index 422d724f6..000000000
--- a/docs/ko/enterprise/features/integrations.mdx
+++ /dev/null
@@ -1,180 +0,0 @@
----
-title: 통합
-description: "에이전트가 조치를 취할 수 있도록 연결된 애플리케이션입니다."
-icon: "plug"
-mode: "wide"
----
-
-## 개요
-
-에이전트가 OAuth를 지원하는 모든 공급자와 인증하고 작업을 수행할 수 있도록 지원합니다. Salesforce와 HubSpot부터 Google 및 GitHub까지, 16개 이상의 통합 서비스를 제공합니다.
-
-<Frame>
-  ![Integrations](/images/enterprise/crew_connectors.png)
-</Frame>
-
-## 지원되는 통합
-
-### **커뮤니케이션 & 협업**
-- **Gmail** - 이메일 및 임시 저장 관리
-- **Slack** - 워크스페이스 알림 및 경고
-- **Microsoft** - Office 365 및 Teams 통합
-
-### **프로젝트 관리**
-- **Jira** - 이슈 추적 및 프로젝트 관리
-- **ClickUp** - 작업 및 생산성 관리
-- **Asana** - 팀 작업 및 프로젝트 조정
-- **Notion** - 페이지 및 데이터베이스 관리
-- **Linear** - 소프트웨어 프로젝트 및 버그 추적
-- **GitHub** - 저장소 및 이슈 관리
-
-### **고객 관계 관리**
-- **Salesforce** - CRM 계정 및 기회 관리
-- **HubSpot** - 영업 파이프라인 및 연락처 관리
-- **Zendesk** - 고객 지원 티켓 관리
-
-### **비즈니스 & 금융**
-- **Stripe** - 결제 처리 및 고객 관리
-- **Shopify** - 전자상거래 스토어 및 상품 관리
-
-### **생산성 및 저장소**
-- **Google Sheets** - 스프레드시트 데이터 동기화
-- **Google Calendar** - 일정 및 스케줄 관리
-- **Box** - 파일 저장 및 문서 관리
-
-추가 기능도 곧 제공됩니다!
-
-## 사전 준비 사항
-
-Authentication Integrations를 사용하기 전에 다음이 준비되어 있는지 확인하세요:
-
-- [CrewAI Enterprise](https://app.crewai.com) 계정. 무료 체험으로 시작할 수 있습니다.
-
-## 통합 설정
-
-### 1. 계정 연결하기
-
-1. [CrewAI Enterprise](https://app.crewai.com)로 이동합니다.
-2. **Integrations** 탭으로 이동합니다 - https://app.crewai.com/crewai_plus/connectors
-3. Authentication Integrations 섹션에서 원하는 서비스의 **Connect** 버튼을 클릭합니다.
-4. OAuth 인증 과정을 완료합니다.
-5. 사용 사례에 필요한 권한을 부여합니다.
-6. 완료! [CrewAI Enterprise](https://app.crewai.com)의 **Integration** 탭에서 Enterprise Token을 받습니다.
-
-<Frame>
-  ![Integrations](/images/enterprise/enterprise_action_auth_token.png)
-</Frame>
-
-### 2. 통합 도구 설치
-
-최신 버전의 `crewai-tools` 패키지만 있으면 됩니다.
-
-```bash
-uv add crewai-tools
-```
-
-## 사용 예시
-
-### 기본 사용법
-<Tip>
-  인증한 모든 서비스가 도구로 제공됩니다. 따라서 필요한 것은 `CrewaiEnterpriseTools`를 에이전트에 추가하는 것뿐이며, 바로 사용하실 수 있습니다.
-</Tip>
-
-```python
-from crewai import Agent, Task, Crew
-from crewai_tools import CrewaiEnterpriseTools
-
-# Get enterprise tools (Gmail tool will be included)
-enterprise_tools = CrewaiEnterpriseTools(
-    enterprise_token="your_enterprise_token"
-)
-# print the tools
-print(enterprise_tools)
-
-# Create an agent with Gmail capabilities
-email_agent = Agent(
-    role="Email Manager",
-    goal="Manage and organize email communications",
-    backstory="An AI assistant specialized in email management and communication.",
-    tools=enterprise_tools
-)
-
-# Task to send an email
-email_task = Task(
-    description="Draft and send a follow-up email to john@example.com about the project update",
-    agent=email_agent,
-    expected_output="Confirmation that email was sent successfully"
-)
-
-# Run the task
-crew = Crew(
-    agents=[email_agent],
-    tasks=[email_task]
-)
-
-# Run the crew
-crew.kickoff()
-```
-
-### 필터링 도구
-
-```python
-from crewai_tools import CrewaiEnterpriseTools
-
-enterprise_tools = CrewaiEnterpriseTools(
-    actions_list=["gmail_find_email"] # only gmail_find_email tool will be available
-)
-gmail_tool = enterprise_tools["gmail_find_email"]
-
-gmail_agent = Agent(
-    role="Gmail Manager",
-    goal="Manage gmail communications and notifications",
-    backstory="An AI assistant that helps coordinate gmail communications.",
-    tools=[gmail_tool]
-)
-
-notification_task = Task(
-    description="Find the email from john@example.com",
-    agent=gmail_agent,
-    expected_output="Email found from john@example.com"
-)
-
-# Run the task
-crew = Crew(
-    agents=[slack_agent],
-    tasks=[notification_task]
-)
-```
-
-## 모범 사례
-
-### 보안
-- **최소 권한 원칙**: 에이전트의 작업에 필요한 최소한의 권한만 부여하세요
-- **정기적인 감사**: 연결된 통합 및 해당 권한을 주기적으로 검토하세요
-- **자격 증명 보안**: 자격 증명을 하드코딩하지 말고, CrewAI의 안전한 인증 플로우를 사용하세요
-
-### 필터링 도구
-배포된 crew에서 연결된 서비스의 설정 페이지에서 각 통합에 대해 사용할 수 있는 작업을 지정할 수 있습니다.
-
-<Frame>
-  ![Integrations](/images/enterprise/filtering_enterprise_action_tools.png)
-</Frame>
-
-### 다중 사용자 조직을 위한 Scoped Deployments
-crew를 배포하고 각 통합을 특정 사용자에게 범위 지정할 수 있습니다. 예를 들어, google에 연결하는 crew는 특정 사용자의 gmail 계정을 사용할 수 있습니다.
-
-<Tip>
-  이것은 통합을 특정 사용자에게 범위 지정하고자 하는 다중 사용자 조직에서 유용합니다.
-</Tip>
-
-`user_bearer_token`을 사용하여 통합을 특정 사용자에 범위 지정하면 crew가 시작될 때 사용자의 bearer token을 사용해 통합에 인증합니다. 사용자가 로그인하지 않은 경우, crew는 연결된 통합을 사용하지 않습니다. 기본 bearer token을 사용하여 crew와 함께 배포된 통합에 인증할 수 있습니다.
-
-<Frame>
-  ![Integrations](/images/enterprise/user_bearer_token.png)
-</Frame>
-
-### 도움 받기
-
-<Card title="도움이 필요하신가요?" icon="headset" href="mailto:support@crewai.com">
-  통합 설정이나 문제 해결에 대한 지원이 필요하시면 저희 지원팀에 문의하세요.
-</Card>
diff --git a/docs/ko/enterprise/features/rbac.mdx b/docs/ko/enterprise/features/rbac.mdx
index d7d7867e5..90f199921 100644
--- a/docs/ko/enterprise/features/rbac.mdx
+++ b/docs/ko/enterprise/features/rbac.mdx
@@ -7,10 +7,10 @@ mode: "wide"
 
 ## 개요
 
-CrewAI Enterprise의 RBAC는 **조직 수준 역할**과 **자동화(Automation) 수준 가시성**을 결합하여 안전하고 확장 가능한 접근 제어를 제공합니다.
+CrewAI AMP의 RBAC는 **조직 수준 역할**과 **자동화(Automation) 수준 가시성**을 결합하여 안전하고 확장 가능한 접근 제어를 제공합니다.
 
 <Frame>
-  <img src="/images/enterprise/users_and_roles.png" alt="CrewAI Enterprise RBAC 개요" />
+  <img src="/images/enterprise/users_and_roles.png" alt="CrewAI AMP RBAC 개요" />
   
 </Frame>
 
@@ -93,7 +93,7 @@ Owner는 항상 접근 가능하며, Private 모드에서는 화이트리스트
 </Tip>
 
 <Frame>
-  <img src="/images/enterprise/visibility.png" alt="CrewAI Enterprise 가시성 설정" />
+  <img src="/images/enterprise/visibility.png" alt="CrewAI AMP 가시성 설정" />
   
 </Frame>
 
diff --git a/docs/ko/enterprise/features/tool-repository.mdx b/docs/ko/enterprise/features/tool-repository.mdx
deleted file mode 100644
index d9b4db3cb..000000000
--- a/docs/ko/enterprise/features/tool-repository.mdx
+++ /dev/null
@@ -1,107 +0,0 @@
----
-title: 도구 저장소
-description: "도구 저장소를 사용하여 도구를 관리하기"
-icon: "toolbox"
-mode: "wide"
----
-
-## 개요
-
-Tool Repository는 CrewAI 도구를 위한 패키지 관리자입니다. 사용자는 CrewAI crew와 flow에 통합되는 도구를 게시, 설치 및 관리할 수 있습니다.
-
-도구는 다음과 같이 분류됩니다:
-
-- **비공개**: 조직 내에서만 접근할 수 있습니다(기본값)
-- **공개**: `--public` 플래그로 게시하면 모든 CrewAI 사용자가 접근할 수 있습니다
-
-이 저장소는 버전 관리 시스템이 아닙니다. 코드 변경 사항을 추적하고 협업을 활성화하려면 Git을 사용하십시오.
-
-## 사전 요구 사항
-
-Tool Repository를 사용하기 전에 다음이 준비되어 있어야 합니다:
-
-- [CrewAI Enterprise](https://app.crewai.com) 계정
-- [CrewAI CLI](https://docs.crewai.com/concepts/cli#cli) 설치됨
-- uv>=0.5.0 이 설치되어 있어야 합니다. [업그레이드 방법](https://docs.astral.sh/uv/getting-started/installation/#upgrading-uv)을 참고하세요.
-- [Git](https://git-scm.com) 설치 및 구성 완료
-- CrewAI Enterprise 조직에서 도구를 게시하거나 설치할 수 있는 액세스 권한
-
-## 도구 설치
-
-도구를 설치하려면:
-
-```bash
-crewai tool install <tool-name>
-```
-
-이 명령은 도구를 설치하고 `pyproject.toml`에 추가합니다.
-
-## 도구 생성 및 게시
-
-새 도구 프로젝트를 생성하려면:
-
-```bash
-crewai tool create <tool-name>
-```
-
-이 명령은 로컬에 스캐폴딩된 도구 프로젝트를 생성합니다.
-
-변경 사항을 적용한 후, Git 저장소를 초기화하고 코드를 커밋합니다:
-
-```bash
-git init
-git add .
-git commit -m "Initial version"
-```
-
-도구를 게시하려면:
-
-```bash
-crewai tool publish
-```
-
-기본적으로 도구는 비공개로 게시됩니다. 도구를 공개로 설정하려면:
-
-```bash
-crewai tool publish --public
-```
-
-도구 빌드에 대한 자세한 내용은 [나만의 도구 만들기](https://docs.crewai.com/concepts/tools#creating-your-own-tools)를 참고하세요.
-
-## 도구 업데이트
-
-공개된 도구를 업데이트하려면:
-
-1. 로컬에서 도구를 수정합니다.
-2. `pyproject.toml`에서 버전을 업데이트합니다(예: `0.1.0`에서 `0.1.1`로).
-3. 변경 사항을 커밋하고 배포합니다.
-
-```bash
-git commit -m "Update version to 0.1.1"
-crewai tool publish
-```
-
-## 도구 삭제
-
-도구를 삭제하려면:
-
-1. [CrewAI Enterprise](https://app.crewai.com)로 이동합니다.
-2. **Tools**로 이동합니다.
-3. 도구를 선택합니다.
-4. **Delete**를 클릭합니다.
-
-<Warning>
-삭제는 영구적입니다. 삭제된 도구는 복구하거나 다시 설치할 수 없습니다.
-</Warning>
-
-## 보안 점검
-
-모든 공개된 버전은 자동화된 보안 점검을 거치며, 통과한 후에만 설치할 수 있습니다.
-
-도구의 보안 점검 상태는 다음에서 확인할 수 있습니다:
-
-`CrewAI Enterprise > Tools > Your Tool > Versions`
-
-<Card title="도움이 필요하신가요?" icon="headset" href="mailto:support@crewai.com">
-  API 통합 또는 문제 해결에 대한 지원이 필요하시면 지원팀에 문의해 주세요.
-</Card>
\ No newline at end of file
diff --git a/docs/ko/enterprise/features/tools-and-integrations.mdx b/docs/ko/enterprise/features/tools-and-integrations.mdx
index 266d02714..9f0c3100a 100644
--- a/docs/ko/enterprise/features/tools-and-integrations.mdx
+++ b/docs/ko/enterprise/features/tools-and-integrations.mdx
@@ -173,10 +173,10 @@ mode: "wide"
 
   ## 내부 도구
 
-  로컬에서 도구를 만들고, CrewAI Enterprise 도구 저장소에 게시한 후, 에이전트에서 사용하세요.
+  로컬에서 도구를 만들고, CrewAI AMP 도구 저장소에 게시한 후, 에이전트에서 사용하세요.
 
   <Tip>
-  아래 명령을 실행하기 전에 CrewAI Enterprise 계정에 로그인하세요:
+  아래 명령을 실행하기 전에 CrewAI AMP 계정에 로그인하세요:
     ```bash
     crewai login
     ```
diff --git a/docs/ko/enterprise/features/traces.mdx b/docs/ko/enterprise/features/traces.mdx
index 2d91c06bd..a568b4339 100644
--- a/docs/ko/enterprise/features/traces.mdx
+++ b/docs/ko/enterprise/features/traces.mdx
@@ -11,7 +11,7 @@ Trace는 crew 실행에 대한 포괄적인 가시성을 제공하여 성능 모
 
 ## Traces란 무엇인가요?
 
-CrewAI Enterprise의 Traces는 crew의 작동 과정을 처음 입력에서 최종 출력까지 모든 측면에서 포착하는 상세 실행 기록입니다. Traces에는 다음 내용이 기록됩니다:
+CrewAI AMP의 Traces는 crew의 작동 과정을 처음 입력에서 최종 출력까지 모든 측면에서 포착하는 상세 실행 기록입니다. Traces에는 다음 내용이 기록됩니다:
 
 - Agent의 생각 및 추론
 - 작업 실행 세부 정보
@@ -28,7 +28,7 @@ CrewAI Enterprise의 Traces는 crew의 작동 과정을 처음 입력에서 최
 
 <Steps>
   <Step title="트레이스 탭으로 이동">
-    CrewAI Enterprise 대시보드에 들어가면, **트레이스**를 클릭하여 모든 실행 기록을 볼 수 있습니다.
+    CrewAI AMP 대시보드에 들어가면, **트레이스**를 클릭하여 모든 실행 기록을 볼 수 있습니다.
   </Step>
   
   <Step title="실행 선택하기">
diff --git a/docs/ko/enterprise/features/webhook-streaming.mdx b/docs/ko/enterprise/features/webhook-streaming.mdx
index 8c4e0a3b6..ce87006db 100644
--- a/docs/ko/enterprise/features/webhook-streaming.mdx
+++ b/docs/ko/enterprise/features/webhook-streaming.mdx
@@ -7,7 +7,7 @@ mode: "wide"
 
 ## 개요
 
-Enterprise Event Streaming을 사용하면 CrewAI Enterprise에 배포된 crew 및 flow에 대한 실시간 웹훅 업데이트(예: 모델 호출, 도구 사용, flow 단계)를 받을 수 있습니다.
+Enterprise Event Streaming을 사용하면 CrewAI AMP에 배포된 crew 및 flow에 대한 실시간 웹훅 업데이트(예: 모델 호출, 도구 사용, flow 단계)를 받을 수 있습니다.
 
 ## 사용법
 
diff --git a/docs/ko/enterprise/guides/automation-triggers.mdx b/docs/ko/enterprise/guides/automation-triggers.mdx
index 73e49d75b..84b31b6bf 100644
--- a/docs/ko/enterprise/guides/automation-triggers.mdx
+++ b/docs/ko/enterprise/guides/automation-triggers.mdx
@@ -1,11 +1,11 @@
 ---
 title: "트리거 개요"
-description: "CrewAI Enterprise 트리거의 동작 방식과 관리 방법, 그리고 통합별 플레이북을 한눈에 확인하세요"
+description: "CrewAI AMP 트리거의 동작 방식과 관리 방법, 그리고 통합별 플레이북을 한눈에 확인하세요"
 icon: "bolt"
 mode: "wide"
 ---
 
-CrewAI Enterprise 트리거는 팀이 이미 사용하고 있는 도구의 실시간 이벤트와 자동화를 연결합니다. 폴링이나 수동 실행 대신, 트리거는 새로운 이메일, 캘린더 업데이트, CRM 상태 변화 등을 감지하여 지정한 크루 또는 플로우를 즉시 실행합니다.
+CrewAI AMP 트리거는 팀이 이미 사용하고 있는 도구의 실시간 이벤트와 자동화를 연결합니다. 폴링이나 수동 실행 대신, 트리거는 새로운 이메일, 캘린더 업데이트, CRM 상태 변화 등을 감지하여 지정한 크루 또는 플로우를 즉시 실행합니다.
 
 <iframe
   className="w-full aspect-video rounded-xl"
@@ -202,6 +202,6 @@ def delegate_to_crew(self, crewai_trigger_payload: dict = None):
 
 <Callout icon="github" title="예제 저장소">
   <a href="https://github.com/crewAIInc/crewai-enterprise-trigger-examples">
-    CrewAI Enterprise Trigger Examples
+    CrewAI AMP Trigger Examples
   </a>
 </Callout>
diff --git a/docs/ko/enterprise/guides/azure-openai-setup.mdx b/docs/ko/enterprise/guides/azure-openai-setup.mdx
index 50dbfe74e..07731c119 100644
--- a/docs/ko/enterprise/guides/azure-openai-setup.mdx
+++ b/docs/ko/enterprise/guides/azure-openai-setup.mdx
@@ -19,8 +19,8 @@ mode: "wide"
             </Frame>
     </Step>
 
-    <Step title="CrewAI Enterprise 연결 구성">
-        4. 다른 탭에서 `CrewAI Enterprise > LLM Connections`를 엽니다. LLM Connection에 이름을 지정하고, 공급자로 Azure를 선택한 다음, Azure에서 선택한 것과 동일한 모델을 선택하세요.
+    <Step title="CrewAI AMP 연결 구성">
+        4. 다른 탭에서 `CrewAI AMP > LLM Connections`를 엽니다. LLM Connection에 이름을 지정하고, 공급자로 Azure를 선택한 다음, Azure에서 선택한 것과 동일한 모델을 선택하세요.
         5. 같은 페이지에서 3단계에서 가져온 환경 변수를 추가하세요:
             - 하나는 `AZURE_DEPLOYMENT_TARGET_URL` (Target URI 사용)로 명명합니다. URL은 다음과 같이 표시됩니다: https://your-deployment.openai.azure.com/openai/deployments/gpt-4o/chat/completions?api-version=2024-08-01-preview
             - 다른 하나는 `AZURE_API_KEY` (Key 사용)로 명명합니다.
@@ -28,7 +28,7 @@ mode: "wide"
     </Step>
 
     <Step title="기본 구성 설정">
-        7. `CrewAI Enterprise > Settings > Defaults > Crew Studio LLM Settings`에서 새 LLM Connection과 모델을 기본값으로 설정합니다.
+        7. `CrewAI AMP > Settings > Defaults > Crew Studio LLM Settings`에서 새 LLM Connection과 모델을 기본값으로 설정합니다.
     </Step>
 
     <Step title="네트워크 액세스 구성">
diff --git a/docs/ko/enterprise/guides/build-crew.mdx b/docs/ko/enterprise/guides/build-crew.mdx
index 9ba3c75cb..b6d747172 100644
--- a/docs/ko/enterprise/guides/build-crew.mdx
+++ b/docs/ko/enterprise/guides/build-crew.mdx
@@ -7,7 +7,7 @@ mode: "wide"
 
 ## 개요
 
-[CrewAI Enterprise](https://app.crewai.com)는 프로덕션 환경에서 AI 에이전트를 **생성**, **배포** 및 **관리**하는 과정을 간소화합니다.
+[CrewAI AMP](https://app.crewai.com)는 프로덕션 환경에서 AI 에이전트를 **생성**, **배포** 및 **관리**하는 과정을 간소화합니다.
 
 ## 시작하기
 
diff --git a/docs/ko/enterprise/guides/deploy-crew.mdx b/docs/ko/enterprise/guides/deploy-crew.mdx
index a8ee0da14..8b703ae24 100644
--- a/docs/ko/enterprise/guides/deploy-crew.mdx
+++ b/docs/ko/enterprise/guides/deploy-crew.mdx
@@ -6,7 +6,7 @@ mode: "wide"
 ---
 
 <Note>
-로컬에서 또는 Crew Studio를 통해 crew를 생성한 후, 다음 단계는 이를 CrewAI Enterprise 플랫폼에 배포하는 것입니다. 본 가이드에서는 다양한 배포 방법을 다루며, 여러분의 워크플로우에 가장 적합한 방식을 선택할 수 있도록 안내합니다.
+로컬에서 또는 Crew Studio를 통해 crew를 생성한 후, 다음 단계는 이를 CrewAI AMP 플랫폼에 배포하는 것입니다. 본 가이드에서는 다양한 배포 방법을 다루며, 여러분의 워크플로우에 가장 적합한 방식을 선택할 수 있도록 안내합니다.
 </Note>
 
 ## 사전 준비 사항
@@ -39,10 +39,10 @@ CLI는 로컬에서 개발된 crew를 Enterprise 플랫폼에 가장 빠르게 
   </Step>
 
   <Step title="Enterprise 플랫폼에 인증">
-    먼저, CrewAI Enterprise 플랫폼에 CLI를 인증해야 합니다:
+    먼저, CrewAI AMP 플랫폼에 CLI를 인증해야 합니다:
 
     ```bash
-    # 이미 CrewAI Enterprise 계정이 있거나 새로 생성하고 싶을 때:
+    # 이미 CrewAI AMP 계정이 있거나 새로 생성하고 싶을 때:
     crewai login
     ```
 
@@ -124,7 +124,7 @@ crewai deploy remove <deployment_id>
 
 ## 옵션 2: 웹 인터페이스를 통한 직접 배포
 
-GitHub 계정을 연결하여 CrewAI Enterprise 웹 인터페이스를 통해 crews를 직접 배포할 수도 있습니다. 이 방법은 로컬 머신에서 CLI를 사용할 필요가 없습니다.
+GitHub 계정을 연결하여 CrewAI AMP 웹 인터페이스를 통해 crews를 직접 배포할 수도 있습니다. 이 방법은 로컬 머신에서 CLI를 사용할 필요가 없습니다.
 
 <Steps>
 
@@ -134,9 +134,9 @@ GitHub 계정을 연결하여 CrewAI Enterprise 웹 인터페이스를 통해 cr
 
   </Step>
 
-  <Step title="GitHub를 CrewAI Enterprise에 연결하기">
+  <Step title="GitHub를 CrewAI AMP에 연결하기">
 
-    1. [CrewAI Enterprise](https://app.crewai.com)에 로그인합니다.
+    1. [CrewAI AMP](https://app.crewai.com)에 로그인합니다.
     2. "Connect GitHub" 버튼을 클릭합니다.
 
     <Frame>
@@ -190,7 +190,7 @@ GitHub 계정을 연결하여 CrewAI Enterprise 웹 인터페이스를 통해 cr
 ## ⚠️ 환경 변수 보안 요구사항
 
 <Warning>
-**중요**: CrewAI Enterprise는 환경 변수 이름에 대한 보안 제한이 있으며, 이를 따르지 않을 경우 배포가 실패할 수 있습니다.
+**중요**: CrewAI AMP는 환경 변수 이름에 대한 보안 제한이 있으며, 이를 따르지 않을 경우 배포가 실패할 수 있습니다.
 </Warning>
 
 ### 차단된 환경 변수 패턴
diff --git a/docs/ko/enterprise/guides/enable-crew-studio.mdx b/docs/ko/enterprise/guides/enable-crew-studio.mdx
index f6119f885..873450d65 100644
--- a/docs/ko/enterprise/guides/enable-crew-studio.mdx
+++ b/docs/ko/enterprise/guides/enable-crew-studio.mdx
@@ -1,6 +1,6 @@
 ---
 title: "Crew Studio 활성화"
-description: "CrewAI Enterprise에서 Crew Studio 활성화하기"
+description: "CrewAI AMP에서 Crew Studio 활성화하기"
 icon: "comments"
 mode: "wide"
 ---
@@ -24,7 +24,7 @@ Crew Studio를 사용하면 다음과 같은 작업이 가능합니다:
 - 적절한 tool 선택
 - 필요한 입력값 구성
 - 커스터마이징을 위한 다운로드 가능한 코드 생성
-- CrewAI Enterprise 플랫폼에 직접 배포
+- CrewAI AMP 플랫폼에 직접 배포
 
 ## 구성 단계
 
@@ -32,7 +32,7 @@ Crew Studio를 사용하기 전에 LLM 연결을 구성해야 합니다:
 
 <Steps>
   <Step title="LLM 연결 설정">
-    CrewAI Enterprise 대시보드의 **LLM Connections** 탭으로 이동하여 새 LLM 연결을 만듭니다.
+    CrewAI AMP 대시보드의 **LLM Connections** 탭으로 이동하여 새 LLM 연결을 만듭니다.
 
     <Note>
       CrewAI에서 지원하는 원하는 LLM 공급자를 자유롭게 사용하실 수 있습니다.
@@ -82,7 +82,7 @@ LLM 연결과 기본 설정을 구성했다면 이제 Crew Studio 사용을 시
 
 <Steps>
   <Step title="Studio 접속">
-    CrewAI Enterprise 대시보드에서 **Studio** 섹션으로 이동하세요.
+    CrewAI AMP 대시보드에서 **Studio** 섹션으로 이동하세요.
   </Step>
   
   <Step title="대화 시작">
@@ -110,7 +110,7 @@ LLM 연결과 기본 설정을 구성했다면 이제 Crew Studio 사용을 시
     구성에 만족하면 다음을 수행할 수 있습니다:
     
     - 생성된 코드를 다운로드하여 로컬에서 커스터마이징
-    - crew를 CrewAI Enterprise 플랫폼에 직접 배포
+    - crew를 CrewAI AMP 플랫폼에 직접 배포
     - 구성을 수정하고 crew를 재생성
   </Step>
   
@@ -162,5 +162,5 @@ LLM 연결과 기본 설정을 구성했다면 이제 Crew Studio 사용을 시
 </Steps>
 
 <Card title="도움이 필요하세요?" icon="headset" href="mailto:support@crewai.com">
-  Crew Studio 또는 기타 CrewAI Enterprise 기능 지원이 필요하다면 지원팀에 문의하세요.
+  Crew Studio 또는 기타 CrewAI AMP 기능 지원이 필요하다면 지원팀에 문의하세요.
 </Card>
\ No newline at end of file
diff --git a/docs/ko/enterprise/guides/gmail-trigger.mdx b/docs/ko/enterprise/guides/gmail-trigger.mdx
new file mode 100644
index 000000000..2caefc045
--- /dev/null
+++ b/docs/ko/enterprise/guides/gmail-trigger.mdx
@@ -0,0 +1,85 @@
+---
+title: "Gmail Trigger"
+description: "Trigger automations when Gmail events occur (e.g., new emails, labels)."
+icon: "envelope"
+mode: "wide"
+---
+
+## Overview
+
+Use the Gmail Trigger to kick off your deployed crews when Gmail events happen in connected accounts, such as receiving a new email or messages matching a label/filter.
+
+<Tip>
+  Make sure Gmail is connected in Tools & Integrations and the trigger is enabled for your deployment.
+</Tip>
+
+## Enabling the Gmail Trigger
+
+1. Open your deployment in CrewAI AMP
+2. Go to the **Triggers** tab
+3. Locate **Gmail** and switch the toggle to enable
+
+<Frame>
+  <img src="/images/enterprise/trigger-selected.png" alt="Enable or disable triggers with toggle" />
+</Frame>
+
+## Example: Process new emails
+
+When a new email arrives, the Gmail Trigger will send the payload to your Crew or Flow. Below is a Crew example that parses and processes the trigger payload.
+
+```python
+@CrewBase
+class GmailProcessingCrew:
+    @agent
+    def parser(self) -> Agent:
+        return Agent(
+            config=self.agents_config['parser'],
+        )
+
+    @task
+    def parse_gmail_payload(self) -> Task:
+        return Task(
+            config=self.tasks_config['parse_gmail_payload'],
+            agent=self.parser(),
+        )
+
+    @task
+    def act_on_email(self) -> Task:
+        return Task(
+            config=self.tasks_config['act_on_email'],
+            agent=self.parser(),
+        )
+```
+
+The Gmail payload will be available via the standard context mechanisms. See the payload samples repository for structure and fields.
+
+### Sample payloads & crews
+
+The [CrewAI AMP Trigger Examples repository](https://github.com/crewAIInc/crewai-enterprise-trigger-examples/tree/main/gmail) includes:
+
+- `new-email-payload-1.json` / `new-email-payload-2.json` — production-style new message alerts with matching crews in `new-email-crew.py`
+- `thread-updated-sample-1.json` — follow-up messages on an existing thread, processed by `gmail-alert-crew.py`
+
+Use these samples to validate your parsing logic locally before wiring the trigger to your live Gmail accounts.
+
+## Monitoring Executions
+
+Track history and performance of triggered runs:
+
+<Frame>
+  <img src="/images/enterprise/list-executions.png" alt="List of executions triggered by automation" />
+</Frame>
+
+## Payload Reference
+
+See the sample payloads and field descriptions:
+
+<Card title="Gmail samples in Trigger Examples Repo" href="https://github.com/crewAIInc/crewai-enterprise-trigger-examples/tree/main/gmail" icon="envelopes-bulk">
+    Gmail samples in Trigger Examples Repo
+</Card>
+
+## Troubleshooting
+
+- Ensure Gmail is connected in Tools & Integrations
+- Verify the Gmail Trigger is enabled on the Triggers tab
+- Check the execution logs and confirm the payload is passed as `crewai_trigger_payload`
diff --git a/docs/ko/enterprise/guides/google-calendar-trigger.mdx b/docs/ko/enterprise/guides/google-calendar-trigger.mdx
new file mode 100644
index 000000000..cf2d32471
--- /dev/null
+++ b/docs/ko/enterprise/guides/google-calendar-trigger.mdx
@@ -0,0 +1,65 @@
+---
+title: "Google Calendar Trigger"
+description: "Kick off crews when Google Calendar events are created, updated, or cancelled"
+icon: "calendar"
+mode: "wide"
+---
+
+## Overview
+
+Use the Google Calendar trigger to launch automations whenever calendar events change. Common use cases include briefing a team before a meeting, notifying stakeholders when a critical event is cancelled, or summarizing daily schedules.
+
+<Tip>
+  Make sure Google Calendar is connected in **Tools & Integrations** and enabled for the deployment you want to automate.
+</Tip>
+
+## Enabling the Google Calendar Trigger
+
+1. Open your deployment in CrewAI AMP
+2. Go to the **Triggers** tab
+3. Locate **Google Calendar** and switch the toggle to enable
+
+<Frame>
+  <img src="/images/enterprise/calendar-trigger.png" alt="Enable or disable triggers with toggle" />
+</Frame>
+
+## Example: Summarize meeting details
+
+The snippet below mirrors the `calendar-event-crew.py` example in the trigger repository. It parses the payload, analyses the attendees and timing, and produces a meeting brief for downstream tools.
+
+```python
+from calendar_event_crew import GoogleCalendarEventTrigger
+
+crew = GoogleCalendarEventTrigger().crew()
+result = crew.kickoff({
+    "crewai_trigger_payload": calendar_payload,
+})
+print(result.raw)
+```
+
+Use `crewai_trigger_payload` exactly as it is delivered by the trigger so the crew can extract the proper fields.
+
+## Sample payloads & crews
+
+The [Google Calendar examples](https://github.com/crewAIInc/crewai-enterprise-trigger-examples/tree/main/google_calendar) show how to handle multiple event types:
+
+- `new-event.json` → standard event creation handled by `calendar-event-crew.py`
+- `event-updated.json` / `event-started.json` / `event-ended.json` → in-flight updates processed by `calendar-meeting-crew.py`
+- `event-canceled.json` → cancellation workflow that alerts attendees via `calendar-meeting-crew.py`
+- Working location events use `calendar-working-location-crew.py` to extract on-site schedules
+
+Each crew transforms raw event metadata (attendees, rooms, working locations) into the summaries your teams need.
+
+## Monitoring Executions
+
+The **Executions** list in the deployment dashboard tracks every triggered run and surfaces payload metadata, output summaries, and errors.
+
+<Frame>
+  <img src="/images/enterprise/list-executions.png" alt="List of executions triggered by automation" />
+</Frame>
+
+## Troubleshooting
+
+- Ensure the correct Google account is connected and the trigger is enabled
+- Confirm your workflow handles all-day events (payloads use `start.date` and `end.date` instead of timestamps)
+- Check execution logs if reminders or attendee arrays are missing—calendar permissions can limit fields in the payload
diff --git a/docs/ko/enterprise/guides/google-drive-trigger.mdx b/docs/ko/enterprise/guides/google-drive-trigger.mdx
new file mode 100644
index 000000000..19c10837b
--- /dev/null
+++ b/docs/ko/enterprise/guides/google-drive-trigger.mdx
@@ -0,0 +1,61 @@
+---
+title: "Google Drive Trigger"
+description: "Respond to Google Drive file events with automated crews"
+icon: "folder"
+mode: "wide"
+---
+
+## Overview
+
+Trigger your automations when files are created, updated, or removed in Google Drive. Typical workflows include summarizing newly uploaded content, enforcing sharing policies, or notifying owners when critical files change.
+
+<Tip>
+  Connect Google Drive in **Tools & Integrations** and confirm the trigger is enabled for the automation you want to monitor.
+</Tip>
+
+## Enabling the Google Drive Trigger
+
+1. Open your deployment in CrewAI AMP
+2. Go to the **Triggers** tab
+3. Locate **Google Drive** and switch the toggle to enable
+
+<Frame>
+  <img src="/images/enterprise/gdrive-trigger.png" alt="Enable or disable triggers with toggle" />
+</Frame>
+
+## Example: Summarize file activity
+
+The drive example crews parse the payload to extract file metadata, evaluate permissions, and publish a summary.
+
+```python
+from drive_file_crew import GoogleDriveFileTrigger
+
+crew = GoogleDriveFileTrigger().crew()
+crew.kickoff({
+    "crewai_trigger_payload": drive_payload,
+})
+```
+
+## Sample payloads & crews
+
+Explore the [Google Drive examples](https://github.com/crewAIInc/crewai-enterprise-trigger-examples/tree/main/google_drive) to cover different operations:
+
+- `new-file.json` → new uploads processed by `drive-file-crew.py`
+- `updated-file.json` → file edits and metadata changes handled by `drive-file-crew.py`
+- `deleted-file.json` → deletion events routed through `drive-file-deletion-crew.py`
+
+Each crew highlights the file name, operation type, owner, permissions, and security considerations so downstream systems can respond appropriately.
+
+## Monitoring Executions
+
+Track history and performance of triggered runs with the **Executions** list in the deployment dashboard.
+
+<Frame>
+  <img src="/images/enterprise/list-executions.png" alt="List of executions triggered by automation" />
+</Frame>
+
+## Troubleshooting
+
+- Verify Google Drive is connected and the trigger toggle is enabled
+- If a payload is missing permission data, ensure the connected account has access to the file or folder
+- The trigger sends file IDs only; use the Drive API if you need to fetch binary content during the crew run
diff --git a/docs/ko/enterprise/guides/hubspot-trigger.mdx b/docs/ko/enterprise/guides/hubspot-trigger.mdx
index 4d55eb1f4..468841a94 100644
--- a/docs/ko/enterprise/guides/hubspot-trigger.mdx
+++ b/docs/ko/enterprise/guides/hubspot-trigger.mdx
@@ -5,22 +5,22 @@ icon: "hubspot"
 mode: "wide"
 ---
 
-이 가이드는 HubSpot Workflows에서 직접 crew를 시작할 수 있도록 CrewAI Enterprise용 HubSpot 트리거를 설정하는 단계별 과정을 제공합니다.
+이 가이드는 HubSpot Workflows에서 직접 crew를 시작할 수 있도록 CrewAI AMP용 HubSpot 트리거를 설정하는 단계별 과정을 제공합니다.
 
 ## 사전 준비 사항
 
-- CrewAI Enterprise 계정
+- CrewAI AMP 계정
 - [HubSpot Workflows](https://knowledge.hubspot.com/workflows/create-workflows) 기능이 활성화된 HubSpot 계정
 
 ## 설정 단계
 
 <Steps>
-    <Step title="HubSpot 계정을 CrewAI Enterprise와 연결하기">
-        - `CrewAI Enterprise 계정 > 트리거`에 로그인합니다.
+    <Step title="HubSpot 계정을 CrewAI AMP와 연결하기">
+        - `CrewAI AMP 계정 > 트리거`에 로그인합니다.
         - 사용 가능한 트리거 목록에서 `HubSpot`을 선택합니다.
-        - CrewAI Enterprise와 연결하고자 하는 HubSpot 계정을 선택합니다.
-        - 화면에 나타나는 안내에 따라 CrewAI Enterprise가 HubSpot 계정에 접근하도록 승인합니다.
-        - HubSpot이 CrewAI Enterprise와 성공적으로 연결되면 확인 메시지가 표시됩니다.
+        - CrewAI AMP와 연결하고자 하는 HubSpot 계정을 선택합니다.
+        - 화면에 나타나는 안내에 따라 CrewAI AMP가 HubSpot 계정에 접근하도록 승인합니다.
+        - HubSpot이 CrewAI AMP와 성공적으로 연결되면 확인 메시지가 표시됩니다.
     </Step>
     <Step title="HubSpot 워크플로우 생성하기">
         - `HubSpot 계정 > 자동화 > 워크플로우 > 새 워크플로우`에 로그인합니다.
diff --git a/docs/ko/enterprise/guides/kickoff-crew.mdx b/docs/ko/enterprise/guides/kickoff-crew.mdx
index 3f7eb2d5d..039fef9c2 100644
--- a/docs/ko/enterprise/guides/kickoff-crew.mdx
+++ b/docs/ko/enterprise/guides/kickoff-crew.mdx
@@ -1,19 +1,19 @@
 ---
 title: "Kickoff Crew"
-description: "CrewAI Enterprise에서 Crew를 시작하세요"
+description: "CrewAI AMP에서 Crew를 시작하세요"
 icon: "flag-checkered"
 mode: "wide"
 ---
 
 ## 개요
 
-Crew를 CrewAI Enterprise 플랫폼에 배포한 후에는 웹 인터페이스 또는 API를 통해 실행을 시작할 수 있습니다. 이 가이드는 두 가지 접근 방식을 모두 다룹니다.
+Crew를 CrewAI AMP 플랫폼에 배포한 후에는 웹 인터페이스 또는 API를 통해 실행을 시작할 수 있습니다. 이 가이드는 두 가지 접근 방식을 모두 다룹니다.
 
 ## 방법 1: 웹 인터페이스 사용
 
 ### 1단계: 배포된 Crew로 이동하기
 
-1. [CrewAI Enterprise](https://app.crewai.com)에 로그인합니다.
+1. [CrewAI AMP](https://app.crewai.com)에 로그인합니다.
 2. 프로젝트 목록에서 crew 이름을 클릭합니다.
 3. crew의 상세 페이지로 이동합니다.
 
@@ -83,7 +83,7 @@ crew의 상세 페이지에서 실행을 시작할 수 있는 두 가지 옵션
 
 ## 방법 2: API 사용
 
-CrewAI Enterprise REST API를 사용하여 프로그래밍 방식으로 crews를 시작할 수도 있습니다.
+CrewAI AMP REST API를 사용하여 프로그래밍 방식으로 crews를 시작할 수도 있습니다.
 
 ### 인증
 
diff --git a/docs/ko/enterprise/guides/microsoft-teams-trigger.mdx b/docs/ko/enterprise/guides/microsoft-teams-trigger.mdx
new file mode 100644
index 000000000..10878af40
--- /dev/null
+++ b/docs/ko/enterprise/guides/microsoft-teams-trigger.mdx
@@ -0,0 +1,52 @@
+---
+title: "Microsoft Teams Trigger"
+description: "Kick off crews from Microsoft Teams chat activity"
+icon: "microsoft"
+mode: "wide"
+---
+
+## Overview
+
+Use the Microsoft Teams trigger to start automations whenever a new chat is created. Common patterns include summarizing inbound requests, routing urgent messages to support teams, or creating follow-up tasks in other systems.
+
+<Tip>
+  Confirm Microsoft Teams is connected under **Tools & Integrations** and enabled in the **Triggers** tab for your deployment.
+</Tip>
+
+## Enabling the Microsoft Teams Trigger
+
+1. Open your deployment in CrewAI AMP
+2. Go to the **Triggers** tab
+3. Locate **Microsoft Teams** and switch the toggle to enable
+
+<Frame caption="Microsoft Teams trigger connection">
+  <img src="/images/enterprise/msteams-trigger.png" alt="Enable or disable triggers with toggle" />
+</Frame>
+
+## Example: Summarize a new chat thread
+
+```python
+from teams_chat_created_crew import MicrosoftTeamsChatTrigger
+
+crew = MicrosoftTeamsChatTrigger().crew()
+result = crew.kickoff({
+    "crewai_trigger_payload": teams_payload,
+})
+print(result.raw)
+```
+
+The crew parses thread metadata (subject, created time, roster) and generates an action plan for the receiving team.
+
+## Sample payloads & crews
+
+The [Microsoft Teams examples](https://github.com/crewAIInc/crewai-enterprise-trigger-examples/tree/main/microsoft-teams) include:
+
+- `chat-created.json` → chat creation payload processed by `teams-chat-created-crew.py`
+
+The crew demonstrates how to extract participants, initial messages, tenant information, and compliance metadata from the Microsoft Graph webhook payload.
+
+## Troubleshooting
+
+- Ensure the Teams connection is active; it must be refreshed if the tenant revokes permissions
+- Confirm the webhook subscription in Microsoft 365 is still valid if payloads stop arriving
+- Review execution logs for payload shape mismatches—Graph notifications may omit fields when a chat is private or restricted
diff --git a/docs/ko/enterprise/guides/onedrive-trigger.mdx b/docs/ko/enterprise/guides/onedrive-trigger.mdx
new file mode 100644
index 000000000..51de175db
--- /dev/null
+++ b/docs/ko/enterprise/guides/onedrive-trigger.mdx
@@ -0,0 +1,53 @@
+---
+title: "OneDrive Trigger"
+description: "Automate responses to OneDrive file activity"
+icon: "cloud"
+mode: "wide"
+---
+
+## Overview
+
+Start automations when files change inside OneDrive. You can generate audit summaries, notify security teams about external sharing, or update downstream line-of-business systems with new document metadata.
+
+<Tip>
+  Connect OneDrive in **Tools & Integrations** and toggle the trigger on for your deployment.
+</Tip>
+
+## Enabling the OneDrive Trigger
+
+1. Open your deployment in CrewAI AMP
+2. Go to the **Triggers** tab
+3. Locate **OneDrive** and switch the toggle to enable
+
+<Frame caption="Microsoft OneDrive trigger connection">
+  <img src="/images/enterprise/onedrive-trigger.png" alt="Enable or disable triggers with toggle" />
+</Frame>
+
+## Example: Audit file permissions
+
+```python
+from onedrive_file_crew import OneDriveFileTrigger
+
+crew = OneDriveFileTrigger().crew()
+crew.kickoff({
+    "crewai_trigger_payload": onedrive_payload,
+})
+```
+
+The crew inspects file metadata, user activity, and permission changes to produce a compliance-friendly summary.
+
+## Sample payloads & crews
+
+The [OneDrive examples](https://github.com/crewAIInc/crewai-enterprise-trigger-examples/tree/main/onedrive) showcase how to:
+
+- Parse file metadata, size, and folder paths
+- Track who created and last modified the file
+- Highlight permission and external sharing changes
+
+`onedrive-file-crew.py` bundles the analysis and summarization tasks so you can add remediation steps as needed.
+
+## Troubleshooting
+
+- Ensure the connected account has permission to read the file metadata included in the webhook
+- If the trigger fires but the payload is missing `permissions`, confirm the site-level sharing settings allow Graph to return this field
+- For large tenants, filter notifications upstream so the crew only runs on relevant directories
diff --git a/docs/ko/enterprise/guides/outlook-trigger.mdx b/docs/ko/enterprise/guides/outlook-trigger.mdx
new file mode 100644
index 000000000..21bda5407
--- /dev/null
+++ b/docs/ko/enterprise/guides/outlook-trigger.mdx
@@ -0,0 +1,52 @@
+---
+title: "Outlook Trigger"
+description: "Launch automations from Outlook emails and calendar updates"
+icon: "microsoft"
+mode: "wide"
+---
+
+## Overview
+
+Automate responses when Outlook delivers a new message or when an event is removed from the calendar. Teams commonly route escalations, file tickets, or alert attendees of cancellations.
+
+<Tip>
+  Connect Outlook in **Tools & Integrations** and ensure the trigger is enabled for your deployment.
+</Tip>
+
+## Enabling the Outlook Trigger
+
+1. Open your deployment in CrewAI AMP
+2. Go to the **Triggers** tab
+3. Locate **Outlook** and switch the toggle to enable
+
+<Frame caption="Microsoft Outlook trigger connection">
+  <img src="/images/enterprise/outlook-trigger.png" alt="Enable or disable triggers with toggle" />
+</Frame>
+
+## Example: Summarize a new email
+
+```python
+from outlook_message_crew import OutlookMessageTrigger
+
+crew = OutlookMessageTrigger().crew()
+crew.kickoff({
+    "crewai_trigger_payload": outlook_payload,
+})
+```
+
+The crew extracts sender details, subject, body preview, and attachments before generating a structured response.
+
+## Sample payloads & crews
+
+Review the [Outlook examples](https://github.com/crewAIInc/crewai-enterprise-trigger-examples/tree/main/outlook) for two common scenarios:
+
+- `new-message.json` → new mail notifications parsed by `outlook-message-crew.py`
+- `event-removed.json` → calendar cleanup handled by `outlook-event-removal-crew.py`
+
+Each crew demonstrates how to handle Microsoft Graph payloads, normalize headers, and keep humans in-the-loop with concise summaries.
+
+## Troubleshooting
+
+- Verify the Outlook connector is still authorized; the subscription must be renewed periodically
+- If attachments are missing, confirm the webhook subscription includes the `includeResourceData` flag
+- Review execution logs when events fail to match—cancellation payloads lack attendee lists by design and the crew should account for that
diff --git a/docs/ko/enterprise/guides/react-component-export.mdx b/docs/ko/enterprise/guides/react-component-export.mdx
index e68defcdb..afc193667 100644
--- a/docs/ko/enterprise/guides/react-component-export.mdx
+++ b/docs/ko/enterprise/guides/react-component-export.mdx
@@ -1,11 +1,11 @@
 ---
 title: "React 컴포넌트 내보내기"
-description: "CrewAI Enterprise React 컴포넌트를 애플리케이션에 내보내고 통합하는 방법을 알아보세요"
+description: "CrewAI AMP React 컴포넌트를 애플리케이션에 내보내고 통합하는 방법을 알아보세요"
 icon: "react"
 mode: "wide"
 ---
 
-이 가이드는 CrewAI Enterprise crew를 React 컴포넌트로 내보내고 이를 여러분의 애플리케이션에 통합하는 방법을 설명합니다.
+이 가이드는 CrewAI AMP crew를 React 컴포넌트로 내보내고 이를 여러분의 애플리케이션에 통합하는 방법을 설명합니다.
 
 ## React 컴포넌트 내보내기
 
diff --git a/docs/ko/enterprise/guides/salesforce-trigger.mdx b/docs/ko/enterprise/guides/salesforce-trigger.mdx
index a7ebff677..9d4e92e58 100644
--- a/docs/ko/enterprise/guides/salesforce-trigger.mdx
+++ b/docs/ko/enterprise/guides/salesforce-trigger.mdx
@@ -5,7 +5,7 @@ icon: "salesforce"
 mode: "wide"
 ---
 
-CrewAI Enterprise는 Salesforce에서 트리거되어 고객 관계 관리 워크플로우를 자동화하고 영업 운영을 강화할 수 있습니다.
+CrewAI AMP는 Salesforce에서 트리거되어 고객 관계 관리 워크플로우를 자동화하고 영업 운영을 강화할 수 있습니다.
 
 ## 개요
 
@@ -31,7 +31,7 @@ Salesforce는 기업이 영업, 서비스, 마케팅 운영을 효율화할 수
 
 Salesforce 트리거를 설정하려면:
 
-1. **지원팀 문의**: Salesforce 트리거 설정을 위해 CrewAI Enterprise 지원팀에 연락하세요.
+1. **지원팀 문의**: Salesforce 트리거 설정을 위해 CrewAI AMP 지원팀에 연락하세요.
 2. **요구 사항 검토**: 필요한 Salesforce 권한과 API 액세스 권한이 있는지 확인하세요.
 3. **연결 구성**: 지원팀과 협력하여 CrewAI와 귀하의 Salesforce 인스턴스 간의 연결을 설정하세요.
 4. **트리거 테스트**: 트리거가 귀하의 특정 사용 사례에 맞게 올바르게 작동하는지 확인하세요.
@@ -47,4 +47,4 @@ Salesforce 트리거를 설정하려면:
 
 ## 다음 단계
 
-자세한 설정 지침 및 고급 구성 옵션에 대해서는 CrewAI Enterprise 지원팀에 문의해 주시기 바랍니다. 지원팀은 귀하의 특정 Salesforce 환경과 비즈니스 요구에 맞는 맞춤형 안내를 제공해 드릴 수 있습니다.
+자세한 설정 지침 및 고급 구성 옵션에 대해서는 CrewAI AMP 지원팀에 문의해 주시기 바랍니다. 지원팀은 귀하의 특정 Salesforce 환경과 비즈니스 요구에 맞는 맞춤형 안내를 제공해 드릴 수 있습니다.
diff --git a/docs/ko/enterprise/guides/team-management.mdx b/docs/ko/enterprise/guides/team-management.mdx
index 50096adc5..8b56fe273 100644
--- a/docs/ko/enterprise/guides/team-management.mdx
+++ b/docs/ko/enterprise/guides/team-management.mdx
@@ -1,17 +1,17 @@
 ---
 title: "팀 관리"
-description: "CrewAI Enterprise 조직에서 팀원을 초대하고 관리하는 방법을 알아보세요"
+description: "CrewAI AMP 조직에서 팀원을 초대하고 관리하는 방법을 알아보세요"
 icon: "users"
 mode: "wide"
 ---
 
-CrewAI Enterprise 계정의 관리자라면 새로운 팀원을 조직에 쉽게 초대할 수 있습니다. 이 안내서는 단계별로 프로세스를 안내합니다.
+CrewAI AMP 계정의 관리자라면 새로운 팀원을 조직에 쉽게 초대할 수 있습니다. 이 안내서는 단계별로 프로세스를 안내합니다.
 
 ## 팀 멤버 초대하기
 
 <Steps>
     <Step title="설정 페이지 접속">
-        - CrewAI Enterprise 계정에 로그인합니다
+        - CrewAI AMP 계정에 로그인합니다
         - 대시보드 오른쪽 상단에 있는 기어 아이콘(⚙️)을 찾습니다
         - 기어 아이콘을 클릭하여 **설정** 페이지에 접속합니다:
             <Frame>
@@ -43,7 +43,7 @@ CrewAI Enterprise 계정의 관리자라면 새로운 팀원을 조직에 쉽게
 
 <Steps>
     <Step title="설정 페이지 접근">
-        - CrewAI Enterprise 계정에 로그인하세요
+        - CrewAI AMP 계정에 로그인하세요
         - 대시보드 오른쪽 상단에서 기어 아이콘(⚙️)을 찾으세요
         - 기어 아이콘을 클릭하여 **설정** 페이지에 접근하세요:
             <Frame>
@@ -85,4 +85,4 @@ CrewAI Enterprise 계정의 관리자라면 새로운 팀원을 조직에 쉽게
 - **초대 수락**: 초대된 멤버는 조직에 가입하기 위해 초대를 수락해야 합니다
 - **이메일 알림**: 팀 멤버에게 초대 이메일(스팸 폴더 포함)을 확인하도록 안내할 수 있습니다
 
-이 단계들을 따르면 팀을 손쉽게 확장하고 CrewAI Enterprise 조직 내에서 더욱 효과적으로 협업할 수 있습니다.
\ No newline at end of file
+이 단계들을 따르면 팀을 손쉽게 확장하고 CrewAI AMP 조직 내에서 더욱 효과적으로 협업할 수 있습니다.
\ No newline at end of file
diff --git a/docs/ko/enterprise/guides/tool-repository.mdx b/docs/ko/enterprise/guides/tool-repository.mdx
index 702eb3c49..6600e6c27 100644
--- a/docs/ko/enterprise/guides/tool-repository.mdx
+++ b/docs/ko/enterprise/guides/tool-repository.mdx
@@ -20,11 +20,11 @@ Tool Repository는 CrewAI 도구를 위한 패키지 관리자입니다. 사용
 
 Tool Repository를 사용하기 전에 다음이 준비되어 있어야 합니다:
 
-- [CrewAI Enterprise](https://app.crewai.com) 계정
+- [CrewAI AMP](https://app.crewai.com) 계정
 - [CrewAI CLI](https://docs.crewai.com/concepts/cli#cli) 설치됨
 - uv>=0.5.0 이 설치되어 있어야 합니다. [업그레이드 방법](https://docs.astral.sh/uv/getting-started/installation/#upgrading-uv)을 참고하세요.
 - [Git](https://git-scm.com) 설치 및 구성 완료
-- CrewAI Enterprise 조직에서 도구를 게시하거나 설치할 수 있는 액세스 권한
+- CrewAI AMP 조직에서 도구를 게시하거나 설치할 수 있는 액세스 권한
 
 ## 도구 설치
 
@@ -85,7 +85,7 @@ crewai tool publish
 
 도구를 삭제하려면:
 
-1. [CrewAI Enterprise](https://app.crewai.com)로 이동합니다.
+1. [CrewAI AMP](https://app.crewai.com)로 이동합니다.
 2. **Tools**로 이동합니다.
 3. 도구를 선택합니다.
 4. **Delete**를 클릭합니다.
@@ -100,7 +100,7 @@ crewai tool publish
 
 도구의 보안 점검 상태는 다음에서 확인할 수 있습니다:
 
-`CrewAI Enterprise > Tools > Your Tool > Versions`
+`CrewAI AMP > Tools > Your Tool > Versions`
 
 <Card title="도움이 필요하신가요?" icon="headset" href="mailto:support@crewai.com">
   API 통합 또는 문제 해결에 대한 지원이 필요하시면 지원팀에 문의해 주세요.
diff --git a/docs/ko/enterprise/guides/update-crew.mdx b/docs/ko/enterprise/guides/update-crew.mdx
index f6fc809f4..dbd8d9637 100644
--- a/docs/ko/enterprise/guides/update-crew.mdx
+++ b/docs/ko/enterprise/guides/update-crew.mdx
@@ -1,12 +1,12 @@
 ---
 title: "크루 업데이트"
-description: "CrewAI Enterprise에서 크루 업데이트하기"
+description: "CrewAI AMP에서 크루 업데이트하기"
 icon: "pencil"
 mode: "wide"
 ---
 
 <Note>
-CrewAI Enterprise에 crew를 배포한 후, 코드, 보안 설정 또는 구성을 업데이트해야 할 수 있습니다.  
+CrewAI AMP에 crew를 배포한 후, 코드, 보안 설정 또는 구성을 업데이트해야 할 수 있습니다.  
 이 가이드는 이러한 일반적인 업데이트 작업을 수행하는 방법을 설명합니다.
 </Note>
 
@@ -23,7 +23,7 @@ Crew 배포를 업데이트하고 싶은 이유는 여러 가지가 있을 수 
 
 GitHub 저장소에 새로운 커밋을 푸시한 후 배포를 업데이트하려면 다음 단계를 따르세요:
 
-1. CrewAI Enterprise 플랫폼에서 자신의 crew로 이동하세요.
+1. CrewAI AMP 플랫폼에서 자신의 crew로 이동하세요.
 2. crew 상세 페이지에서 `Re-deploy` 버튼을 클릭하세요.
 
 <Frame>
@@ -36,7 +36,7 @@ GitHub 저장소에 새로운 커밋을 푸시한 후 배포를 업데이트하
 
 현재 토큰이 유출되었을 가능성이 있다고 의심되는 경우 등, 새 베어러 토큰을 생성해야 한다면 다음 단계를 따르세요:
 
-1. CrewAI Enterprise 플랫폼에서 해당 crew로 이동하세요.
+1. CrewAI AMP 플랫폼에서 해당 crew로 이동하세요.
 2. `Bearer Token` 섹션을 찾으세요.
 3. 현재 토큰 옆에 있는 `Reset` 버튼을 클릭하세요.
 
diff --git a/docs/ko/enterprise/guides/webhook-automation.mdx b/docs/ko/enterprise/guides/webhook-automation.mdx
index fd699e447..62200922f 100644
--- a/docs/ko/enterprise/guides/webhook-automation.mdx
+++ b/docs/ko/enterprise/guides/webhook-automation.mdx
@@ -1,17 +1,17 @@
 ---
 title: "웹후크 자동화"
-description: "ActivePieces, Zapier, Make.com과 같은 플랫폼을 사용하여 CrewAI Enterprise 워크플로우를 웹후크로 자동화하세요"
+description: "ActivePieces, Zapier, Make.com과 같은 플랫폼을 사용하여 CrewAI AMP 워크플로우를 웹후크로 자동화하세요"
 icon: "webhook"
 mode: "wide"
 ---
 
-CrewAI Enterprise를 사용하면 웹훅을 통해 워크플로우를 자동화할 수 있습니다. 이 문서에서는 웹훅을 설정하고 사용하는 과정을 안내하며, Zapier와 Make.com과 유사한 워크플로우 자동화 플랫폼인 ActivePieces와의 통합에 중점을 두고 crew 실행을 시작하는 방법을 설명합니다.
+CrewAI AMP를 사용하면 웹훅을 통해 워크플로우를 자동화할 수 있습니다. 이 문서에서는 웹훅을 설정하고 사용하는 과정을 안내하며, Zapier와 Make.com과 유사한 워크플로우 자동화 플랫폼인 ActivePieces와의 통합에 중점을 두고 crew 실행을 시작하는 방법을 설명합니다.
 
 ## Webhook 설정하기
 
 <Steps>
     <Step title="Kickoff 인터페이스 접근">
-        - CrewAI Enterprise 대시보드로 이동하세요.
+        - CrewAI AMP 대시보드로 이동하세요.
         - crew 실행을 시작할 때 사용하는 `/kickoff` 섹션을 찾으세요.
             <Frame>
                 <img src="/images/enterprise/kickoff-interface.png" alt="Kickoff 인터페이스" />
@@ -44,7 +44,7 @@ CrewAI Enterprise를 사용하면 웹훅을 통해 워크플로우를 자동화
         3. HTTP 액션 단계를 추가하세요.
             - 액션을 `Send HTTP request`로 설정하세요.
             - 메소드는 `POST`로 사용하세요.
-            - URL은 CrewAI Enterprise kickoff 엔드포인트로 설정하세요.
+            - URL은 CrewAI AMP kickoff 엔드포인트로 설정하세요.
             - 필요한 헤더 추가 (예: `Bearer Token`)
                 <Frame>
                     <img src="/images/enterprise/activepieces-headers.png" alt="ActivePieces 헤더" />
diff --git a/docs/ko/enterprise/guides/zapier-trigger.mdx b/docs/ko/enterprise/guides/zapier-trigger.mdx
index 662633f2a..e590ba854 100644
--- a/docs/ko/enterprise/guides/zapier-trigger.mdx
+++ b/docs/ko/enterprise/guides/zapier-trigger.mdx
@@ -5,11 +5,11 @@ icon: "bolt"
 mode: "wide"
 ---
 
-이 가이드는 CrewAI Enterprise용 Zapier 트리거를 설정하는 과정을 안내합니다. 이를 통해 CrewAI Enterprise와 기타 애플리케이션 간의 워크플로우를 자동화할 수 있습니다.
+이 가이드는 CrewAI AMP용 Zapier 트리거를 설정하는 과정을 안내합니다. 이를 통해 CrewAI AMP와 기타 애플리케이션 간의 워크플로우를 자동화할 수 있습니다.
 
 ## 사전 요구 사항
 
-- CrewAI Enterprise 계정
+- CrewAI AMP 계정
 - Zapier 계정
 - Slack 계정 (이 특정 예시에 해당)
 
@@ -32,7 +32,7 @@ mode: "wide"
         - 아직 Slack 계정을 연결하지 않았다면 연결하세요.
     </Step>
 
-    <Step title="CrewAI Enterprise 액션 구성">
+    <Step title="CrewAI AMP 액션 구성">
         - Zap에 새 액션 단계를 추가합니다.
         - CrewAI+를 액션 앱으로, Kickoff를 액션 이벤트로 선택합니다.
 
@@ -41,8 +41,8 @@ mode: "wide"
         </Frame>
     </Step>
 
-    <Step title="CrewAI Enterprise 계정 연결">
-        - CrewAI Enterprise 계정을 연결하세요.
+    <Step title="CrewAI AMP 계정 연결">
+        - CrewAI AMP 계정을 연결하세요.
         - 워크플로에 적합한 Crew를 선택하세요.
 
         <Frame>
@@ -51,8 +51,8 @@ mode: "wide"
         - Slack 메시지의 데이터를 사용하여 Crew의 입력값을 구성하세요.
     </Step>
 
-    <Step title="CrewAI Enterprise 출력 포맷팅">
-        - CrewAI Enterprise에서 출력된 텍스트를 포맷팅하기 위해 추가 액션 단계를 추가합니다.
+    <Step title="CrewAI AMP 출력 포맷팅">
+        - CrewAI AMP에서 출력된 텍스트를 포맷팅하기 위해 추가 액션 단계를 추가합니다.
         - Zapier의 포매팅 도구를 사용하여 Markdown 출력을 HTML로 변환합니다.
 
         <Frame>
@@ -67,7 +67,7 @@ mode: "wide"
         - 포맷팅된 출력을 이메일로 전송하는 마지막 액션 단계를 추가합니다.
         - 원하는 이메일 서비스를 선택하세요 (예: Gmail, Outlook).
         - 수신자, 제목, 본문 등 이메일 상세 정보를 구성하세요.
-        - 포맷팅된 CrewAI Enterprise 출력을 이메일 본문에 삽입합니다.
+        - 포맷팅된 CrewAI AMP 출력을 이메일 본문에 삽입합니다.
 
         <Frame>
             <img src="/images/enterprise/zapier-7.png" alt="Zapier 7" />
@@ -97,8 +97,8 @@ mode: "wide"
 
 ## 성공을 위한 팁
 
-- CrewAI Enterprise 입력값이 Slack 메시지에서 올바르게 매핑되었는지 확인하세요.
+- CrewAI AMP 입력값이 Slack 메시지에서 올바르게 매핑되었는지 확인하세요.
 - Zap을 활성화하기 전에 철저히 테스트하여 잠재적인 문제를 미리 파악하세요.
 - 워크플로우 내에서 발생할 수 있는 실패 상황을 관리하기 위해 오류 처리 단계를 추가하는 것을 고려하세요.
 
-이 단계를 따르면 Slack 메시지로 트리거되는 자동화된 워크플로우와 CrewAI Enterprise 출력이 포함된 이메일 알림을 설정할 수 있습니다.
\ No newline at end of file
+이 단계를 따르면 Slack 메시지로 트리거되는 자동화된 워크플로우와 CrewAI AMP 출력이 포함된 이메일 알림을 설정할 수 있습니다.
\ No newline at end of file
diff --git a/docs/ko/enterprise/integrations/asana.mdx b/docs/ko/enterprise/integrations/asana.mdx
index bccf34f2e..658e18d19 100644
--- a/docs/ko/enterprise/integrations/asana.mdx
+++ b/docs/ko/enterprise/integrations/asana.mdx
@@ -13,7 +13,7 @@ mode: "wide"
 
 Asana 연동을 사용하기 전에 다음을 확인하세요:
 
-- 활성 구독이 있는 [CrewAI Enterprise](https://app.crewai.com) 계정
+- 활성 구독이 있는 [CrewAI AMP](https://app.crewai.com) 계정
 - 적절한 권한이 있는 Asana 계정
 - [통합 페이지](https://app.crewai.com/crewai_plus/connectors)를 통해 Asana 계정 연결
 
@@ -21,7 +21,7 @@ Asana 연동을 사용하기 전에 다음을 확인하세요:
 
 ### 1. Asana 계정 연결하기
 
-1. [CrewAI Enterprise Integrations](https://app.crewai.com/crewai_plus/connectors)로 이동합니다.
+1. [CrewAI AMP Integrations](https://app.crewai.com/crewai_plus/connectors)로 이동합니다.
 2. 인증 통합 섹션에서 **Asana**를 찾습니다.
 3. **Connect**를 클릭하고 OAuth 플로우를 완료합니다.
 4. 작업 및 프로젝트 관리를 위한 필요한 권한을 부여합니다.
diff --git a/docs/ko/enterprise/integrations/box.mdx b/docs/ko/enterprise/integrations/box.mdx
index 3140b0608..0bd33e860 100644
--- a/docs/ko/enterprise/integrations/box.mdx
+++ b/docs/ko/enterprise/integrations/box.mdx
@@ -13,7 +13,7 @@ mode: "wide"
 
 Box 통합을 사용하기 전에 다음을 확인하세요:
 
-- 활성 구독이 있는 [CrewAI Enterprise](https://app.crewai.com) 계정
+- 활성 구독이 있는 [CrewAI AMP](https://app.crewai.com) 계정
 - 적절한 권한이 있는 Box 계정
 - [통합 페이지](https://app.crewai.com/crewai_plus/connectors)를 통해 Box 계정 연결
 
@@ -21,7 +21,7 @@ Box 통합을 사용하기 전에 다음을 확인하세요:
 
 ### 1. Box 계정 연결하기
 
-1. [CrewAI Enterprise Integrations](https://app.crewai.com/crewai_plus/connectors)로 이동합니다.
+1. [CrewAI AMP Integrations](https://app.crewai.com/crewai_plus/connectors)로 이동합니다.
 2. 인증 통합 섹션에서 **Box**를 찾습니다.
 3. **Connect**를 클릭하고 OAuth 흐름을 완료합니다.
 4. 파일 및 폴더 관리를 위한 필요한 권한을 부여합니다.
diff --git a/docs/ko/enterprise/integrations/clickup.mdx b/docs/ko/enterprise/integrations/clickup.mdx
index 0cdc7ac36..ffa20931e 100644
--- a/docs/ko/enterprise/integrations/clickup.mdx
+++ b/docs/ko/enterprise/integrations/clickup.mdx
@@ -13,7 +13,7 @@ mode: "wide"
 
 ClickUp 통합을 사용하기 전에 다음을 준비해야 합니다:
 
-- 활성 구독이 있는 [CrewAI Enterprise](https://app.crewai.com) 계정
+- 활성 구독이 있는 [CrewAI AMP](https://app.crewai.com) 계정
 - 적절한 권한이 있는 ClickUp 계정
 - [통합 페이지](https://app.crewai.com/crewai_plus/connectors)를 통해 ClickUp 계정 연결
 
@@ -21,7 +21,7 @@ ClickUp 통합을 사용하기 전에 다음을 준비해야 합니다:
 
 ### 1. ClickUp 계정 연결하기
 
-1. [CrewAI Enterprise Integrations](https://app.crewai.com/crewai_plus/connectors)로 이동합니다.
+1. [CrewAI AMP Integrations](https://app.crewai.com/crewai_plus/connectors)로 이동합니다.
 2. 인증 통합 섹션에서 **ClickUp**을 찾습니다.
 3. **Connect**를 클릭하고 OAuth 과정을 완료합니다.
 4. 작업 및 프로젝트 관리에 필요한 권한을 부여합니다.
diff --git a/docs/ko/enterprise/integrations/github.mdx b/docs/ko/enterprise/integrations/github.mdx
index f9635c2f9..06e2cd3fb 100644
--- a/docs/ko/enterprise/integrations/github.mdx
+++ b/docs/ko/enterprise/integrations/github.mdx
@@ -13,7 +13,7 @@ mode: "wide"
 
 GitHub 통합을 사용하기 전에 다음을 확인하세요:
 
-- 활성 구독이 있는 [CrewAI Enterprise](https://app.crewai.com) 계정
+- 활성 구독이 있는 [CrewAI AMP](https://app.crewai.com) 계정
 - 해당 리포지토리에 대한 적절한 권한이 있는 GitHub 계정
 - [통합 페이지](https://app.crewai.com/crewai_plus/connectors)를 통해 GitHub 계정 연결 완료
 
@@ -21,7 +21,7 @@ GitHub 통합을 사용하기 전에 다음을 확인하세요:
 
 ### 1. GitHub 계정 연결하기
 
-1. [CrewAI Enterprise Integrations](https://app.crewai.com/crewai_plus/connectors)로 이동합니다.
+1. [CrewAI AMP Integrations](https://app.crewai.com/crewai_plus/connectors)로 이동합니다.
 2. 인증 통합 섹션에서 **GitHub**을 찾습니다.
 3. **Connect**를 클릭하고 OAuth 흐름을 완료합니다.
 4. 리포지토리 및 이슈 관리를 위한 필수 권한을 부여합니다.
diff --git a/docs/ko/enterprise/integrations/gmail.mdx b/docs/ko/enterprise/integrations/gmail.mdx
index 81f7956fe..de0f68161 100644
--- a/docs/ko/enterprise/integrations/gmail.mdx
+++ b/docs/ko/enterprise/integrations/gmail.mdx
@@ -13,7 +13,7 @@ mode: "wide"
 
 Gmail 통합을 사용하기 전에 다음을 확인하세요:
 
-- 활성 구독이 있는 [CrewAI Enterprise](https://app.crewai.com) 계정
+- 활성 구독이 있는 [CrewAI AMP](https://app.crewai.com) 계정
 - 적절한 권한이 있는 Gmail 계정
 - [통합 페이지](https://app.crewai.com/crewai_plus/connectors)를 통해 Gmail 계정 연결
 
@@ -21,7 +21,7 @@ Gmail 통합을 사용하기 전에 다음을 확인하세요:
 
 ### 1. Gmail 계정 연결하기
 
-1. [CrewAI Enterprise Integrations](https://app.crewai.com/crewai_plus/connectors)로 이동합니다.
+1. [CrewAI AMP Integrations](https://app.crewai.com/crewai_plus/connectors)로 이동합니다.
 2. 인증 통합 섹션에서 **Gmail**을 찾습니다.
 3. **Connect**를 클릭하고 OAuth 흐름을 완료합니다.
 4. 이메일 및 연락처 관리를 위한 필요한 권한을 부여합니다.
diff --git a/docs/ko/enterprise/integrations/google_calendar.mdx b/docs/ko/enterprise/integrations/google_calendar.mdx
index f95d78209..fdaa20005 100644
--- a/docs/ko/enterprise/integrations/google_calendar.mdx
+++ b/docs/ko/enterprise/integrations/google_calendar.mdx
@@ -13,7 +13,7 @@ mode: "wide"
 
 Google Calendar 통합을 사용하기 전에 다음을 준비해야 합니다:
 
-- 활성 구독이 있는 [CrewAI Enterprise](https://app.crewai.com) 계정
+- 활성 구독이 있는 [CrewAI AMP](https://app.crewai.com) 계정
 - Google Calendar에 접근 가능한 Google 계정
 - [통합 페이지](https://app.crewai.com/crewai_plus/connectors)를 통해 Google 계정을 연결 완료
 
@@ -21,7 +21,7 @@ Google Calendar 통합을 사용하기 전에 다음을 준비해야 합니다:
 
 ### 1. Google 계정 연결하기
 
-1. [CrewAI Enterprise Integrations](https://app.crewai.com/crewai_plus/connectors)로 이동합니다.
+1. [CrewAI AMP Integrations](https://app.crewai.com/crewai_plus/connectors)로 이동합니다.
 2. 인증 통합 섹션에서 **Google Calendar**를 찾습니다.
 3. **Connect**를 클릭하고 OAuth 과정을 완료합니다.
 4. 캘린더 및 연락처 접근 권한을 허용합니다.
diff --git a/docs/ko/enterprise/integrations/google_sheets.mdx b/docs/ko/enterprise/integrations/google_sheets.mdx
index 67c35f0c0..5b1df0d64 100644
--- a/docs/ko/enterprise/integrations/google_sheets.mdx
+++ b/docs/ko/enterprise/integrations/google_sheets.mdx
@@ -13,7 +13,7 @@ mode: "wide"
 
 Google Sheets 통합을 사용하기 전에 다음을 확인하세요:
 
-- 활성 구독이 되어 있는 [CrewAI Enterprise](https://app.crewai.com) 계정
+- 활성 구독이 되어 있는 [CrewAI AMP](https://app.crewai.com) 계정
 - Google Sheets에 액세스할 수 있는 Google 계정
 - [통합 페이지](https://app.crewai.com/crewai_plus/connectors)를 통해 Google 계정 연결
 - 데이터 작업을 위한 올바른 열 헤더가 있는 스프레드시트
@@ -22,7 +22,7 @@ Google Sheets 통합을 사용하기 전에 다음을 확인하세요:
 
 ### 1. Google 계정 연결하기
 
-1. [CrewAI Enterprise Integrations](https://app.crewai.com/crewai_plus/connectors)로 이동합니다.
+1. [CrewAI AMP Integrations](https://app.crewai.com/crewai_plus/connectors)로 이동합니다.
 2. 인증 통합 섹션에서 **Google Sheets**를 찾습니다.
 3. **Connect**를 클릭하고 OAuth 흐름을 완료합니다.
 4. 스프레드시트 접근에 필요한 권한을 허용합니다.
diff --git a/docs/ko/enterprise/integrations/hubspot.mdx b/docs/ko/enterprise/integrations/hubspot.mdx
index aadd2ce5e..132001650 100644
--- a/docs/ko/enterprise/integrations/hubspot.mdx
+++ b/docs/ko/enterprise/integrations/hubspot.mdx
@@ -13,7 +13,7 @@ mode: "wide"
 
 HubSpot 통합을 사용하기 전에 다음을 확인하세요.
 
-- 활성 구독이 있는 [CrewAI Enterprise](https://app.crewai.com) 계정
+- 활성 구독이 있는 [CrewAI AMP](https://app.crewai.com) 계정
 - 적절한 권한이 있는 HubSpot 계정
 - [통합 페이지](https://app.crewai.com/crewai_plus/connectors)를 통해 HubSpot 계정이 연결되어 있음
 
@@ -21,7 +21,7 @@ HubSpot 통합을 사용하기 전에 다음을 확인하세요.
 
 ### 1. HubSpot 계정 연결하기
 
-1. [CrewAI Enterprise Integrations](https://app.crewai.com/crewai_plus/connectors)로 이동합니다.
+1. [CrewAI AMP Integrations](https://app.crewai.com/crewai_plus/connectors)로 이동합니다.
 2. 인증 통합 섹션에서 **HubSpot**을 찾습니다.
 3. **Connect**를 클릭하고 OAuth 플로우를 완료합니다.
 4. 회사 및 연락처 관리를 위한 필요한 권한을 부여합니다.
diff --git a/docs/ko/enterprise/integrations/jira.mdx b/docs/ko/enterprise/integrations/jira.mdx
index fc28d5e37..64fc50334 100644
--- a/docs/ko/enterprise/integrations/jira.mdx
+++ b/docs/ko/enterprise/integrations/jira.mdx
@@ -13,7 +13,7 @@ mode: "wide"
 
 Jira 통합을 사용하기 전에 다음을 준비하세요:
 
-- 활성 구독이 있는 [CrewAI Enterprise](https://app.crewai.com) 계정
+- 활성 구독이 있는 [CrewAI AMP](https://app.crewai.com) 계정
 - 적절한 프로젝트 권한이 있는 Jira 계정
 - [통합 페이지](https://app.crewai.com/crewai_plus/connectors)를 통해 Jira 계정 연결
 
@@ -21,7 +21,7 @@ Jira 통합을 사용하기 전에 다음을 준비하세요:
 
 ### 1. Jira 계정 연결하기
 
-1. [CrewAI Enterprise Integrations](https://app.crewai.com/crewai_plus/connectors)로 이동합니다.
+1. [CrewAI AMP Integrations](https://app.crewai.com/crewai_plus/connectors)로 이동합니다.
 2. **Jira**를 인증 통합 섹션에서 찾습니다.
 3. **Connect**를 클릭하고 OAuth 절차를 완료합니다.
 4. 이슈 및 프로젝트 관리를 위한 필요한 권한을 부여합니다.
diff --git a/docs/ko/enterprise/integrations/linear.mdx b/docs/ko/enterprise/integrations/linear.mdx
index 9ee67d624..f81459763 100644
--- a/docs/ko/enterprise/integrations/linear.mdx
+++ b/docs/ko/enterprise/integrations/linear.mdx
@@ -13,7 +13,7 @@ mode: "wide"
 
 Linear 통합을 사용하기 전에 다음을 확인하세요:
 
-- 활성 구독이 있는 [CrewAI Enterprise](https://app.crewai.com) 계정
+- 활성 구독이 있는 [CrewAI AMP](https://app.crewai.com) 계정
 - 적절한 워크스페이스 권한이 있는 Linear 계정
 - [통합 페이지](https://app.crewai.com/crewai_plus/connectors)에서 Linear 계정 연결
 
@@ -21,7 +21,7 @@ Linear 통합을 사용하기 전에 다음을 확인하세요:
 
 ### 1. Linear 계정 연결하기
 
-1. [CrewAI Enterprise Integrations](https://app.crewai.com/crewai_plus/connectors)로 이동합니다.
+1. [CrewAI AMP Integrations](https://app.crewai.com/crewai_plus/connectors)로 이동합니다.
 2. 인증 통합( Authentication Integrations ) 섹션에서 **Linear**를 찾습니다.
 3. **Connect**를 클릭하고 OAuth 절차를 완료합니다.
 4. 이슈 및 프로젝트 관리를 위한 필수 권한을 부여합니다.
diff --git a/docs/ko/enterprise/integrations/notion.mdx b/docs/ko/enterprise/integrations/notion.mdx
index 9d399beae..04da69150 100644
--- a/docs/ko/enterprise/integrations/notion.mdx
+++ b/docs/ko/enterprise/integrations/notion.mdx
@@ -13,7 +13,7 @@ mode: "wide"
 
 Notion 통합을 사용하기 전에 다음을 확인하세요:
 
-- 활성 구독이 있는 [CrewAI Enterprise](https://app.crewai.com) 계정
+- 활성 구독이 있는 [CrewAI AMP](https://app.crewai.com) 계정
 - 적절한 워크스페이스 권한이 있는 Notion 계정
 - [통합 페이지](https://app.crewai.com/crewai_plus/connectors)를 통해 Notion 계정을 연결함
 
@@ -21,7 +21,7 @@ Notion 통합을 사용하기 전에 다음을 확인하세요:
 
 ### 1. Notion 계정 연결하기
 
-1. [CrewAI Enterprise Integrations](https://app.crewai.com/crewai_plus/connectors)로 이동합니다.
+1. [CrewAI AMP Integrations](https://app.crewai.com/crewai_plus/connectors)로 이동합니다.
 2. 인증 통합(Auhtentication Integrations) 섹션에서 **Notion**을(를) 찾습니다.
 3. **Connect**를 클릭하고 OAuth 플로우를 완료합니다.
 4. 페이지 및 데이터베이스 관리를 위한 필요한 권한을 부여합니다.
diff --git a/docs/ko/enterprise/integrations/salesforce.mdx b/docs/ko/enterprise/integrations/salesforce.mdx
index 25cad7594..e2fb2b5af 100644
--- a/docs/ko/enterprise/integrations/salesforce.mdx
+++ b/docs/ko/enterprise/integrations/salesforce.mdx
@@ -13,7 +13,7 @@ mode: "wide"
 
 Salesforce 통합을 사용하기 전에 다음을 확인하세요:
 
-- 활성 구독이 있는 [CrewAI Enterprise](https://app.crewai.com) 계정
+- 활성 구독이 있는 [CrewAI AMP](https://app.crewai.com) 계정
 - 적절한 권한이 있는 Salesforce 계정
 - [통합 페이지](https://app.crewai.com/integrations)를 통해 Salesforce 계정 연결
 
diff --git a/docs/ko/enterprise/integrations/shopify.mdx b/docs/ko/enterprise/integrations/shopify.mdx
index e801af9fa..a7a77a3f3 100644
--- a/docs/ko/enterprise/integrations/shopify.mdx
+++ b/docs/ko/enterprise/integrations/shopify.mdx
@@ -13,7 +13,7 @@ mode: "wide"
 
 Shopify 연동을 사용하기 전에 다음을 확인하세요:
 
-- 활성 구독이 있는 [CrewAI Enterprise](https://app.crewai.com) 계정
+- 활성 구독이 있는 [CrewAI AMP](https://app.crewai.com) 계정
 - 적절한 관리자 권한이 있는 Shopify 스토어
 - [통합 페이지](https://app.crewai.com/integrations)를 통해 Shopify 스토어 연결
 
diff --git a/docs/ko/enterprise/integrations/slack.mdx b/docs/ko/enterprise/integrations/slack.mdx
index e920c84d7..e9e0401d9 100644
--- a/docs/ko/enterprise/integrations/slack.mdx
+++ b/docs/ko/enterprise/integrations/slack.mdx
@@ -13,7 +13,7 @@ mode: "wide"
 
 Slack 통합을 사용하기 전에 다음을 확인하십시오:
 
-- 활성 구독이 있는 [CrewAI Enterprise](https://app.crewai.com) 계정
+- 활성 구독이 있는 [CrewAI AMP](https://app.crewai.com) 계정
 - 적절한 권한이 있는 Slack 워크스페이스
 - [통합 페이지](https://app.crewai.com/integrations)를 통해 Slack 워크스페이스를 연결함
 
diff --git a/docs/ko/enterprise/integrations/stripe.mdx b/docs/ko/enterprise/integrations/stripe.mdx
index 8918b13f2..05309087c 100644
--- a/docs/ko/enterprise/integrations/stripe.mdx
+++ b/docs/ko/enterprise/integrations/stripe.mdx
@@ -13,7 +13,7 @@ mode: "wide"
 
 Stripe 통합을 사용하기 전에 다음 사항을 확인하세요:
 
-- 활성 구독이 있는 [CrewAI Enterprise](https://app.crewai.com) 계정
+- 활성 구독이 있는 [CrewAI AMP](https://app.crewai.com) 계정
 - 적절한 API 권한이 있는 Stripe 계정
 - [통합 페이지](https://app.crewai.com/integrations)를 통해 Stripe 계정 연결
 
diff --git a/docs/ko/enterprise/integrations/zendesk.mdx b/docs/ko/enterprise/integrations/zendesk.mdx
index e326aed8c..87e5b7f11 100644
--- a/docs/ko/enterprise/integrations/zendesk.mdx
+++ b/docs/ko/enterprise/integrations/zendesk.mdx
@@ -13,7 +13,7 @@ mode: "wide"
 
 Zendesk 통합을 사용하기 전에 다음을 확인하세요.
 
-- 활성 구독이 있는 [CrewAI Enterprise](https://app.crewai.com) 계정
+- 활성 구독이 있는 [CrewAI AMP](https://app.crewai.com) 계정
 - 적절한 API 권한이 있는 Zendesk 계정
 - [통합 페이지](https://app.crewai.com/integrations)를 통해 Zendesk 계정 연결
 
diff --git a/docs/ko/enterprise/introduction.mdx b/docs/ko/enterprise/introduction.mdx
index e9804d395..fdc270eff 100644
--- a/docs/ko/enterprise/introduction.mdx
+++ b/docs/ko/enterprise/introduction.mdx
@@ -7,13 +7,13 @@ mode: "wide"
 
 ## 소개
 
-CrewAI Enterprise는 프로덕션 환경에서 crew와 agent를 배포, 모니터링, 확장할 수 있는 플랫폼을 제공합니다.
+CrewAI AMP는 프로덕션 환경에서 crew와 agent를 배포, 모니터링, 확장할 수 있는 플랫폼을 제공합니다.
 
 <Frame>
-  <img src="/images/enterprise/crewai-enterprise-dashboard.png" alt="CrewAI Enterprise Dashboard" />
+  <img src="/images/enterprise/crewai-enterprise-dashboard.png" alt="CrewAI AMP Dashboard" />
 </Frame>
 
-CrewAI Enterprise는 오픈 소스 프레임워크의 강력함에 프로덕션 배포, 협업, 확장성을 위한 기능을 더했습니다. crew를 관리형 인프라에 배포하고, 실행을 실시간으로 모니터링하세요.
+CrewAI AMP는 오픈 소스 프레임워크의 강력함에 프로덕션 배포, 협업, 확장성을 위한 기능을 더했습니다. crew를 관리형 인프라에 배포하고, 실행을 실시간으로 모니터링하세요.
 
 ## 주요 기능
 
diff --git a/docs/ko/enterprise/resources/frequently-asked-questions.mdx b/docs/ko/enterprise/resources/frequently-asked-questions.mdx
index c0e6cfd53..f26863016 100644
--- a/docs/ko/enterprise/resources/frequently-asked-questions.mdx
+++ b/docs/ko/enterprise/resources/frequently-asked-questions.mdx
@@ -1,6 +1,6 @@
 ---
 title: 자주 묻는 질문
-description: "CrewAI Enterprise에 대한 자주 묻는 질문"
+description: "CrewAI AMP에 대한 자주 묻는 질문"
 icon: "circle-question"
 mode: "wide"
 ---
diff --git a/docs/ko/installation.mdx b/docs/ko/installation.mdx
index 04c92c92d..ab7051d40 100644
--- a/docs/ko/installation.mdx
+++ b/docs/ko/installation.mdx
@@ -161,7 +161,7 @@ CrewAI는 의존성 관리와 패키지 처리를 위해 `uv`를 사용합니다
 <Note type="info">
 팀과 조직을 위해, CrewAI는 설치 복잡성을 없애는 엔터프라이즈 배포 옵션을 제공합니다:
 
-### CrewAI Enterprise (SaaS)
+### CrewAI AMP (SaaS)
 - 설치가 전혀 필요하지 않습니다 - [app.crewai.com](https://app.crewai.com)에서 무료로 가입하세요
 - 자동 업데이트 및 유지 보수
 - 관리형 인프라 및 확장성 지원
diff --git a/docs/ko/learn/human-input-on-execution.mdx b/docs/ko/learn/human-input-on-execution.mdx
index 8665652a1..095928f72 100644
--- a/docs/ko/learn/human-input-on-execution.mdx
+++ b/docs/ko/learn/human-input-on-execution.mdx
@@ -1,7 +1,7 @@
 ---
 title: 실행 중 인간 입력
 description: 복잡한 의사결정 과정에서 실행 중 CrewAI와 인간 입력을 통합하고, 에이전트의 속성과 도구의 모든 기능을 활용하는 방법.
-icon: user-check
+icon: user-plus
 mode: "wide"
 ---
 
diff --git a/docs/ko/learn/llm-selection-guide.mdx b/docs/ko/learn/llm-selection-guide.mdx
index 38ba27daf..7b2997d64 100644
--- a/docs/ko/learn/llm-selection-guide.mdx
+++ b/docs/ko/learn/llm-selection-guide.mdx
@@ -394,7 +394,7 @@ tech_writer = Agent(
   
   <Step title="엔터프라이즈 테스트로 검증" icon="test-tube">
     **agent를 프로덕션에 배포한 후:**
-    - [CrewAI Enterprise platform](https://app.crewai.com)을 활용하여 모델 선택을 A/B 테스트하세요
+    - [CrewAI AMP platform](https://app.crewai.com)을 활용하여 모델 선택을 A/B 테스트하세요
     - 실제 입력으로 여러 번 반복 테스트하여 일관성과 성능을 측정하세요
     - 최적화된 셋업 전반의 비용과 성능을 비교하세요
     - 팀과 결과를 공유하여 협업 의사결정을 지원하세요
@@ -541,7 +541,7 @@ tech_writer = Agent(
 
 ### 엔터프라이즈급 모델 검증
 
-LLM 선택을 최적화하고자 하는 팀을 위해 **CrewAI Enterprise 플랫폼**은 기본적인 CLI 테스트를 훨씬 능가하는 정교한 테스트 기능을 제공합니다. 이 플랫폼은 데이터 기반의 LLM 전략 의사결정을 지원하는 종합적인 모델 평가를 가능하게 합니다.
+LLM 선택을 최적화하고자 하는 팀을 위해 **CrewAI AMP 플랫폼**은 기본적인 CLI 테스트를 훨씬 능가하는 정교한 테스트 기능을 제공합니다. 이 플랫폼은 데이터 기반의 LLM 전략 의사결정을 지원하는 종합적인 모델 평가를 가능하게 합니다.
 
 <Frame>
   ![엔터프라이즈 테스트 인터페이스](/images/enterprise/enterprise-testing.png)
diff --git a/docs/ko/observability/truefoundry.mdx b/docs/ko/observability/truefoundry.mdx
new file mode 100644
index 000000000..bc41cc624
--- /dev/null
+++ b/docs/ko/observability/truefoundry.mdx
@@ -0,0 +1,147 @@
+---
+title: TrueFoundry Integration
+icon: chart-line
+mode: "wide"
+---
+
+TrueFoundry provides an enterprise-ready [AI Gateway](https://www.truefoundry.com/ai-gateway) which can integrate with agentic frameworks like CrewAI and provides governance and observability for your AI Applications. TrueFoundry AI Gateway serves as a unified interface for LLM access, providing:
+
+- **Unified API Access**: Connect to 250+ LLMs (OpenAI, Claude, Gemini, Groq, Mistral) through one API
+- **Low Latency**: Sub-3ms internal latency with intelligent routing and load balancing  
+- **Enterprise Security**: SOC 2, HIPAA, GDPR compliance with RBAC and audit logging
+- **Quota and cost management**: Token-based quotas, rate limiting, and comprehensive usage tracking
+- **Observability**: Full request/response logging, metrics, and traces with customizable retention
+
+## How TrueFoundry Integrates with CrewAI
+
+
+### Installation & Setup
+
+<Steps>
+<Step title="Install CrewAI">
+```bash
+pip install crewai
+```
+</Step>
+
+<Step title="Get TrueFoundry Access Token">
+1. Sign up for a [TrueFoundry account](https://www.truefoundry.com/register)
+2. Follow the steps here in [Quick start](https://docs.truefoundry.com/gateway/quick-start)
+</Step>
+
+<Step title="Configure CrewAI with TrueFoundry">
+![TrueFoundry Code Configuration](/images/new-code-snippet.png)
+
+```python
+from crewai import LLM
+
+# Create an LLM instance with TrueFoundry AI Gateway
+truefoundry_llm = LLM(
+    model="openai-main/gpt-4o",  # Similarly, you can call any model from any provider
+    base_url="your_truefoundry_gateway_base_url",
+    api_key="your_truefoundry_api_key"
+)
+
+# Use in your CrewAI agents
+from crewai import Agent
+
+@agent
+def researcher(self) -> Agent:
+    return Agent(
+        config=self.agents_config['researcher'],
+        llm=truefoundry_llm,
+        verbose=True
+    )
+```
+</Step>
+</Steps>
+
+### Complete CrewAI Example
+
+```python
+from crewai import Agent, Task, Crew, LLM
+
+# Configure LLM with TrueFoundry
+llm = LLM(
+    model="openai-main/gpt-4o",
+    base_url="your_truefoundry_gateway_base_url", 
+    api_key="your_truefoundry_api_key"
+)
+
+# Create agents
+researcher = Agent(
+    role='Research Analyst',
+    goal='Conduct detailed market research',
+    backstory='Expert market analyst with attention to detail',
+    llm=llm,
+    verbose=True
+)
+
+writer = Agent(
+    role='Content Writer', 
+    goal='Create comprehensive reports',
+    backstory='Experienced technical writer',
+    llm=llm,
+    verbose=True
+)
+
+# Create tasks
+research_task = Task(
+    description='Research AI market trends for 2024',
+    agent=researcher,
+    expected_output='Comprehensive research summary'
+)
+
+writing_task = Task(
+    description='Create a market research report',
+    agent=writer,
+    expected_output='Well-structured report with insights',
+    context=[research_task]
+)
+
+# Create and execute crew
+crew = Crew(
+    agents=[researcher, writer],
+    tasks=[research_task, writing_task],
+    verbose=True
+)
+
+result = crew.kickoff()
+```
+
+### Observability and Governance
+
+Monitor your CrewAI agents through TrueFoundry's metrics tab:
+![TrueFoundry metrics](/images/gateway-metrics.png)
+
+With Truefoundry's AI gateway, you can monitor and analyze:
+
+- **Performance Metrics**: Track key latency metrics like Request Latency, Time to First Token (TTFS), and Inter-Token Latency (ITL) with P99, P90, and P50 percentiles
+- **Cost and Token Usage**: Gain visibility into your application's costs with detailed breakdowns of input/output tokens and the associated expenses for each model
+- **Usage Patterns**: Understand how your application is being used with detailed analytics on user activity, model distribution, and team-based usage
+- **Rate limit and Load balancing**: You can set up rate limiting, load balancing and fallback for your models
+
+## Tracing
+
+For a more detailed understanding on tracing, please see [getting-started-tracing](https://docs.truefoundry.com/docs/tracing/tracing-getting-started).For tracing, you can add the Traceloop SDK: 
+For tracing, you can add the Traceloop SDK: 
+
+```bash
+pip install traceloop-sdk
+```
+
+```python
+from traceloop.sdk import Traceloop
+
+# Initialize enhanced tracing
+Traceloop.init(
+    api_endpoint="https://your-truefoundry-endpoint/api/tracing",
+    headers={
+        "Authorization": f"Bearer {your_truefoundry_pat_token}",
+        "TFY-Tracing-Project": "your_project_name",
+    },
+)
+```
+
+This provides additional trace correlation across your entire CrewAI workflow.
+![TrueFoundry CrewAI Tracing](/images/tracing_crewai.png)
\ No newline at end of file
diff --git a/docs/ko/quickstart.mdx b/docs/ko/quickstart.mdx
index 621ad5e32..0b55915eb 100644
--- a/docs/ko/quickstart.mdx
+++ b/docs/ko/quickstart.mdx
@@ -209,9 +209,9 @@ mode: "wide"
   </Step>
 
   <Step title="엔터프라이즈 대안: Crew Studio에서 생성">
-  CrewAI Enterprise 사용자는 코드를 작성하지 않고도 동일한 crew를 생성할 수 있습니다:
+  CrewAI AMP 사용자는 코드를 작성하지 않고도 동일한 crew를 생성할 수 있습니다:
 
-  1. CrewAI Enterprise 계정에 로그인하세요([app.crewai.com](https://app.crewai.com)에서 무료 계정 만들기)
+  1. CrewAI AMP 계정에 로그인하세요([app.crewai.com](https://app.crewai.com)에서 무료 계정 만들기)
   2. Crew Studio 열기
   3. 구현하려는 자동화 내용을 입력하세요
   4. 미션을 시각적으로 생성하고 순차적으로 연결하세요
@@ -219,8 +219,8 @@ mode: "wide"
 
   ![Crew Studio Quickstart](/images/enterprise/crew-studio-interface.png)
 
-  <Card title="CrewAI Enterprise 체험하기" icon="rocket" href="https://app.crewai.com">
-    CrewAI Enterprise에서 무료 계정을 시작하세요
+  <Card title="CrewAI AMP 체험하기" icon="rocket" href="https://app.crewai.com">
+    CrewAI AMP에서 무료 계정을 시작하세요
   </Card>
   </Step>
   <Step title="최종 보고서 확인하기">
@@ -340,9 +340,9 @@ email_summarizer_task:
 
 ## Crew 배포하기
 
-production 환경에 crew를 배포하는 가장 쉬운 방법은 [CrewAI Enterprise](http://app.crewai.com)를 통해서입니다.
+production 환경에 crew를 배포하는 가장 쉬운 방법은 [CrewAI AMP](http://app.crewai.com)를 통해서입니다.
 
-CLI를 사용하여 [CrewAI Enterprise](http://app.crewai.com)에 crew를 배포하는 단계별 시연은 이 영상 튜토리얼을 참고하세요.
+CLI를 사용하여 [CrewAI AMP](http://app.crewai.com)에 crew를 배포하는 단계별 시연은 이 영상 튜토리얼을 참고하세요.
 
 <iframe
   className="w-full aspect-video rounded-xl"
@@ -359,7 +359,7 @@ CLI를 사용하여 [CrewAI Enterprise](http://app.crewai.com)에 crew를 배포
     icon="rocket"
     href="http://app.crewai.com"
   >
-    CrewAI Enterprise로 시작하여 몇 번의 클릭만으로 production 환경에 crew를 배포하세요.
+    CrewAI AMP로 시작하여 몇 번의 클릭만으로 production 환경에 crew를 배포하세요.
   </Card>
   <Card
     title="커뮤니티 참여하기"
diff --git a/docs/ko/tools/cloud-storage/bedrockinvokeagenttool.mdx b/docs/ko/tools/cloud-storage/bedrockinvokeagenttool.mdx
deleted file mode 100644
index cdb9f4cd4..000000000
--- a/docs/ko/tools/cloud-storage/bedrockinvokeagenttool.mdx
+++ /dev/null
@@ -1,188 +0,0 @@
----
-title: Bedrock Invoke Agent 도구
-description: CrewAI 에이전트가 Amazon Bedrock 에이전트를 호출하고, 워크플로우 내에서 그 기능을 활용할 수 있도록 합니다
-icon: aws
-mode: "wide"
----
-
-# `BedrockInvokeAgentTool`
-
-`BedrockInvokeAgentTool`은 CrewAI agent가 Amazon Bedrock Agent를 호출하여 워크플로우 내에서 해당 기능을 활용할 수 있도록 해줍니다.
-
-## 설치
-
-```bash
-uv pip install 'crewai[tools]'
-```
-
-## 요구 사항
-
-- AWS 자격 증명이 구성되어 있어야 합니다(AWS CLI 또는 환경 변수 사용)
-- `boto3` 및 `python-dotenv` 패키지
-- Amazon Bedrock Agents에 대한 액세스 권한
-
-## 사용법
-
-CrewAI agent와 함께 이 도구를 사용하는 방법은 다음과 같습니다:
-
-```python {2, 4-8}
-from crewai import Agent, Task, Crew
-from crewai_tools.aws.bedrock.agents.invoke_agent_tool import BedrockInvokeAgentTool
-
-# Initialize the tool
-agent_tool = BedrockInvokeAgentTool(
-    agent_id="your-agent-id",
-    agent_alias_id="your-agent-alias-id"
-)
-
-# Create a CrewAI agent that uses the tool
-aws_expert = Agent(
-    role='AWS Service Expert',
-    goal='Help users understand AWS services and quotas',
-    backstory='I am an expert in AWS services and can provide detailed information about them.',
-    tools=[agent_tool],
-    verbose=True
-)
-
-# Create a task for the agent
-quota_task = Task(
-    description="Find out the current service quotas for EC2 in us-west-2 and explain any recent changes.",
-    agent=aws_expert
-)
-
-# Create a crew with the agent
-crew = Crew(
-    agents=[aws_expert],
-    tasks=[quota_task],
-    verbose=2
-)
-
-# Run the crew
-result = crew.kickoff()
-print(result)
-```
-
-## 도구 인수
-
-| 인수 | 타입 | 필수 여부 | 기본값 | 설명 |
-|:---------|:-----|:---------|:--------|:------------|
-| **agent_id** | `str` | 예 | 없음 | Bedrock agent의 고유 식별자 |
-| **agent_alias_id** | `str` | 예 | 없음 | agent alias의 고유 식별자 |
-| **session_id** | `str` | 아니오 | timestamp | 세션의 고유 식별자 |
-| **enable_trace** | `bool` | 아니오 | False | 디버깅을 위한 trace 활성화 여부 |
-| **end_session** | `bool` | 아니오 | False | 호출 후 세션 종료 여부 |
-| **description** | `str` | 아니오 | 없음 | 도구에 대한 사용자 지정 설명 |
-
-## 환경 변수
-
-```bash
-BEDROCK_AGENT_ID=your-agent-id           # Alternative to passing agent_id
-BEDROCK_AGENT_ALIAS_ID=your-agent-alias-id # Alternative to passing agent_alias_id
-AWS_REGION=your-aws-region               # Defaults to us-west-2
-AWS_ACCESS_KEY_ID=your-access-key        # Required for AWS authentication
-AWS_SECRET_ACCESS_KEY=your-secret-key    # Required for AWS authentication
-```
-
-## 고급 사용법
-
-### 세션 관리가 포함된 다중 에이전트 워크플로우
-
-```python {2, 4-22}
-from crewai import Agent, Task, Crew, Process
-from crewai_tools.aws.bedrock.agents.invoke_agent_tool import BedrockInvokeAgentTool
-
-# Initialize tools with session management
-initial_tool = BedrockInvokeAgentTool(
-    agent_id="your-agent-id",
-    agent_alias_id="your-agent-alias-id",
-    session_id="custom-session-id"
-)
-
-followup_tool = BedrockInvokeAgentTool(
-    agent_id="your-agent-id",
-    agent_alias_id="your-agent-alias-id",
-    session_id="custom-session-id"
-)
-
-final_tool = BedrockInvokeAgentTool(
-    agent_id="your-agent-id",
-    agent_alias_id="your-agent-alias-id",
-    session_id="custom-session-id",
-    end_session=True
-)
-
-# Create agents for different stages
-researcher = Agent(
-    role='AWS Service Researcher',
-    goal='Gather information about AWS services',
-    backstory='I am specialized in finding detailed AWS service information.',
-    tools=[initial_tool]
-)
-
-analyst = Agent(
-    role='Service Compatibility Analyst',
-    goal='Analyze service compatibility and requirements',
-    backstory='I analyze AWS services for compatibility and integration possibilities.',
-    tools=[followup_tool]
-)
-
-summarizer = Agent(
-    role='Technical Documentation Writer',
-    goal='Create clear technical summaries',
-    backstory='I specialize in creating clear, concise technical documentation.',
-    tools=[final_tool]
-)
-
-# Create tasks
-research_task = Task(
-    description="Find all available AWS services in us-west-2 region.",
-    agent=researcher
-)
-
-analysis_task = Task(
-    description="Analyze which services support IPv6 and their implementation requirements.",
-    agent=analyst
-)
-
-summary_task = Task(
-    description="Create a summary of IPv6-compatible services and their key features.",
-    agent=summarizer
-)
-
-# Create a crew with the agents and tasks
-crew = Crew(
-    agents=[researcher, analyst, summarizer],
-    tasks=[research_task, analysis_task, summary_task],
-    process=Process.sequential,
-    verbose=2
-)
-
-# Run the crew
-result = crew.kickoff()
-```
-
-## 사용 사례
-
-### 하이브리드 멀티 에이전트 협업
-- CrewAI 에이전트가 AWS에서 서비스로 실행되는 관리형 Bedrock 에이전트와 협력하는 워크플로우를 생성합니다.
-- 민감한 데이터 처리가 AWS 환경 내에서 이루어지면서, 다른 에이전트는 외부에서 작동하는 시나리오를 구현합니다.
-- 온프레미스 CrewAI 에이전트와 클라우드 기반 Bedrock 에이전트를 연결하여 분산 지능 워크플로우를 실현합니다.
-
-### 데이터 주권 및 준수
-- 데이터에 민감한 에이전틱 워크플로우를 AWS 환경 내에서 유지하면서, 외부 CrewAI 에이전트가 작업을 오케스트레이션할 수 있도록 허용합니다
-- 민감한 정보를 오직 귀하의 AWS 계정 내에서 처리함으로써 데이터 보관 위치 요건을 준수합니다
-- 일부 에이전트가 귀 조직의 비공개 데이터에 접근할 수 없는 안전한 다중 에이전트 협업을 가능하게 합니다
-
-### 원활한 AWS 서비스 통합
-- 복잡한 통합 코드를 작성하지 않고도 Amazon Bedrock Actions를 통해 모든 AWS 서비스에 액세스할 수 있습니다.
-- CrewAI 에이전트가 자연어 요청을 통해 AWS 서비스와 상호작용할 수 있습니다.
-- Bedrock Knowledge Bases, Lambda 등과 같은 AWS 서비스와 상호작용할 수 있도록 사전 구축된 Bedrock 에이전트 기능을 활용할 수 있습니다.
-
-### 확장 가능한 하이브리드 에이전트 아키텍처
-- 계산 집약적인 작업은 관리형 Bedrock 에이전트에 오프로드하고, 경량 작업은 CrewAI에서 실행
-- 로컬 CrewAI 에이전트와 클라우드 기반 Bedrock 에이전트 간에 워크로드를 분산하여 에이전트 처리를 확장
-
-### 조직 간 에이전트 협업
-- 귀 조직의 CrewAI 에이전트와 파트너 조직의 Bedrock 에이전트 간의 안전한 협업을 지원합니다
-- 민감한 데이터를 노출하지 않고도 Bedrock 에이전트의 외부 전문 지식을 워크플로우에 통합할 수 있습니다
-- 보안 및 데이터 통제를 유지하면서 조직 경계를 넘는 에이전트 생태계를 구축합니다
\ No newline at end of file
diff --git a/docs/ko/tools/tool-integrations/overview.mdx b/docs/ko/tools/tool-integrations/overview.mdx
new file mode 100644
index 000000000..6f59ca471
--- /dev/null
+++ b/docs/ko/tools/tool-integrations/overview.mdx
@@ -0,0 +1,31 @@
+---
+title: Overview
+description: Integrations for deploying and automating crews with external platforms
+icon: face-smile
+mode: "wide"
+---
+
+## Available Integrations
+
+<CardGroup cols={2}>
+  <Card
+    title="Bedrock Invoke Agent Tool"
+    icon="cloud"
+    href="/en/tools/tool-integrations/bedrockinvokeagenttool"
+    color="#0891B2"
+  >
+    Invoke Amazon Bedrock Agents from CrewAI to orchestrate actions across AWS services.
+  </Card>
+
+  <Card
+    title="CrewAI Automation Tool"
+    icon="bolt"
+    href="/en/tools/tool-integrations/crewaiautomationtool"
+    color="#7C3AED"
+  >
+    Automate deployment and operations by integrating CrewAI with external platforms and workflows.
+  </Card>
+</CardGroup>
+
+Use these integrations to connect CrewAI with your infrastructure and workflows.
+
diff --git a/docs/pt-BR/api-reference/introduction.mdx b/docs/pt-BR/api-reference/introduction.mdx
index 5a6cb83f3..6256648ce 100644
--- a/docs/pt-BR/api-reference/introduction.mdx
+++ b/docs/pt-BR/api-reference/introduction.mdx
@@ -1,19 +1,19 @@
 ---
 title: "Introdução"
-description: "Referência completa para a API REST do CrewAI Enterprise"
+description: "Referência completa para a API REST do CrewAI AMP"
 icon: "code"
 mode: "wide"
 ---
 
-# CrewAI Enterprise API
+# CrewAI AMP API
 
-Bem-vindo à referência da API do CrewAI Enterprise. Esta API permite que você interaja programaticamente com seus crews implantados, possibilitando a integração com seus aplicativos, fluxos de trabalho e serviços.
+Bem-vindo à referência da API do CrewAI AMP. Esta API permite que você interaja programaticamente com seus crews implantados, possibilitando a integração com seus aplicativos, fluxos de trabalho e serviços.
 
 ## Início Rápido
 
 <Steps>
   <Step title="Obtenha suas credenciais de API">
-    Navegue até a página de detalhes do seu crew no painel do CrewAI Enterprise e copie seu Bearer Token na aba Status.
+    Navegue até a página de detalhes do seu crew no painel do CrewAI AMP e copie seu Bearer Token na aba Status.
   </Step>
   
   <Step title="Descubra os Inputs Necessários">
@@ -46,7 +46,7 @@ curl -H "Authorization: Bearer YOUR_CREW_TOKEN" \
 | **User Bearer Token** | Acesso com escopo de usuário         | Permissões limitadas, adequado para operações específicas de usuário   |
 
 <Tip>
-Você pode encontrar ambos os tipos de token na aba Status da página de detalhes do seu crew no painel do CrewAI Enterprise.
+Você pode encontrar ambos os tipos de token na aba Status da página de detalhes do seu crew no painel do CrewAI AMP.
 </Tip>
 
 ## URL Base
@@ -82,7 +82,7 @@ A API utiliza códigos de status HTTP padrão:
 ## Testes Interativos
 
 <Info>
-**Por que não há botão "Enviar"?** Como cada usuário do CrewAI Enterprise possui sua própria URL de crew, utilizamos o **modo referência** em vez de um playground interativo para evitar confusão. Isso mostra exatamente como as requisições devem ser feitas, sem botões de envio não funcionais.
+**Por que não há botão "Enviar"?** Como cada usuário do CrewAI AMP possui sua própria URL de crew, utilizamos o **modo referência** em vez de um playground interativo para evitar confusão. Isso mostra exatamente como as requisições devem ser feitas, sem botões de envio não funcionais.
 </Info>
 
 Cada página de endpoint mostra para você:
diff --git a/docs/pt-BR/changelog.mdx b/docs/pt-BR/changelog.mdx
index 419337d15..9642f2cf3 100644
--- a/docs/pt-BR/changelog.mdx
+++ b/docs/pt-BR/changelog.mdx
@@ -4,6 +4,84 @@ description: "Atualizações de produto, melhorias e correções do CrewAI"
 icon: "clock"
 mode: "wide"
 ---
+<Update label="30 set 2025">
+  ## v1.0.0a1
+
+  [Ver release no GitHub](https://github.com/crewAIInc/crewAI/releases/tag/1.0.0a1)
+
+  ## O que mudou
+
+  ### Melhorias e correções principais
+  - Corrigido o controle de permissões do atributo `actions` na configuração de agentes
+  - Fluxos de CI e publicação atualizados para suportar a nova estrutura de monorepo
+  - Migração para Python 3.13 e atualização do metadado dos pacotes
+
+  ### Novos recursos e melhorias
+  - Novos atributos `apps` e `actions` nos agentes para controles avançados em runtime
+  - Repositório `crewai-tools` incorporado ao workspace principal (monorepo)
+  - Versão incrementada para 1.0.0a1 em todos os pacotes (marco alpha)
+
+  ### Limpeza e infraestrutura
+  - Novo pipeline de CI com versionamento fixo e estratégia de publicação
+  - Unificação do código interno para gerenciar múltiplos pacotes
+
+</Update>
+
+<Update label="26 set 2025">
+  ## v0.201.1
+
+  [Ver release no GitHub](https://github.com/crewAIInc/crewAI/releases/tag/0.201.1)
+
+  ## O que mudou
+
+  ### Melhorias e correções principais
+  - Provedor de embeddings Watson renomeado para `watsonx` com prefixos de ambiente atualizados
+  - Compatibilidade do ChromaDB com providers `watsonx` e `voyageai`
+
+  ### Limpeza e descontinuações
+  - Padronização dos prefixos de variáveis de ambiente para todos os providers
+  - Versão do CrewAI atualizada para 0.201.1 com dependências internas revisadas
+
+</Update>
+
+<Update label="24 set 2025">
+  ## v0.201.0
+
+  [Ver release no GitHub](https://github.com/crewAIInc/crewAI/releases/tag/0.201.0)
+
+  ## O que mudou
+
+  ### Melhorias e correções principais
+  - Parâmetro `ready` agora é opcional em `_create_reasoning_plan`
+  - Correções no tratamento de configuração aninhada para embedders
+  - Suporte ao parâmetro `batch_size` para evitar limites de tokens
+  - Corrigido o nome do diretório na documentação do Quickstart
+  - Resolvidos problemas de cache da duração de testes e exportação de eventos
+  - Adicionada lógica de fallback nas configurações de crew
+
+  ### Novos recursos e melhorias
+  - Introduzido gerenciamento de contexto da plataforma thread-safe
+  - Adicionado comando `crewai uv` para executar `uv` diretamente via CLI
+  - Possibilidade de marcar traces como falhas para fluxos de observabilidade
+  - Suporte a tipos de embedding personalizados e migração entre providers
+  - ChromaDB atualizado para v1.1.0 com correções de compatibilidade e melhorias de tipagem
+  - Validações compatíveis com Pydantic e reorganização dos grupos de dependências
+
+  ### Documentação e guias
+  - Cobertura do changelog atualizada para os releases 0.193.x
+  - Documentado suporte a metadados de eventos no LLM Guardrail
+  - Orientações adicionais sobre fallback e visibilidade de parâmetros de configuração
+
+  ### Limpeza e descontinuações
+  - Resolvidos problemas de Ruff e MyPy em diversos módulos
+  - Melhorias nas anotações de tipos e consolidação de utilidades
+  - Descontinuação de utilitários antigos em favor de importações compatíveis com Pydantic
+
+  ### Contribuidores
+  - Novo contribuidor: @qizwiz (primeira contribuição)
+
+</Update>
+
 
 <Update label="20 set 2025">
   ## v0.193.2
diff --git a/docs/pt-BR/concepts/agents.mdx b/docs/pt-BR/concepts/agents.mdx
index bda88e74b..54560a0a5 100644
--- a/docs/pt-BR/concepts/agents.mdx
+++ b/docs/pt-BR/concepts/agents.mdx
@@ -20,7 +20,7 @@ Pense em um agente como um membro especializado da equipe com habilidades, compe
 </Tip>
 
 <Note type="info" title="Aprimoramento Empresarial: Construtor Visual de Agentes">
-O CrewAI Enterprise inclui um Construtor Visual de Agentes, que simplifica a criação e configuração de agentes sem escrever código. Projete seus agentes visualmente e teste-os em tempo real.
+O CrewAI AMP inclui um Construtor Visual de Agentes, que simplifica a criação e configuração de agentes sem escrever código. Projete seus agentes visualmente e teste-os em tempo real.
 
 ![Visual Agent Builder Screenshot](/images/enterprise/crew-studio-interface.png)
 
diff --git a/docs/pt-BR/concepts/cli.mdx b/docs/pt-BR/concepts/cli.mdx
index 63731e85b..7c47c8f75 100644
--- a/docs/pt-BR/concepts/cli.mdx
+++ b/docs/pt-BR/concepts/cli.mdx
@@ -4,7 +4,7 @@ description: Aprenda a usar o CLI do CrewAI para interagir com o CrewAI.
 icon: terminal
 mode: "wide"
 ---
-<Warning>A partir da versão 0.140.0, a plataforma CrewAI Enterprise iniciou um processo de migração de seu provedor de login. Como resultado, o fluxo de autenticação via CLI foi atualizado. Usuários que utlizam o Google para fazer login, ou que criaram conta após 3 de julho de 2025 não poderão fazer login com versões anteriores da biblioteca `crewai`.</Warning>
+<Warning>A partir da versão 0.140.0, a plataforma CrewAI AMP iniciou um processo de migração de seu provedor de login. Como resultado, o fluxo de autenticação via CLI foi atualizado. Usuários que utlizam o Google para fazer login, ou que criaram conta após 3 de julho de 2025 não poderão fazer login com versões anteriores da biblioteca `crewai`.</Warning>
 
 ## Visão Geral
 
@@ -201,9 +201,9 @@ def crew(self) -> Crew:
 
 ### 10. Deploy
 
-Implemente o crew ou flow no [CrewAI Enterprise](https://app.crewai.com).
+Implemente o crew ou flow no [CrewAI AMP](https://app.crewai.com).
 
-- **Autenticação**: Você precisa estar autenticado para implementar no CrewAI Enterprise.
+- **Autenticação**: Você precisa estar autenticado para implementar no CrewAI AMP.
     Você pode fazer login ou criar uma conta com:
     ```shell Terminal
     crewai login
@@ -218,7 +218,7 @@ Implemente o crew ou flow no [CrewAI Enterprise](https://app.crewai.com).
 
 ### 11. Gerenciamento de Organização
 
-Gerencie suas organizações no CrewAI Enterprise.
+Gerencie suas organizações no CrewAI AMP.
 
 ```shell Terminal
 crewai org [COMMAND] [OPTIONS]
@@ -242,17 +242,17 @@ crewai org switch <organization_id>
 ```
 
 <Note>
-Você deve estar autenticado no CrewAI Enterprise para usar estes comandos de gerenciamento de organização.
+Você deve estar autenticado no CrewAI AMP para usar estes comandos de gerenciamento de organização.
 </Note>
 
 - **Criar um deployment** (continuação):
     - Vincula o deployment ao respectivo repositório remoto do GitHub (normalmente detectado automaticamente).
 
-- **Implantar o Crew**: Depois de autenticado, você pode implantar seu crew ou flow no CrewAI Enterprise.
+- **Implantar o Crew**: Depois de autenticado, você pode implantar seu crew ou flow no CrewAI AMP.
     ```shell Terminal
     crewai deploy push
     ```
-    - Inicia o processo de deployment na plataforma CrewAI Enterprise.
+    - Inicia o processo de deployment na plataforma CrewAI AMP.
     - Após a iniciação bem-sucedida, será exibida a mensagem Deployment created successfully! juntamente com o Nome do Deployment e um Deployment ID (UUID) único.
 
 - **Status do Deployment**: Você pode verificar o status do seu deployment com:
@@ -277,7 +277,7 @@ Você deve estar autenticado no CrewAI Enterprise para usar estes comandos de ge
     ```shell Terminal
     crewai deploy remove
     ```
-    Isto exclui o deployment da plataforma CrewAI Enterprise.
+    Isto exclui o deployment da plataforma CrewAI AMP.
 
 - **Comando de Ajuda**: Você pode obter ajuda sobre o CLI com:
     ```shell Terminal
@@ -285,7 +285,7 @@ Você deve estar autenticado no CrewAI Enterprise para usar estes comandos de ge
     ```
     Isto exibe a mensagem de ajuda para o CLI CrewAI Deploy.
 
-Assista ao vídeo tutorial para uma demonstração passo-a-passo de implantação do seu crew no [CrewAI Enterprise](http://app.crewai.com) usando o CLI.
+Assista ao vídeo tutorial para uma demonstração passo-a-passo de implantação do seu crew no [CrewAI AMP](http://app.crewai.com) usando o CLI.
 
 <iframe
   className="w-full aspect-video rounded-xl"
@@ -351,7 +351,7 @@ crewai config reset
 
 #### Parâmetros de Configuração Disponíveis
 
-- `enterprise_base_url`: URL base da instância CrewAI Enterprise
+- `enterprise_base_url`: URL base da instância CrewAI AMP
 - `oauth2_provider`: Provedor OAuth2 usado para autenticação (ex: workos, okta, auth0)
 - `oauth2_audience`: Valor de audiência OAuth2, tipicamente usado para identificar a API ou recurso de destino
 - `oauth2_client_id`: ID do cliente OAuth2 emitido pelo provedor, usado durante solicitações de autenticação
@@ -368,7 +368,7 @@ Exemplo de saída:
 
 | Parâmetro            | Valor                   | Descrição                                                     |
 | :------------------- | :---------------------- | :------------------------------------------------------------ |
-| enterprise_base_url  | https://app.crewai.com | URL base da instância CrewAI Enterprise                       |
+| enterprise_base_url  | https://app.crewai.com | URL base da instância CrewAI AMP                       |
 | org_name             | Not set                 | Nome da organização atualmente ativa                          |
 | org_uuid             | Not set                 | UUID da organização atualmente ativa                          |
 | oauth2_provider      | workos                  | Provedor OAuth2 (ex.: workos, okta, auth0)                    |
diff --git a/docs/pt-BR/concepts/event-listener.mdx b/docs/pt-BR/concepts/event-listener.mdx
index 616153a0b..184d286ab 100644
--- a/docs/pt-BR/concepts/event-listener.mdx
+++ b/docs/pt-BR/concepts/event-listener.mdx
@@ -20,7 +20,7 @@ O CrewAI utiliza uma arquitetura de event bus para emitir eventos ao longo do ci
 Quando ações específicas ocorrem no CrewAI (como a inicialização de um Crew, um Agent concluindo uma tarefa ou o uso de uma ferramenta), o sistema emite os eventos correspondentes. Você pode registrar handlers para esses eventos para executar código personalizado quando eles acontecerem.
 
 <Note type="info" title="Aprimoramento Enterprise: Prompt Tracing">
-O CrewAI Enterprise fornece o recurso Prompt Tracing, que aproveita o sistema de eventos para rastrear, armazenar e visualizar todos os prompts, respostas e metadados associados. Isso proporciona poderosas capacidades de depuração e transparência nas operações dos seus agentes.
+O CrewAI AMP fornece o recurso Prompt Tracing, que aproveita o sistema de eventos para rastrear, armazenar e visualizar todos os prompts, respostas e metadados associados. Isso proporciona poderosas capacidades de depuração e transparência nas operações dos seus agentes.
 
 ![Prompt Tracing Dashboard](/images/enterprise/traces-overview.png)
 
diff --git a/docs/pt-BR/concepts/tasks.mdx b/docs/pt-BR/concepts/tasks.mdx
index 251a1ee20..153150833 100644
--- a/docs/pt-BR/concepts/tasks.mdx
+++ b/docs/pt-BR/concepts/tasks.mdx
@@ -14,7 +14,7 @@ As tarefas fornecem todos os detalhes necessários para sua execução, como des
 As tarefas dentro do CrewAI podem ser colaborativas, exigindo que múltiplos agentes trabalhem juntos. Isso é gerenciado por meio das propriedades da tarefa e orquestrado pelo processo do Crew, potencializando o trabalho em equipe e a eficiência.
 
 <Note type="info" title="Aprimoramento Empresarial: Construtor Visual de Tarefas">
-O CrewAI Enterprise inclui um Construtor Visual de Tarefas no Crew Studio, que simplifica a criação e o encadeamento de tarefas complexas. Projete seus fluxos de tarefas visualmente e teste-os em tempo real sem necessidade de escrever código.
+O CrewAI AMP inclui um Construtor Visual de Tarefas no Crew Studio, que simplifica a criação e o encadeamento de tarefas complexas. Projete seus fluxos de tarefas visualmente e teste-os em tempo real sem necessidade de escrever código.
 
 ![Task Builder Screenshot](/images/enterprise/crew-studio-interface.png)
 
diff --git a/docs/pt-BR/concepts/tools.mdx b/docs/pt-BR/concepts/tools.mdx
index f196182b0..5681430c9 100644
--- a/docs/pt-BR/concepts/tools.mdx
+++ b/docs/pt-BR/concepts/tools.mdx
@@ -17,7 +17,7 @@ Isso inclui ferramentas do [CrewAI Toolkit](https://github.com/joaomdmoura/crewa
 permitindo desde buscas simples até interações complexas e trabalho em equipe eficiente entre agentes.
 
 <Note type="info" title="Aprimoramento para Empresas: Repositório de Ferramentas">
-O CrewAI Enterprise oferece um Repositório de Ferramentas abrangente, com integrações pré-construídas para sistemas empresariais e APIs comuns. Implemente agentes com ferramentas corporativas em minutos em vez de dias.
+O CrewAI AMP oferece um Repositório de Ferramentas abrangente, com integrações pré-construídas para sistemas empresariais e APIs comuns. Implemente agentes com ferramentas corporativas em minutos em vez de dias.
 
 O Repositório de Ferramentas Empresariais inclui:
 - Conectores pré-construídos para sistemas empresariais populares
diff --git a/docs/pt-BR/enterprise/features/integrations.mdx b/docs/pt-BR/enterprise/features/integrations.mdx
deleted file mode 100644
index 48c286fc8..000000000
--- a/docs/pt-BR/enterprise/features/integrations.mdx
+++ /dev/null
@@ -1,180 +0,0 @@
----
-title: Integrações
-description: "Aplicativos conectados para que seus agentes possam tomar ações."
-icon: "plug"
-mode: "wide"
----
-
-## Visão Geral
-
-Permita que seus agentes autentiquem com qualquer provedor habilitado para OAuth e tomem ações. Do Salesforce e HubSpot ao Google e GitHub, você conta com mais de 16 serviços integrados.
-
-<Frame>
-  ![Integrações](/images/enterprise/crew_connectors.png)
-</Frame>
-
-## Integrações Suportadas
-
-### **Comunicação & Colaboração**
-- **Gmail** - Gerencie e-mails e rascunhos
-- **Slack** - Notificações e alertas do workspace
-- **Microsoft** - Integração com Office 365 e Teams
-
-### **Gerenciamento de Projetos**
-- **Jira** - Rastreamento de issues e gerenciamento de projetos
-- **ClickUp** - Gerenciamento de tarefas e produtividade
-- **Asana** - Coordenação de tarefas e projetos de equipe
-- **Notion** - Gerenciamento de páginas e bases de dados
-- **Linear** - Gerenciamento de projetos de software e bugs
-- **GitHub** - Gerenciamento de repositórios e issues
-
-### **Gestão de Relacionamento com o Cliente**
-- **Salesforce** - Gerenciamento de contas e oportunidades de CRM
-- **HubSpot** - Gestão de pipeline de vendas e contatos
-- **Zendesk** - Administração de chamados de suporte ao cliente
-
-### **Negócios & Finanças**
-- **Stripe** - Processamento de pagamentos e gerenciamento de clientes
-- **Shopify** - Gestão de loja de e-commerce e produtos
-
-### **Produtividade & Armazenamento**
-- **Google Sheets** - Sincronização de dados de planilhas
-- **Google Calendar** - Gerenciamento de eventos e agendas
-- **Box** - Armazenamento de arquivos e gerenciamento de documentos
-
-e mais estão por vir!
-
-## Pré-requisitos
-
-Antes de usar as Integrações de Autenticação, certifique-se de que você possui:
-
-- Uma conta [CrewAI Enterprise](https://app.crewai.com). Você pode começar com uma avaliação gratuita.
-
-## Configurando Integrações
-
-### 1. Conecte sua Conta
-
-1. Acesse o [CrewAI Enterprise](https://app.crewai.com)
-2. Vá até a aba **Integrações** - https://app.crewai.com/crewai_plus/connectors
-3. Clique em **Conectar** no serviço desejado na seção Integrações de Autenticação
-4. Complete o fluxo de autenticação OAuth
-5. Conceda as permissões necessárias para seu caso de uso
-6. Pronto! Obtenha seu Token Enterprise do [CrewAI Enterprise](https://app.crewai.com) na aba **Integration**
-
-<Frame>
-  ![Integrações](/images/enterprise/enterprise_action_auth_token.png)
-</Frame>
-
-### 2. Instale as Ferramentas de Integração
-
-Tudo o que você precisa é da versão mais recente do pacote `crewai-tools`.
-
-```bash
-uv add crewai-tools
-```
-
-## Exemplos de Uso
-
-### Uso Básico
-<Tip>
-  Todos os serviços nos quais você estiver autenticado estarão disponíveis como ferramentas. Portanto, tudo que você precisa fazer é adicionar o `CrewaiEnterpriseTools` ao seu agente e pronto.
-</Tip>
-
-```python
-from crewai import Agent, Task, Crew
-from crewai_tools import CrewaiEnterpriseTools
-
-# Obtenha ferramentas enterprise (a ferramenta Gmail será incluída)
-ferramentas_enterprise = CrewaiEnterpriseTools(
-    enterprise_token="seu_token_enterprise"
-)
-# imprima as ferramentas
-printf(ferramentas_enterprise)
-
-# Crie um agente com capacidades do Gmail
-agente_email = Agent(
-    role="Gerente de E-mails",
-    goal="Gerenciar e organizar comunicações por e-mail",
-    backstory="Um assistente de IA especializado em gestão de e-mails e comunicação.",
-    tools=ferramentas_enterprise
-)
-
-# Tarefa para enviar um e-mail
-tarefa_email = Task(
-    description="Redigir e enviar um e-mail de acompanhamento para john@example.com sobre a atualização do projeto",
-    agent=agente_email,
-    expected_output="Confirmação de que o e-mail foi enviado com sucesso"
-)
-
-# Execute a tarefa
-crew = Crew(
-    agents=[agente_email],
-    tasks=[tarefa_email]
-)
-
-# Execute o crew
-crew.kickoff()
-```
-
-### Filtrando Ferramentas
-
-```python
-from crewai_tools import CrewaiEnterpriseTools
-
-enterprise_tools = CrewaiEnterpriseTools(
-    actions_list=["gmail_find_email"] # apenas a ferramenta gmail_find_email estará disponível
-)
-gmail_tool = enterprise_tools["gmail_find_email"]
-
-agente_gmail = Agent(
-    role="Gerente do Gmail",
-    goal="Gerenciar comunicações e notificações do gmail",
-    backstory="Um assistente de IA que ajuda a coordenar comunicações no gmail.",
-    tools=[gmail_tool]
-)
-
-tarefa_notificacao = Task(
-    description="Encontrar o e-mail de john@example.com",
-    agent=agente_gmail,
-    expected_output="E-mail encontrado de john@example.com"
-)
-
-# Execute a tarefa
-crew = Crew(
-    agents=[agente_gmail],
-    tasks=[tarefa_notificacao]
-)
-```
-
-## Melhores Práticas
-
-### Segurança
-- **Princípio do Menor Privilégio**: Conceda apenas as permissões mínimas exigidas para as tarefas dos seus agentes
-- **Auditorias Regulares**: Revise periodicamente as integrações conectadas e suas permissões
-- **Credenciais Seguras**: Nunca insira credenciais diretamente no código; utilize o fluxo seguro de autenticação do CrewAI
-
-### Filtrando Ferramentas
-Em um crew implantado, você pode especificar quais ações estão disponíveis para cada integração a partir da página de configurações do serviço ao qual você se conectou.
-
-<Frame>
-  ![Integrações](/images/enterprise/filtering_enterprise_action_tools.png)
-</Frame>
-
-### Implantações com Escopo para organizações multiusuário
-Você pode implantar seu crew e associar cada integração a um usuário específico. Por exemplo, um crew que se conecta ao Google pode usar a conta do Gmail de um usuário específico.
-
-<Tip>
-  Isso é útil para organizações multiusuário, onde você deseja direcionar a integração para um usuário específico.
-</Tip>
-
-Use o `user_bearer_token` para direcionar a integração a um usuário específico; assim, quando o crew for iniciado, ele usará o bearer token desse usuário para autenticar com a integração. Se o usuário não estiver logado, o crew não utilizará nenhuma integração conectada. Use o bearer token padrão para autenticar com as integrações que estão sendo implantadas com o crew.
-
-<Frame>
-  ![Integrações](/images/enterprise/user_bearer_token.png)
-</Frame>
-
-### Precisa de Ajuda?
-
-<Card title="Precisa de ajuda?" icon="headset" href="mailto:support@crewai.com">
-  Entre em contato com nosso time de suporte para assistência com a configuração de integrações ou solução de problemas.
-</Card>
diff --git a/docs/pt-BR/enterprise/features/rbac.mdx b/docs/pt-BR/enterprise/features/rbac.mdx
index aba3e0596..827e8b4e8 100644
--- a/docs/pt-BR/enterprise/features/rbac.mdx
+++ b/docs/pt-BR/enterprise/features/rbac.mdx
@@ -7,10 +7,10 @@ mode: "wide"
 
 ## Visão Geral
 
-O RBAC no CrewAI Enterprise permite gerenciar acesso de forma segura e escalável combinando **funções em nível de organização** com **controles de visibilidade em nível de automação**.
+O RBAC no CrewAI AMP permite gerenciar acesso de forma segura e escalável combinando **funções em nível de organização** com **controles de visibilidade em nível de automação**.
 
 <Frame>
-  <img src="/images/enterprise/users_and_roles.png" alt="Visão geral de RBAC no CrewAI Enterprise" />
+  <img src="/images/enterprise/users_and_roles.png" alt="Visão geral de RBAC no CrewAI AMP" />
   
 </Frame>
 
@@ -28,7 +28,7 @@ A configuração de usuários e funções é feita em Settings → Roles.
 
 <Steps>
   <Step title="Abrir Roles">
-    Vá em <b>Settings → Roles</b> no CrewAI Enterprise.
+    Vá em <b>Settings → Roles</b> no CrewAI AMP.
   </Step>
   <Step title="Escolher a função">
     Use <b>Owner</b> ou <b>Member</b>, ou clique em <b>Create role</b> para criar uma função personalizada.
@@ -93,7 +93,7 @@ O owner sempre possui acesso. Em modo privado, somente usuários/funções na wh
 </Tip>
 
 <Frame>
-  <img src="/images/enterprise/visibility.png" alt="Configuração de visibilidade no CrewAI Enterprise" />
+  <img src="/images/enterprise/visibility.png" alt="Configuração de visibilidade no CrewAI AMP" />
   
 </Frame>
 
diff --git a/docs/pt-BR/enterprise/features/tools-and-integrations.mdx b/docs/pt-BR/enterprise/features/tools-and-integrations.mdx
index ac59e4b04..5c1c1cf75 100644
--- a/docs/pt-BR/enterprise/features/tools-and-integrations.mdx
+++ b/docs/pt-BR/enterprise/features/tools-and-integrations.mdx
@@ -173,10 +173,10 @@ Ferramentas & Integrações é o hub central para conectar aplicações de terce
 
   ## Ferramentas Internas
 
-  Crie ferramentas localmente, publique no Repositório de Ferramentas da CrewAI Enterprise e use nos seus agentes.
+  Crie ferramentas localmente, publique no Repositório de Ferramentas da CrewAI AMP e use nos seus agentes.
 
   <Tip>
-  Antes de executar os comandos abaixo, faça login na sua conta CrewAI Enterprise:
+  Antes de executar os comandos abaixo, faça login na sua conta CrewAI AMP:
     ```bash
     crewai login
     ```
diff --git a/docs/pt-BR/enterprise/features/traces.mdx b/docs/pt-BR/enterprise/features/traces.mdx
index 45fbbf831..4641309bd 100644
--- a/docs/pt-BR/enterprise/features/traces.mdx
+++ b/docs/pt-BR/enterprise/features/traces.mdx
@@ -11,7 +11,7 @@ Traces fornecem visibilidade abrangente sobre as execuções dos seus crews, aju
 
 ## O que são Traces?
 
-Traces no CrewAI Enterprise são registros detalhados de execução que capturam todos os aspectos da operação do seu crew, desde as entradas iniciais até as saídas finais. Eles registram:
+Traces no CrewAI AMP são registros detalhados de execução que capturam todos os aspectos da operação do seu crew, desde as entradas iniciais até as saídas finais. Eles registram:
 
 - Pensamentos e raciocínio do agente
 - Detalhes da execução das tarefas
@@ -28,7 +28,7 @@ Traces no CrewAI Enterprise são registros detalhados de execução que capturam
 
 <Steps>
   <Step title="Navegue até a aba Traces">
-    No seu painel do CrewAI Enterprise, clique em **Traces** para ver todos os registros de execução.
+    No seu painel do CrewAI AMP, clique em **Traces** para ver todos os registros de execução.
   </Step>
   
   <Step title="Selecione uma Execução">
@@ -143,5 +143,5 @@ Traces são indispensáveis para solucionar problemas nos seus crews:
 </Steps>
 
 <Card title="Precisa de ajuda?" icon="headset" href="mailto:support@crewai.com">
-  Entre em contato com nossa equipe de suporte para assistência com análise de traces ou outros recursos do CrewAI Enterprise.
+  Entre em contato com nossa equipe de suporte para assistência com análise de traces ou outros recursos do CrewAI AMP.
 </Card>
\ No newline at end of file
diff --git a/docs/pt-BR/enterprise/features/webhook-streaming.mdx b/docs/pt-BR/enterprise/features/webhook-streaming.mdx
index b187af324..f5d801e0c 100644
--- a/docs/pt-BR/enterprise/features/webhook-streaming.mdx
+++ b/docs/pt-BR/enterprise/features/webhook-streaming.mdx
@@ -7,7 +7,7 @@ mode: "wide"
 
 ## Visão Geral
 
-O Enterprise Event Streaming permite que você receba atualizações em tempo real via webhook sobre suas crews e flows implantados no CrewAI Enterprise, como chamadas de modelo, uso de ferramentas e etapas do flow.
+O Enterprise Event Streaming permite que você receba atualizações em tempo real via webhook sobre suas crews e flows implantados no CrewAI AMP, como chamadas de modelo, uso de ferramentas e etapas do flow.
 
 ## Uso
 
diff --git a/docs/pt-BR/enterprise/guides/automation-triggers.mdx b/docs/pt-BR/enterprise/guides/automation-triggers.mdx
index 80b41a3f5..07f5a757a 100644
--- a/docs/pt-BR/enterprise/guides/automation-triggers.mdx
+++ b/docs/pt-BR/enterprise/guides/automation-triggers.mdx
@@ -1,11 +1,11 @@
 ---
 title: "Visão Geral de Triggers"
-description: "Entenda como os triggers da CrewAI Enterprise funcionam, como gerenciá-los e onde encontrar playbooks específicos de integração"
+description: "Entenda como os triggers da CrewAI AMP funcionam, como gerenciá-los e onde encontrar playbooks específicos de integração"
 icon: "bolt"
 mode: "wide"
 ---
 
-Os triggers da CrewAI Enterprise conectam suas automações a eventos em tempo real nas ferramentas que sua equipe já usa. Em vez de fazer polling ou depender de execuções manuais, os triggers escutam mudanças — novos e‑mails, atualizações de calendário, alterações no CRM — e iniciam imediatamente a crew ou flow que você definiu.
+Os triggers da CrewAI AMP conectam suas automações a eventos em tempo real nas ferramentas que sua equipe já usa. Em vez de fazer polling ou depender de execuções manuais, os triggers escutam mudanças — novos e‑mails, atualizações de calendário, alterações no CRM — e iniciam imediatamente a crew ou flow que você definiu.
 
 <iframe
   className="w-full aspect-video rounded-xl"
@@ -214,6 +214,6 @@ Os triggers transformam suas implantações CrewAI em sistemas orientados por ev
 
 <Callout icon="github" title="Exemplos na prática">
   <a href="https://github.com/crewAIInc/crewai-enterprise-trigger-examples">
-    Repositório CrewAI Enterprise Trigger Examples
+    Repositório CrewAI AMP Trigger Examples
   </a>
 </Callout>
diff --git a/docs/pt-BR/enterprise/guides/azure-openai-setup.mdx b/docs/pt-BR/enterprise/guides/azure-openai-setup.mdx
index 76c13f4db..85de1117d 100644
--- a/docs/pt-BR/enterprise/guides/azure-openai-setup.mdx
+++ b/docs/pt-BR/enterprise/guides/azure-openai-setup.mdx
@@ -20,7 +20,7 @@ Este guia orienta você na conexão do Azure OpenAI com o Crew Studio para opera
     </Step>
 
     <Step title="Configure a Conexão Enterprise do CrewAI">
-        4. Em outra aba, abra `CrewAI Enterprise > LLM Connections`. Dê um nome à sua LLM Connection, selecione Azure como provedor e escolha o mesmo modelo que você selecionou no Azure.
+        4. Em outra aba, abra `CrewAI AMP > LLM Connections`. Dê um nome à sua LLM Connection, selecione Azure como provedor e escolha o mesmo modelo que você selecionou no Azure.
         5. Na mesma página, adicione as variáveis de ambiente do passo 3:
             - Uma chamada `AZURE_DEPLOYMENT_TARGET_URL` (usando o Target URI). A URL deve ser parecida com: https://your-deployment.openai.azure.com/openai/deployments/gpt-4o/chat/completions?api-version=2024-08-01-preview
             - Outra chamada `AZURE_API_KEY` (usando a Key).
@@ -28,7 +28,7 @@ Este guia orienta você na conexão do Azure OpenAI com o Crew Studio para opera
     </Step>
 
     <Step title="Defina Configurações Padrão">
-        7. Em `CrewAI Enterprise > Settings > Defaults > Crew Studio LLM Settings`, defina a nova LLM Connection e o modelo como padrão.
+        7. Em `CrewAI AMP > Settings > Defaults > Crew Studio LLM Settings`, defina a nova LLM Connection e o modelo como padrão.
     </Step>
 
     <Step title="Configure o Acesso à Rede">
diff --git a/docs/pt-BR/enterprise/guides/build-crew.mdx b/docs/pt-BR/enterprise/guides/build-crew.mdx
index b599551a1..b605a63aa 100644
--- a/docs/pt-BR/enterprise/guides/build-crew.mdx
+++ b/docs/pt-BR/enterprise/guides/build-crew.mdx
@@ -7,7 +7,7 @@ mode: "wide"
 
 ## Visão Geral
 
-[CrewAI Enterprise](https://app.crewai.com) simplifica o processo de **criação**, **implantação** e **gerenciamento** dos seus agentes de IA em ambientes de produção.
+[CrewAI AMP](https://app.crewai.com) simplifica o processo de **criação**, **implantação** e **gerenciamento** dos seus agentes de IA em ambientes de produção.
 
 ## Primeiros Passos
 
diff --git a/docs/pt-BR/enterprise/guides/deploy-crew.mdx b/docs/pt-BR/enterprise/guides/deploy-crew.mdx
index f00dac2da..1ff0d9bab 100644
--- a/docs/pt-BR/enterprise/guides/deploy-crew.mdx
+++ b/docs/pt-BR/enterprise/guides/deploy-crew.mdx
@@ -1,12 +1,12 @@
 ---
 title: "Deploy Crew"
-description: "Implantando um Crew na CrewAI Enterprise"
+description: "Implantando um Crew na CrewAI AMP"
 icon: "rocket"
 mode: "wide"
 ---
 
 <Note>
-Depois de criar um crew localmente ou pelo Crew Studio, o próximo passo é implantá-lo na plataforma CrewAI Enterprise. Este guia cobre múltiplos métodos de implantação para ajudá-lo a escolher a melhor abordagem para o seu fluxo de trabalho.
+Depois de criar um crew localmente ou pelo Crew Studio, o próximo passo é implantá-lo na plataforma CrewAI AMP. Este guia cobre múltiplos métodos de implantação para ajudá-lo a escolher a melhor abordagem para o seu fluxo de trabalho.
 </Note>
 
 ## Pré-requisitos
@@ -39,10 +39,10 @@ A CLI fornece a maneira mais rápida de implantar crews desenvolvidos localmente
   </Step>
 
   <Step title="Autentique-se na Plataforma Enterprise">
-    Primeiro, você precisa autenticar sua CLI com a plataforma CrewAI Enterprise:
+    Primeiro, você precisa autenticar sua CLI com a plataforma CrewAI AMP:
 
     ```bash
-    # Se já possui uma conta CrewAI Enterprise, ou deseja criar uma:
+    # Se já possui uma conta CrewAI AMP, ou deseja criar uma:
     crewai login
     ```
 
@@ -124,7 +124,7 @@ O CrewAI CLI oferece vários comandos para gerenciar suas implantações:
 
 ## Opção 2: Implantar Diretamente pela Interface Web
 
-Você também pode implantar seus crews diretamente pela interface web da CrewAI Enterprise conectando sua conta do GitHub. Esta abordagem não requer utilizar a CLI na sua máquina local.
+Você também pode implantar seus crews diretamente pela interface web da CrewAI AMP conectando sua conta do GitHub. Esta abordagem não requer utilizar a CLI na sua máquina local.
 
 <Steps>
 
@@ -134,9 +134,9 @@ Você também pode implantar seus crews diretamente pela interface web da CrewAI
 
   </Step>
 
-  <Step title="Conectando o GitHub ao CrewAI Enterprise">
+  <Step title="Conectando o GitHub ao CrewAI AMP">
 
-    1. Faça login em [CrewAI Enterprise](https://app.crewai.com)
+    1. Faça login em [CrewAI AMP](https://app.crewai.com)
     2. Clique no botão "Connect GitHub"
 
     <Frame>
@@ -190,7 +190,7 @@ Você também pode implantar seus crews diretamente pela interface web da CrewAI
 ## ⚠️ Requisitos de Segurança para Variáveis de Ambiente
 
 <Warning>
-**Importante**: A CrewAI Enterprise possui restrições de segurança sobre os nomes de variáveis de ambiente que podem causar falha na implantação caso não sejam seguidas.
+**Importante**: A CrewAI AMP possui restrições de segurança sobre os nomes de variáveis de ambiente que podem causar falha na implantação caso não sejam seguidas.
 </Warning>
 
 ### Padrões de Variáveis de Ambiente Bloqueados
diff --git a/docs/pt-BR/enterprise/guides/enable-crew-studio.mdx b/docs/pt-BR/enterprise/guides/enable-crew-studio.mdx
index 329f87aa1..5e85dfdde 100644
--- a/docs/pt-BR/enterprise/guides/enable-crew-studio.mdx
+++ b/docs/pt-BR/enterprise/guides/enable-crew-studio.mdx
@@ -1,6 +1,6 @@
 ---
 title: "Ativar Crew Studio"
-description: "Ativando o Crew Studio no CrewAI Enterprise"
+description: "Ativando o Crew Studio no CrewAI AMP"
 icon: "comments"
 mode: "wide"
 ---
@@ -24,7 +24,7 @@ Com o Crew Studio, você pode:
 - Selecionar as ferramentas apropriadas
 - Configurar os inputs necessários
 - Gerar código para download e personalização
-- Fazer deploy diretamente na plataforma CrewAI Enterprise
+- Fazer deploy diretamente na plataforma CrewAI AMP
 
 ## Etapas de Configuração
 
@@ -32,7 +32,7 @@ Antes de começar a usar o Crew Studio, você precisa configurar suas conexões
 
 <Steps>
   <Step title="Configurar a Conexão LLM">
-    Acesse a aba **LLM Connections** no painel do CrewAI Enterprise e crie uma nova conexão LLM.
+    Acesse a aba **LLM Connections** no painel do CrewAI AMP e crie uma nova conexão LLM.
 
     <Note>
       Sinta-se à vontade para utilizar qualquer provedor LLM suportado pelo CrewAI.
@@ -82,7 +82,7 @@ Agora que você configurou sua conexão LLM e os padrões, está pronto para com
 
 <Steps>
   <Step title="Acessar o Studio">
-    Navegue até a seção **Studio** no painel do CrewAI Enterprise.
+    Navegue até a seção **Studio** no painel do CrewAI AMP.
   </Step>
   
   <Step title="Iniciar uma Conversa">
@@ -110,7 +110,7 @@ Agora que você configurou sua conexão LLM e os padrões, está pronto para com
     Quando estiver satisfeito com a configuração, você pode:
     
     - Baixar o código gerado para personalização local
-    - Fazer deploy do crew diretamente na plataforma CrewAI Enterprise
+    - Fazer deploy do crew diretamente na plataforma CrewAI AMP
     - Modificar a configuração e gerar o crew novamente
   </Step>
   
@@ -162,5 +162,5 @@ Veja um fluxo de trabalho típico para criação de um crew com o Crew Studio:
 </Steps>
 
 <Card title="Precisa de ajuda?" icon="headset" href="mailto:support@crewai.com">
-  Entre em contato com nossa equipe de suporte para obter assistência com o Crew Studio ou qualquer outro recurso do CrewAI Enterprise.
+  Entre em contato com nossa equipe de suporte para obter assistência com o Crew Studio ou qualquer outro recurso do CrewAI AMP.
 </Card>
\ No newline at end of file
diff --git a/docs/pt-BR/enterprise/guides/gmail-trigger.mdx b/docs/pt-BR/enterprise/guides/gmail-trigger.mdx
new file mode 100644
index 000000000..2caefc045
--- /dev/null
+++ b/docs/pt-BR/enterprise/guides/gmail-trigger.mdx
@@ -0,0 +1,85 @@
+---
+title: "Gmail Trigger"
+description: "Trigger automations when Gmail events occur (e.g., new emails, labels)."
+icon: "envelope"
+mode: "wide"
+---
+
+## Overview
+
+Use the Gmail Trigger to kick off your deployed crews when Gmail events happen in connected accounts, such as receiving a new email or messages matching a label/filter.
+
+<Tip>
+  Make sure Gmail is connected in Tools & Integrations and the trigger is enabled for your deployment.
+</Tip>
+
+## Enabling the Gmail Trigger
+
+1. Open your deployment in CrewAI AMP
+2. Go to the **Triggers** tab
+3. Locate **Gmail** and switch the toggle to enable
+
+<Frame>
+  <img src="/images/enterprise/trigger-selected.png" alt="Enable or disable triggers with toggle" />
+</Frame>
+
+## Example: Process new emails
+
+When a new email arrives, the Gmail Trigger will send the payload to your Crew or Flow. Below is a Crew example that parses and processes the trigger payload.
+
+```python
+@CrewBase
+class GmailProcessingCrew:
+    @agent
+    def parser(self) -> Agent:
+        return Agent(
+            config=self.agents_config['parser'],
+        )
+
+    @task
+    def parse_gmail_payload(self) -> Task:
+        return Task(
+            config=self.tasks_config['parse_gmail_payload'],
+            agent=self.parser(),
+        )
+
+    @task
+    def act_on_email(self) -> Task:
+        return Task(
+            config=self.tasks_config['act_on_email'],
+            agent=self.parser(),
+        )
+```
+
+The Gmail payload will be available via the standard context mechanisms. See the payload samples repository for structure and fields.
+
+### Sample payloads & crews
+
+The [CrewAI AMP Trigger Examples repository](https://github.com/crewAIInc/crewai-enterprise-trigger-examples/tree/main/gmail) includes:
+
+- `new-email-payload-1.json` / `new-email-payload-2.json` — production-style new message alerts with matching crews in `new-email-crew.py`
+- `thread-updated-sample-1.json` — follow-up messages on an existing thread, processed by `gmail-alert-crew.py`
+
+Use these samples to validate your parsing logic locally before wiring the trigger to your live Gmail accounts.
+
+## Monitoring Executions
+
+Track history and performance of triggered runs:
+
+<Frame>
+  <img src="/images/enterprise/list-executions.png" alt="List of executions triggered by automation" />
+</Frame>
+
+## Payload Reference
+
+See the sample payloads and field descriptions:
+
+<Card title="Gmail samples in Trigger Examples Repo" href="https://github.com/crewAIInc/crewai-enterprise-trigger-examples/tree/main/gmail" icon="envelopes-bulk">
+    Gmail samples in Trigger Examples Repo
+</Card>
+
+## Troubleshooting
+
+- Ensure Gmail is connected in Tools & Integrations
+- Verify the Gmail Trigger is enabled on the Triggers tab
+- Check the execution logs and confirm the payload is passed as `crewai_trigger_payload`
diff --git a/docs/pt-BR/enterprise/guides/google-calendar-trigger.mdx b/docs/pt-BR/enterprise/guides/google-calendar-trigger.mdx
new file mode 100644
index 000000000..cf2d32471
--- /dev/null
+++ b/docs/pt-BR/enterprise/guides/google-calendar-trigger.mdx
@@ -0,0 +1,65 @@
+---
+title: "Google Calendar Trigger"
+description: "Kick off crews when Google Calendar events are created, updated, or cancelled"
+icon: "calendar"
+mode: "wide"
+---
+
+## Overview
+
+Use the Google Calendar trigger to launch automations whenever calendar events change. Common use cases include briefing a team before a meeting, notifying stakeholders when a critical event is cancelled, or summarizing daily schedules.
+
+<Tip>
+  Make sure Google Calendar is connected in **Tools & Integrations** and enabled for the deployment you want to automate.
+</Tip>
+
+## Enabling the Google Calendar Trigger
+
+1. Open your deployment in CrewAI AMP
+2. Go to the **Triggers** tab
+3. Locate **Google Calendar** and switch the toggle to enable
+
+<Frame>
+  <img src="/images/enterprise/calendar-trigger.png" alt="Enable or disable triggers with toggle" />
+</Frame>
+
+## Example: Summarize meeting details
+
+The snippet below mirrors the `calendar-event-crew.py` example in the trigger repository. It parses the payload, analyses the attendees and timing, and produces a meeting brief for downstream tools.
+
+```python
+from calendar_event_crew import GoogleCalendarEventTrigger
+
+crew = GoogleCalendarEventTrigger().crew()
+result = crew.kickoff({
+    "crewai_trigger_payload": calendar_payload,
+})
+print(result.raw)
+```
+
+Use `crewai_trigger_payload` exactly as it is delivered by the trigger so the crew can extract the proper fields.
+
+## Sample payloads & crews
+
+The [Google Calendar examples](https://github.com/crewAIInc/crewai-enterprise-trigger-examples/tree/main/google_calendar) show how to handle multiple event types:
+
+- `new-event.json` → standard event creation handled by `calendar-event-crew.py`
+- `event-updated.json` / `event-started.json` / `event-ended.json` → in-flight updates processed by `calendar-meeting-crew.py`
+- `event-canceled.json` → cancellation workflow that alerts attendees via `calendar-meeting-crew.py`
+- Working location events use `calendar-working-location-crew.py` to extract on-site schedules
+
+Each crew transforms raw event metadata (attendees, rooms, working locations) into the summaries your teams need.
+
+## Monitoring Executions
+
+The **Executions** list in the deployment dashboard tracks every triggered run and surfaces payload metadata, output summaries, and errors.
+
+<Frame>
+  <img src="/images/enterprise/list-executions.png" alt="List of executions triggered by automation" />
+</Frame>
+
+## Troubleshooting
+
+- Ensure the correct Google account is connected and the trigger is enabled
+- Confirm your workflow handles all-day events (payloads use `start.date` and `end.date` instead of timestamps)
+- Check execution logs if reminders or attendee arrays are missing—calendar permissions can limit fields in the payload
diff --git a/docs/pt-BR/enterprise/guides/google-drive-trigger.mdx b/docs/pt-BR/enterprise/guides/google-drive-trigger.mdx
new file mode 100644
index 000000000..19c10837b
--- /dev/null
+++ b/docs/pt-BR/enterprise/guides/google-drive-trigger.mdx
@@ -0,0 +1,61 @@
+---
+title: "Google Drive Trigger"
+description: "Respond to Google Drive file events with automated crews"
+icon: "folder"
+mode: "wide"
+---
+
+## Overview
+
+Trigger your automations when files are created, updated, or removed in Google Drive. Typical workflows include summarizing newly uploaded content, enforcing sharing policies, or notifying owners when critical files change.
+
+<Tip>
+  Connect Google Drive in **Tools & Integrations** and confirm the trigger is enabled for the automation you want to monitor.
+</Tip>
+
+## Enabling the Google Drive Trigger
+
+1. Open your deployment in CrewAI AMP
+2. Go to the **Triggers** tab
+3. Locate **Google Drive** and switch the toggle to enable
+
+<Frame>
+  <img src="/images/enterprise/gdrive-trigger.png" alt="Enable or disable triggers with toggle" />
+</Frame>
+
+## Example: Summarize file activity
+
+The drive example crews parse the payload to extract file metadata, evaluate permissions, and publish a summary.
+
+```python
+from drive_file_crew import GoogleDriveFileTrigger
+
+crew = GoogleDriveFileTrigger().crew()
+crew.kickoff({
+    "crewai_trigger_payload": drive_payload,
+})
+```
+
+## Sample payloads & crews
+
+Explore the [Google Drive examples](https://github.com/crewAIInc/crewai-enterprise-trigger-examples/tree/main/google_drive) to cover different operations:
+
+- `new-file.json` → new uploads processed by `drive-file-crew.py`
+- `updated-file.json` → file edits and metadata changes handled by `drive-file-crew.py`
+- `deleted-file.json` → deletion events routed through `drive-file-deletion-crew.py`
+
+Each crew highlights the file name, operation type, owner, permissions, and security considerations so downstream systems can respond appropriately.
+
+## Monitoring Executions
+
+Track history and performance of triggered runs with the **Executions** list in the deployment dashboard.
+
+<Frame>
+  <img src="/images/enterprise/list-executions.png" alt="List of executions triggered by automation" />
+</Frame>
+
+## Troubleshooting
+
+- Verify Google Drive is connected and the trigger toggle is enabled
+- If a payload is missing permission data, ensure the connected account has access to the file or folder
+- The trigger sends file IDs only; use the Drive API if you need to fetch binary content during the crew run
diff --git a/docs/pt-BR/enterprise/guides/hubspot-trigger.mdx b/docs/pt-BR/enterprise/guides/hubspot-trigger.mdx
index 9ffcefd95..25fa2edeb 100644
--- a/docs/pt-BR/enterprise/guides/hubspot-trigger.mdx
+++ b/docs/pt-BR/enterprise/guides/hubspot-trigger.mdx
@@ -5,22 +5,22 @@ icon: "hubspot"
 mode: "wide"
 ---
 
-Este guia fornece um processo passo a passo para configurar gatilhos do HubSpot para o CrewAI Enterprise, permitindo iniciar crews diretamente a partir de Workflows do HubSpot.
+Este guia fornece um processo passo a passo para configurar gatilhos do HubSpot para o CrewAI AMP, permitindo iniciar crews diretamente a partir de Workflows do HubSpot.
 
 ## Pré-requisitos
 
-- Uma conta CrewAI Enterprise
+- Uma conta CrewAI AMP
 - Uma conta HubSpot com o recurso de [Workflows do HubSpot](https://knowledge.hubspot.com/workflows/create-workflows)
 
 ## Etapas de Configuração
 
 <Steps>
-    <Step title="Conecte sua conta HubSpot com o CrewAI Enterprise">
-        - Faça login na sua `Conta CrewAI Enterprise > Triggers`
+    <Step title="Conecte sua conta HubSpot com o CrewAI AMP">
+        - Faça login na sua `Conta CrewAI AMP > Triggers`
         - Selecione `HubSpot` na lista de gatilhos disponíveis
-        - Escolha a conta HubSpot que deseja conectar ao CrewAI Enterprise
-        - Siga as instruções na tela para autorizar o acesso do CrewAI Enterprise à sua conta HubSpot
-        - Uma mensagem de confirmação aparecerá assim que o HubSpot estiver conectado com sucesso ao CrewAI Enterprise
+        - Escolha a conta HubSpot que deseja conectar ao CrewAI AMP
+        - Siga as instruções na tela para autorizar o acesso do CrewAI AMP à sua conta HubSpot
+        - Uma mensagem de confirmação aparecerá assim que o HubSpot estiver conectado com sucesso ao CrewAI AMP
     </Step>
     <Step title="Crie um Workflow no HubSpot">
         - Faça login na sua `Conta HubSpot > Automations > Workflows > New workflow`
diff --git a/docs/pt-BR/enterprise/guides/kickoff-crew.mdx b/docs/pt-BR/enterprise/guides/kickoff-crew.mdx
index 2682dbb34..cbdafea9d 100644
--- a/docs/pt-BR/enterprise/guides/kickoff-crew.mdx
+++ b/docs/pt-BR/enterprise/guides/kickoff-crew.mdx
@@ -1,19 +1,19 @@
 ---
 title: "Kickoff Crew"
-description: "Inicie um Crew no CrewAI Enterprise"
+description: "Inicie um Crew no CrewAI AMP"
 icon: "flag-checkered"
 mode: "wide"
 ---
 
 ## Visão Geral
 
-Uma vez que você tenha implantado seu crew na plataforma CrewAI Enterprise, é possível iniciar execuções pela interface web ou pela API. Este guia aborda ambos os métodos.
+Uma vez que você tenha implantado seu crew na plataforma CrewAI AMP, é possível iniciar execuções pela interface web ou pela API. Este guia aborda ambos os métodos.
 
 ## Método 1: Usando a Interface Web
 
 ### Passo 1: Navegue até seu Crew Implantado
 
-1. Faça login no [CrewAI Enterprise](https://app.crewai.com)
+1. Faça login no [CrewAI AMP](https://app.crewai.com)
 2. Clique no nome do crew na sua lista de projetos
 3. Você será direcionado para a página de detalhes do crew
 
@@ -83,7 +83,7 @@ Quando a execução for concluída:
 
 ## Método 2: Usando a API
 
-Você também pode iniciar crews programaticamente usando a REST API do CrewAI Enterprise.
+Você também pode iniciar crews programaticamente usando a REST API do CrewAI AMP.
 
 ### Autenticação
 
diff --git a/docs/pt-BR/enterprise/guides/microsoft-teams-trigger.mdx b/docs/pt-BR/enterprise/guides/microsoft-teams-trigger.mdx
new file mode 100644
index 000000000..10878af40
--- /dev/null
+++ b/docs/pt-BR/enterprise/guides/microsoft-teams-trigger.mdx
@@ -0,0 +1,52 @@
+---
+title: "Microsoft Teams Trigger"
+description: "Kick off crews from Microsoft Teams chat activity"
+icon: "microsoft"
+mode: "wide"
+---
+
+## Overview
+
+Use the Microsoft Teams trigger to start automations whenever a new chat is created. Common patterns include summarizing inbound requests, routing urgent messages to support teams, or creating follow-up tasks in other systems.
+
+<Tip>
+  Confirm Microsoft Teams is connected under **Tools & Integrations** and enabled in the **Triggers** tab for your deployment.
+</Tip>
+
+## Enabling the Microsoft Teams Trigger
+
+1. Open your deployment in CrewAI AMP
+2. Go to the **Triggers** tab
+3. Locate **Microsoft Teams** and switch the toggle to enable
+
+<Frame caption="Microsoft Teams trigger connection">
+  <img src="/images/enterprise/msteams-trigger.png" alt="Enable or disable triggers with toggle" />
+</Frame>
+
+## Example: Summarize a new chat thread
+
+```python
+from teams_chat_created_crew import MicrosoftTeamsChatTrigger
+
+crew = MicrosoftTeamsChatTrigger().crew()
+result = crew.kickoff({
+    "crewai_trigger_payload": teams_payload,
+})
+print(result.raw)
+```
+
+The crew parses thread metadata (subject, created time, roster) and generates an action plan for the receiving team.
+
+## Sample payloads & crews
+
+The [Microsoft Teams examples](https://github.com/crewAIInc/crewai-enterprise-trigger-examples/tree/main/microsoft-teams) include:
+
+- `chat-created.json` → chat creation payload processed by `teams-chat-created-crew.py`
+
+The crew demonstrates how to extract participants, initial messages, tenant information, and compliance metadata from the Microsoft Graph webhook payload.
+
+## Troubleshooting
+
+- Ensure the Teams connection is active; it must be refreshed if the tenant revokes permissions
+- Confirm the webhook subscription in Microsoft 365 is still valid if payloads stop arriving
+- Review execution logs for payload shape mismatches—Graph notifications may omit fields when a chat is private or restricted
diff --git a/docs/pt-BR/enterprise/guides/onedrive-trigger.mdx b/docs/pt-BR/enterprise/guides/onedrive-trigger.mdx
new file mode 100644
index 000000000..51de175db
--- /dev/null
+++ b/docs/pt-BR/enterprise/guides/onedrive-trigger.mdx
@@ -0,0 +1,53 @@
+---
+title: "OneDrive Trigger"
+description: "Automate responses to OneDrive file activity"
+icon: "cloud"
+mode: "wide"
+---
+
+## Overview
+
+Start automations when files change inside OneDrive. You can generate audit summaries, notify security teams about external sharing, or update downstream line-of-business systems with new document metadata.
+
+<Tip>
+  Connect OneDrive in **Tools & Integrations** and toggle the trigger on for your deployment.
+</Tip>
+
+## Enabling the OneDrive Trigger
+
+1. Open your deployment in CrewAI AMP
+2. Go to the **Triggers** tab
+3. Locate **OneDrive** and switch the toggle to enable
+
+<Frame caption="Microsoft OneDrive trigger connection">
+  <img src="/images/enterprise/onedrive-trigger.png" alt="Enable or disable triggers with toggle" />
+</Frame>
+
+## Example: Audit file permissions
+
+```python
+from onedrive_file_crew import OneDriveFileTrigger
+
+crew = OneDriveFileTrigger().crew()
+crew.kickoff({
+    "crewai_trigger_payload": onedrive_payload,
+})
+```
+
+The crew inspects file metadata, user activity, and permission changes to produce a compliance-friendly summary.
+
+## Sample payloads & crews
+
+The [OneDrive examples](https://github.com/crewAIInc/crewai-enterprise-trigger-examples/tree/main/onedrive) showcase how to:
+
+- Parse file metadata, size, and folder paths
+- Track who created and last modified the file
+- Highlight permission and external sharing changes
+
+`onedrive-file-crew.py` bundles the analysis and summarization tasks so you can add remediation steps as needed.
+
+## Troubleshooting
+
+- Ensure the connected account has permission to read the file metadata included in the webhook
+- If the trigger fires but the payload is missing `permissions`, confirm the site-level sharing settings allow Graph to return this field
+- For large tenants, filter notifications upstream so the crew only runs on relevant directories
diff --git a/docs/pt-BR/enterprise/guides/outlook-trigger.mdx b/docs/pt-BR/enterprise/guides/outlook-trigger.mdx
new file mode 100644
index 000000000..21bda5407
--- /dev/null
+++ b/docs/pt-BR/enterprise/guides/outlook-trigger.mdx
@@ -0,0 +1,52 @@
+---
+title: "Outlook Trigger"
+description: "Launch automations from Outlook emails and calendar updates"
+icon: "microsoft"
+mode: "wide"
+---
+
+## Overview
+
+Automate responses when Outlook delivers a new message or when an event is removed from the calendar. Teams commonly route escalations, file tickets, or alert attendees of cancellations.
+
+<Tip>
+  Connect Outlook in **Tools & Integrations** and ensure the trigger is enabled for your deployment.
+</Tip>
+
+## Enabling the Outlook Trigger
+
+1. Open your deployment in CrewAI AMP
+2. Go to the **Triggers** tab
+3. Locate **Outlook** and switch the toggle to enable
+
+<Frame caption="Microsoft Outlook trigger connection">
+  <img src="/images/enterprise/outlook-trigger.png" alt="Enable or disable triggers with toggle" />
+</Frame>
+
+## Example: Summarize a new email
+
+```python
+from outlook_message_crew import OutlookMessageTrigger
+
+crew = OutlookMessageTrigger().crew()
+crew.kickoff({
+    "crewai_trigger_payload": outlook_payload,
+})
+```
+
+The crew extracts sender details, subject, body preview, and attachments before generating a structured response.
+
+## Sample payloads & crews
+
+Review the [Outlook examples](https://github.com/crewAIInc/crewai-enterprise-trigger-examples/tree/main/outlook) for two common scenarios:
+
+- `new-message.json` → new mail notifications parsed by `outlook-message-crew.py`
+- `event-removed.json` → calendar cleanup handled by `outlook-event-removal-crew.py`
+
+Each crew demonstrates how to handle Microsoft Graph payloads, normalize headers, and keep humans in-the-loop with concise summaries.
+
+## Troubleshooting
+
+- Verify the Outlook connector is still authorized; the subscription must be renewed periodically
+- If attachments are missing, confirm the webhook subscription includes the `includeResourceData` flag
+- Review execution logs when events fail to match—cancellation payloads lack attendee lists by design and the crew should account for that
diff --git a/docs/pt-BR/enterprise/guides/react-component-export.mdx b/docs/pt-BR/enterprise/guides/react-component-export.mdx
index 062d2564c..fd5ede46a 100644
--- a/docs/pt-BR/enterprise/guides/react-component-export.mdx
+++ b/docs/pt-BR/enterprise/guides/react-component-export.mdx
@@ -1,11 +1,11 @@
 ---
 title: "Exportação de Componentes React"
-description: "Aprenda como exportar e integrar componentes React do CrewAI Enterprise em suas aplicações"
+description: "Aprenda como exportar e integrar componentes React do CrewAI AMP em suas aplicações"
 icon: "react"
 mode: "wide"
 ---
 
-Este guia explica como exportar crews do CrewAI Enterprise como componentes React e integrá-los às suas próprias aplicações.
+Este guia explica como exportar crews do CrewAI AMP como componentes React e integrá-los às suas próprias aplicações.
 
 ## Exportando um Componente React
 
diff --git a/docs/pt-BR/enterprise/guides/salesforce-trigger.mdx b/docs/pt-BR/enterprise/guides/salesforce-trigger.mdx
index 043dbd91f..229923e88 100644
--- a/docs/pt-BR/enterprise/guides/salesforce-trigger.mdx
+++ b/docs/pt-BR/enterprise/guides/salesforce-trigger.mdx
@@ -5,7 +5,7 @@ icon: "salesforce"
 mode: "wide"
 ---
 
-A CrewAI Enterprise pode ser acionada a partir do Salesforce para automatizar fluxos de trabalho de gestão de relacionamento com o cliente e aprimorar suas operações de vendas.
+A CrewAI AMP pode ser acionada a partir do Salesforce para automatizar fluxos de trabalho de gestão de relacionamento com o cliente e aprimorar suas operações de vendas.
 
 ## Visão Geral
 
@@ -31,7 +31,7 @@ O Salesforce é uma das principais plataformas de gestão de relacionamento com
 
 Para configurar triggers no Salesforce:
 
-1. **Contato com o Suporte**: Entre em contato com o suporte da CrewAI Enterprise para obter assistência na configuração dos triggers no Salesforce
+1. **Contato com o Suporte**: Entre em contato com o suporte da CrewAI AMP para obter assistência na configuração dos triggers no Salesforce
 2. **Revisar Requisitos**: Certifique-se de possuir as permissões necessárias no Salesforce e acesso à API
 3. **Configurar Conexão**: Trabalhe com a equipe de suporte para estabelecer a conexão entre a CrewAI e sua instância do Salesforce
 4. **Testar Triggers**: Verifique se os triggers funcionam corretamente para os seus casos de uso específicos
@@ -47,4 +47,4 @@ Cenários comuns de uso de triggers Salesforce + CrewAI incluem:
 
 ## Próximos Passos
 
-Para instruções detalhadas de configuração e opções avançadas, entre em contato com o suporte da CrewAI Enterprise, que pode fornecer orientações personalizadas para o seu ambiente Salesforce e necessidades de negócio.
+Para instruções detalhadas de configuração e opções avançadas, entre em contato com o suporte da CrewAI AMP, que pode fornecer orientações personalizadas para o seu ambiente Salesforce e necessidades de negócio.
diff --git a/docs/pt-BR/enterprise/guides/team-management.mdx b/docs/pt-BR/enterprise/guides/team-management.mdx
index 1594bca15..7c5c584c4 100644
--- a/docs/pt-BR/enterprise/guides/team-management.mdx
+++ b/docs/pt-BR/enterprise/guides/team-management.mdx
@@ -1,17 +1,17 @@
 ---
 title: "Gestão de Equipes"
-description: "Aprenda como convidar e gerenciar membros da equipe em sua organização CrewAI Enterprise"
+description: "Aprenda como convidar e gerenciar membros da equipe em sua organização CrewAI AMP"
 icon: "users"
 mode: "wide"
 ---
 
-Como administrador de uma conta CrewAI Enterprise, você pode facilmente convidar novos membros para sua organização. Este guia irá orientá-lo passo a passo pelo processo.
+Como administrador de uma conta CrewAI AMP, você pode facilmente convidar novos membros para sua organização. Este guia irá orientá-lo passo a passo pelo processo.
 
 ## Convidando Membros da Equipe
 
 <Steps>
     <Step title="Acesse a Página de Configurações">
-        - Faça login na sua conta CrewAI Enterprise
+        - Faça login na sua conta CrewAI AMP
         - Procure o ícone de engrenagem (⚙️) no canto superior direito do painel
         - Clique no ícone de engrenagem para acessar a página de **Configurações**:
             <Frame>
@@ -43,7 +43,7 @@ Você pode adicionar funções aos membros da equipe para controlar o acesso a d
 
 <Steps>
     <Step title="Acesse a Página de Configurações">
-        - Faça login na sua conta CrewAI Enterprise
+        - Faça login na sua conta CrewAI AMP
         - Procure o ícone de engrenagem (⚙️) no canto superior direito do painel
         - Clique no ícone de engrenagem para acessar a página de **Configurações**:
             <Frame>
@@ -85,4 +85,4 @@ Você pode adicionar funções aos membros da equipe para controlar o acesso a d
 - **Aceite do Convite**: Os membros convidados precisarão aceitar o convite para ingressar na sua organização
 - **Notificações por E-mail**: Oriente seus membros a verificarem o e-mail (incluindo a pasta de spam) para localizar o convite
 
-Seguindo estes passos, você conseguirá expandir sua equipe e colaborar de forma mais eficaz dentro da sua organização CrewAI Enterprise.
\ No newline at end of file
+Seguindo estes passos, você conseguirá expandir sua equipe e colaborar de forma mais eficaz dentro da sua organização CrewAI AMP.
\ No newline at end of file
diff --git a/docs/pt-BR/enterprise/guides/tool-repository.mdx b/docs/pt-BR/enterprise/guides/tool-repository.mdx
index e77843f8a..042ebc300 100644
--- a/docs/pt-BR/enterprise/guides/tool-repository.mdx
+++ b/docs/pt-BR/enterprise/guides/tool-repository.mdx
@@ -20,11 +20,11 @@ O repositório não é um sistema de controle de versões. Use Git para rastrear
 
 Antes de usar o Repositório de Ferramentas, certifique-se de que você possui:
 
-- Uma conta [CrewAI Enterprise](https://app.crewai.com)
+- Uma conta [CrewAI AMP](https://app.crewai.com)
 - [CrewAI CLI](https://docs.crewai.com/concepts/cli#cli) instalada
 - uv>=0.5.0 instalado. Veja [como atualizar](https://docs.astral.sh/uv/getting-started/installation/#upgrading-uv)
 - [Git](https://git-scm.com) instalado e configurado
-- Permissões de acesso para publicar ou instalar ferramentas em sua organização CrewAI Enterprise
+- Permissões de acesso para publicar ou instalar ferramentas em sua organização CrewAI AMP
 
 ## Instalando ferramentas
 
@@ -85,7 +85,7 @@ crewai tool publish
 
 Para excluir uma ferramenta:
 
-1. Acesse o [CrewAI Enterprise](https://app.crewai.com)
+1. Acesse o [CrewAI AMP](https://app.crewai.com)
 2. Navegue até **Ferramentas**
 3. Selecione a ferramenta
 4. Clique em **Excluir**
@@ -100,7 +100,7 @@ Cada versão publicada passa por verificações automáticas de segurança e só
 
 Você pode verificar o status das verificações de segurança de uma ferramenta em:
 
-`CrewAI Enterprise > Tools > Your Tool > Versions`
+`CrewAI AMP > Tools > Your Tool > Versions`
 
 <Card title="Precisa de ajuda?" icon="headset" href="mailto:support@crewai.com">
   Entre em contato com nossa equipe de suporte para assistência com integração de API ou resolução de problemas.
diff --git a/docs/pt-BR/enterprise/guides/update-crew.mdx b/docs/pt-BR/enterprise/guides/update-crew.mdx
index b48a5a818..295792bcc 100644
--- a/docs/pt-BR/enterprise/guides/update-crew.mdx
+++ b/docs/pt-BR/enterprise/guides/update-crew.mdx
@@ -1,12 +1,12 @@
 ---
 title: "Atualizar Crew"
-description: "Atualizando uma Crew no CrewAI Enterprise"
+description: "Atualizando uma Crew no CrewAI AMP"
 icon: "pencil"
 mode: "wide"
 ---
 
 <Note>
-Após implantar sua crew no CrewAI Enterprise, pode ser necessário fazer atualizações no código, configurações de segurança ou configuração. 
+Após implantar sua crew no CrewAI AMP, pode ser necessário fazer atualizações no código, configurações de segurança ou configuração. 
 Este guia explica como realizar essas operações de atualização comuns.
 </Note>
 
@@ -23,7 +23,7 @@ Há várias razões para querer atualizar sua implantação de crew:
 
 Quando você fizer push de novos commits no seu repositório do GitHub e quiser atualizar sua implantação:
 
-1. Navegue até sua crew na plataforma CrewAI Enterprise
+1. Navegue até sua crew na plataforma CrewAI AMP
 2. Clique no botão `Re-deploy` na página de detalhes da sua crew
 
 <Frame>
@@ -36,7 +36,7 @@ Isso irá acionar uma atualização que pode ser acompanhada pela barra de progr
 
 Se precisar gerar um novo bearer token (por exemplo, se suspeitar que o token atual possa ter sido comprometido):
 
-1. Navegue até sua crew na plataforma CrewAI Enterprise
+1. Navegue até sua crew na plataforma CrewAI AMP
 2. Encontre a seção `Bearer Token`
 3. Clique no botão `Reset` ao lado do token atual
 
diff --git a/docs/pt-BR/enterprise/guides/webhook-automation.mdx b/docs/pt-BR/enterprise/guides/webhook-automation.mdx
index e972e9df4..488293968 100644
--- a/docs/pt-BR/enterprise/guides/webhook-automation.mdx
+++ b/docs/pt-BR/enterprise/guides/webhook-automation.mdx
@@ -1,17 +1,17 @@
 ---
 title: "Automação com Webhook"
-description: "Automatize fluxos de trabalho do CrewAI Enterprise usando webhooks com plataformas como ActivePieces, Zapier e Make.com"
+description: "Automatize fluxos de trabalho do CrewAI AMP usando webhooks com plataformas como ActivePieces, Zapier e Make.com"
 icon: "webhook"
 mode: "wide"
 ---
 
-O CrewAI Enterprise permite que você automatize seu fluxo de trabalho usando webhooks. Este artigo irá guiá-lo no processo de configuração e uso de webhooks para iniciar a execução do crew, com foco na integração com o ActivePieces, uma plataforma de automação de fluxos de trabalho semelhante ao Zapier e Make.com.
+O CrewAI AMP permite que você automatize seu fluxo de trabalho usando webhooks. Este artigo irá guiá-lo no processo de configuração e uso de webhooks para iniciar a execução do crew, com foco na integração com o ActivePieces, uma plataforma de automação de fluxos de trabalho semelhante ao Zapier e Make.com.
 
 ## Configurando Webhooks
 
 <Steps>
     <Step title="Acessando a Interface de Kickoff">
-        - Navegue até o painel do CrewAI Enterprise
+        - Navegue até o painel do CrewAI AMP
         - Procure pela seção `/kickoff`, que é usada para iniciar a execução do crew
             <Frame>
                 <img src="/images/enterprise/kickoff-interface.png" alt="Interface Kickoff" />
@@ -44,7 +44,7 @@ O CrewAI Enterprise permite que você automatize seu fluxo de trabalho usando we
         3. Adicione uma etapa de ação HTTP
             - Configure a ação como `Send HTTP request`
             - Use o método `POST`
-            - Defina a URL para o endpoint de kickoff do CrewAI Enterprise
+            - Defina a URL para o endpoint de kickoff do CrewAI AMP
             - Adicione os headers necessários (ex.: `Bearer Token`)
                 <Frame>
                     <img src="/images/enterprise/activepieces-headers.png" alt="Headers ActivePieces" />
diff --git a/docs/pt-BR/enterprise/guides/zapier-trigger.mdx b/docs/pt-BR/enterprise/guides/zapier-trigger.mdx
index 7520f06b6..36763892c 100644
--- a/docs/pt-BR/enterprise/guides/zapier-trigger.mdx
+++ b/docs/pt-BR/enterprise/guides/zapier-trigger.mdx
@@ -5,11 +5,11 @@ icon: "bolt"
 mode: "wide"
 ---
 
-Este guia irá conduzi-lo pelo processo de configuração de triggers no Zapier para o CrewAI Enterprise, permitindo automatizar fluxos de trabalho entre CrewAI Enterprise e outros aplicativos.
+Este guia irá conduzi-lo pelo processo de configuração de triggers no Zapier para o CrewAI AMP, permitindo automatizar fluxos de trabalho entre CrewAI AMP e outros aplicativos.
 
 ## Pré-requisitos
 
-- Uma conta CrewAI Enterprise
+- Uma conta CrewAI AMP
 - Uma conta Zapier
 - Uma conta Slack (para este exemplo específico)
 
@@ -32,7 +32,7 @@ Este guia irá conduzi-lo pelo processo de configuração de triggers no Zapier
         - Conecte sua conta Slack, caso ainda não tenha feito isso.
     </Step>
 
-    <Step title="Configure a ação do CrewAI Enterprise">
+    <Step title="Configure a ação do CrewAI AMP">
         - Adicione uma nova etapa de ação ao seu Zap.
         - Escolha CrewAI+ como o app de ação e Kickoff como Evento de Ação.
 
@@ -41,8 +41,8 @@ Este guia irá conduzi-lo pelo processo de configuração de triggers no Zapier
         </Frame>
     </Step>
 
-    <Step title="Conecte sua conta CrewAI Enterprise">
-        - Conecte sua conta CrewAI Enterprise.
+    <Step title="Conecte sua conta CrewAI AMP">
+        - Conecte sua conta CrewAI AMP.
         - Selecione o Crew apropriado para seu fluxo de trabalho.
 
         <Frame>
@@ -51,8 +51,8 @@ Este guia irá conduzi-lo pelo processo de configuração de triggers no Zapier
         - Configure as entradas para o Crew usando os dados da mensagem do Slack.
     </Step>
 
-    <Step title="Formate a saída do CrewAI Enterprise">
-        - Adicione outra etapa de ação para formatar a saída de texto do CrewAI Enterprise.
+    <Step title="Formate a saída do CrewAI AMP">
+        - Adicione outra etapa de ação para formatar a saída de texto do CrewAI AMP.
         - Utilize as ferramentas de formatação do Zapier para converter a saída em Markdown para HTML.
 
         <Frame>
@@ -67,7 +67,7 @@ Este guia irá conduzi-lo pelo processo de configuração de triggers no Zapier
         - Adicione uma etapa final de ação para enviar a saída formatada por e-mail.
         - Escolha seu serviço de e-mail preferido (ex.: Gmail, Outlook).
         - Configure os detalhes do e-mail, incluindo destinatário, assunto e corpo.
-        - Insira a saída formatada do CrewAI Enterprise no corpo do e-mail.
+        - Insira a saída formatada do CrewAI AMP no corpo do e-mail.
 
         <Frame>
             <img src="/images/enterprise/zapier-7.png" alt="Zapier 7" />
@@ -97,8 +97,8 @@ Este guia irá conduzi-lo pelo processo de configuração de triggers no Zapier
 
 ## Dicas para o Sucesso
 
-- Certifique-se de que as entradas do CrewAI Enterprise estejam corretamente mapeadas a partir da mensagem do Slack.
+- Certifique-se de que as entradas do CrewAI AMP estejam corretamente mapeadas a partir da mensagem do Slack.
 - Teste seu Zap cuidadosamente antes de ativá-lo para identificar possíveis problemas.
 - Considere adicionar etapas de tratamento de erros para gerenciar possíveis falhas no fluxo.
 
-Seguindo estes passos, você terá configurado com sucesso triggers no Zapier para o CrewAI Enterprise, permitindo fluxos de trabalho automatizados disparados por mensagens no Slack e resultando em notificações por e-mail com a saída do CrewAI Enterprise.
\ No newline at end of file
+Seguindo estes passos, você terá configurado com sucesso triggers no Zapier para o CrewAI AMP, permitindo fluxos de trabalho automatizados disparados por mensagens no Slack e resultando em notificações por e-mail com a saída do CrewAI AMP.
\ No newline at end of file
diff --git a/docs/pt-BR/enterprise/integrations/asana.mdx b/docs/pt-BR/enterprise/integrations/asana.mdx
index 9de42d86f..21a46cf18 100644
--- a/docs/pt-BR/enterprise/integrations/asana.mdx
+++ b/docs/pt-BR/enterprise/integrations/asana.mdx
@@ -13,7 +13,7 @@ Permita que seus agentes gerenciem tarefas, projetos e a coordenação da equipe
 
 Antes de usar a integração com o Asana, assegure-se de ter:
 
-- Uma conta [CrewAI Enterprise](https://app.crewai.com) com assinatura ativa
+- Uma conta [CrewAI AMP](https://app.crewai.com) com assinatura ativa
 - Uma conta Asana com as permissões apropriadas
 - Sua conta Asana conectada através da [página de Integrações](https://app.crewai.com/crewai_plus/connectors)
 
@@ -21,7 +21,7 @@ Antes de usar a integração com o Asana, assegure-se de ter:
 
 ### 1. Conecte sua Conta Asana
 
-1. Acesse [CrewAI Enterprise Integrações](https://app.crewai.com/crewai_plus/connectors)
+1. Acesse [CrewAI AMP Integrações](https://app.crewai.com/crewai_plus/connectors)
 2. Encontre **Asana** na seção Integrações de Autenticação
 3. Clique em **Conectar** e complete o fluxo OAuth
 4. Conceda as permissões necessárias para gerenciamento de tarefas e projetos
diff --git a/docs/pt-BR/enterprise/integrations/box.mdx b/docs/pt-BR/enterprise/integrations/box.mdx
index 8845e9945..8cf5469c8 100644
--- a/docs/pt-BR/enterprise/integrations/box.mdx
+++ b/docs/pt-BR/enterprise/integrations/box.mdx
@@ -13,7 +13,7 @@ Permita que seus agentes gerenciem arquivos, pastas e documentos através do Box
 
 Antes de utilizar a integração com o Box, assegure-se de que você possui:
 
-- Uma conta [CrewAI Enterprise](https://app.crewai.com) com assinatura ativa
+- Uma conta [CrewAI AMP](https://app.crewai.com) com assinatura ativa
 - Uma conta Box com as permissões apropriadas
 - Sua conta Box conectada através da [página de Integrações](https://app.crewai.com/crewai_plus/connectors)
 
@@ -21,7 +21,7 @@ Antes de utilizar a integração com o Box, assegure-se de que você possui:
 
 ### 1. Conecte sua conta Box
 
-1. Acesse [Integrações do CrewAI Enterprise](https://app.crewai.com/crewai_plus/connectors)
+1. Acesse [Integrações do CrewAI AMP](https://app.crewai.com/crewai_plus/connectors)
 2. Encontre **Box** na seção de Integrações de Autenticação
 3. Clique em **Conectar** e conclua o fluxo de OAuth
 4. Conceda as permissões necessárias para gerenciamento de arquivos e pastas
diff --git a/docs/pt-BR/enterprise/integrations/clickup.mdx b/docs/pt-BR/enterprise/integrations/clickup.mdx
index 83cf7a216..e35f458f6 100644
--- a/docs/pt-BR/enterprise/integrations/clickup.mdx
+++ b/docs/pt-BR/enterprise/integrations/clickup.mdx
@@ -13,7 +13,7 @@ Permita que seus agentes gerenciem tarefas, projetos e fluxos de produtividade p
 
 Antes de utilizar a integração com o ClickUp, certifique-se de que você possui:
 
-- Uma conta [CrewAI Enterprise](https://app.crewai.com) com assinatura ativa
+- Uma conta [CrewAI AMP](https://app.crewai.com) com assinatura ativa
 - Uma conta ClickUp com as permissões apropriadas
 - Sua conta ClickUp conectada pela [Página de Integrações](https://app.crewai.com/crewai_plus/connectors)
 
@@ -21,7 +21,7 @@ Antes de utilizar a integração com o ClickUp, certifique-se de que você possu
 
 ### 1. Conecte sua Conta ClickUp
 
-1. Acesse [CrewAI Enterprise Integrações](https://app.crewai.com/crewai_plus/connectors)
+1. Acesse [CrewAI AMP Integrações](https://app.crewai.com/crewai_plus/connectors)
 2. Encontre **ClickUp** na seção Integrações de Autenticação
 3. Clique em **Conectar** e complete o fluxo OAuth
 4. Conceda as permissões necessárias para gerenciamento de tarefas e projetos
diff --git a/docs/pt-BR/enterprise/integrations/github.mdx b/docs/pt-BR/enterprise/integrations/github.mdx
index b5a238c28..eb43b0c6c 100644
--- a/docs/pt-BR/enterprise/integrations/github.mdx
+++ b/docs/pt-BR/enterprise/integrations/github.mdx
@@ -13,7 +13,7 @@ Permita que seus agentes gerenciem repositórios, issues e releases através do
 
 Antes de usar a integração do GitHub, assegure-se de ter:
 
-- Uma conta [CrewAI Enterprise](https://app.crewai.com) com assinatura ativa
+- Uma conta [CrewAI AMP](https://app.crewai.com) com assinatura ativa
 - Uma conta GitHub com permissões adequadas no repositório
 - Conta do GitHub conectada através da [página de Integrações](https://app.crewai.com/crewai_plus/connectors)
 
@@ -21,7 +21,7 @@ Antes de usar a integração do GitHub, assegure-se de ter:
 
 ### 1. Conecte sua conta GitHub
 
-1. Acesse [Integrações CrewAI Enterprise](https://app.crewai.com/crewai_plus/connectors)
+1. Acesse [Integrações CrewAI AMP](https://app.crewai.com/crewai_plus/connectors)
 2. Encontre **GitHub** na seção de Integrações de Autenticação
 3. Clique em **Conectar** e complete o fluxo OAuth
 4. Conceda as permissões necessárias para gerenciamento de repositório e issues
diff --git a/docs/pt-BR/enterprise/integrations/gmail.mdx b/docs/pt-BR/enterprise/integrations/gmail.mdx
index c16d4448f..6a281d2a6 100644
--- a/docs/pt-BR/enterprise/integrations/gmail.mdx
+++ b/docs/pt-BR/enterprise/integrations/gmail.mdx
@@ -13,7 +13,7 @@ Permita que seus agentes gerenciem e-mails, contatos e rascunhos através do Gma
 
 Antes de usar a integração com o Gmail, certifique-se de que você possui:
 
-- Uma conta [CrewAI Enterprise](https://app.crewai.com) com assinatura ativa
+- Uma conta [CrewAI AMP](https://app.crewai.com) com assinatura ativa
 - Uma conta do Gmail com as permissões adequadas
 - Conectou sua conta do Gmail através da [página de Integrações](https://app.crewai.com/crewai_plus/connectors)
 
@@ -21,7 +21,7 @@ Antes de usar a integração com o Gmail, certifique-se de que você possui:
 
 ### 1. Conecte sua Conta do Gmail
 
-1. Navegue até [Integrações CrewAI Enterprise](https://app.crewai.com/crewai_plus/connectors)
+1. Navegue até [Integrações CrewAI AMP](https://app.crewai.com/crewai_plus/connectors)
 2. Encontre **Gmail** na seção de Integrações de Autenticação
 3. Clique em **Conectar** e conclua o fluxo OAuth
 4. Conceda as permissões necessárias para o gerenciamento de e-mail e contato
diff --git a/docs/pt-BR/enterprise/integrations/google_calendar.mdx b/docs/pt-BR/enterprise/integrations/google_calendar.mdx
index bd413a9e3..d6df0edec 100644
--- a/docs/pt-BR/enterprise/integrations/google_calendar.mdx
+++ b/docs/pt-BR/enterprise/integrations/google_calendar.mdx
@@ -13,7 +13,7 @@ Permita que seus agentes gerenciem eventos de calendário, agendas e disponibili
 
 Antes de usar a integração com o Google Calendar, certifique-se de ter:
 
-- Uma conta [CrewAI Enterprise](https://app.crewai.com) com assinatura ativa
+- Uma conta [CrewAI AMP](https://app.crewai.com) com assinatura ativa
 - Uma conta Google com acesso ao Google Calendar
 - Sua conta Google conectada pela [página de Integrações](https://app.crewai.com/crewai_plus/connectors)
 
@@ -21,7 +21,7 @@ Antes de usar a integração com o Google Calendar, certifique-se de ter:
 
 ### 1. Conecte sua Conta Google
 
-1. Acesse [Integrações do CrewAI Enterprise](https://app.crewai.com/crewai_plus/connectors)
+1. Acesse [Integrações do CrewAI AMP](https://app.crewai.com/crewai_plus/connectors)
 2. Encontre **Google Calendar** na seção de Integrações de Autenticação
 3. Clique em **Conectar** e complete o fluxo OAuth
 4. Conceda as permissões necessárias para acesso ao calendário e contatos
diff --git a/docs/pt-BR/enterprise/integrations/google_sheets.mdx b/docs/pt-BR/enterprise/integrations/google_sheets.mdx
index eb7e7a0de..39072eba2 100644
--- a/docs/pt-BR/enterprise/integrations/google_sheets.mdx
+++ b/docs/pt-BR/enterprise/integrations/google_sheets.mdx
@@ -13,7 +13,7 @@ Permita que seus agentes gerenciem dados de planilhas por meio do Google Sheets.
 
 Antes de utilizar a integração com o Google Sheets, certifique-se de que você possui:
 
-- Uma conta [CrewAI Enterprise](https://app.crewai.com) com assinatura ativa
+- Uma conta [CrewAI AMP](https://app.crewai.com) com assinatura ativa
 - Uma conta Google com acesso ao Google Sheets
 - Sua conta Google conectada pela [página de integrações](https://app.crewai.com/crewai_plus/connectors)
 - Planilhas com cabeçalhos de coluna adequados para operações com dados
@@ -22,7 +22,7 @@ Antes de utilizar a integração com o Google Sheets, certifique-se de que você
 
 ### 1. Conecte sua Conta Google
 
-1. Acesse [Integrações do CrewAI Enterprise](https://app.crewai.com/crewai_plus/connectors)
+1. Acesse [Integrações do CrewAI AMP](https://app.crewai.com/crewai_plus/connectors)
 2. Localize **Google Sheets** na seção Integrações de Autenticação
 3. Clique em **Conectar** e conclua o fluxo OAuth
 4. Conceda as permissões necessárias para acesso à planilha
diff --git a/docs/pt-BR/enterprise/integrations/hubspot.mdx b/docs/pt-BR/enterprise/integrations/hubspot.mdx
index d3207aabf..03a03a2b6 100644
--- a/docs/pt-BR/enterprise/integrations/hubspot.mdx
+++ b/docs/pt-BR/enterprise/integrations/hubspot.mdx
@@ -13,7 +13,7 @@ Permita que seus agentes gerenciem empresas e contatos dentro do HubSpot. Crie n
 
 Antes de utilizar a integração com o HubSpot, certifique-se de que você possui:
 
-- Uma conta [CrewAI Enterprise](https://app.crewai.com) com assinatura ativa.
+- Uma conta [CrewAI AMP](https://app.crewai.com) com assinatura ativa.
 - Uma conta HubSpot com permissões adequadas.
 - Sua conta HubSpot conectada pela [página de Integrações](https://app.crewai.com/crewai_plus/connectors).
 
@@ -21,7 +21,7 @@ Antes de utilizar a integração com o HubSpot, certifique-se de que você possu
 
 ### 1. Conecte Sua Conta HubSpot
 
-1. Navegue até [CrewAI Enterprise Integrações](https://app.crewai.com/crewai_plus/connectors).
+1. Navegue até [CrewAI AMP Integrações](https://app.crewai.com/crewai_plus/connectors).
 2. Encontre **HubSpot** na seção de Integrações de Autenticação.
 3. Clique em **Conectar** e complete o fluxo OAuth.
 4. Conceda as permissões necessárias para gerenciamento de empresas e contatos.
diff --git a/docs/pt-BR/enterprise/integrations/jira.mdx b/docs/pt-BR/enterprise/integrations/jira.mdx
index 2fde5e331..748eaff15 100644
--- a/docs/pt-BR/enterprise/integrations/jira.mdx
+++ b/docs/pt-BR/enterprise/integrations/jira.mdx
@@ -13,7 +13,7 @@ Permita que seus agentes gerenciem problemas, projetos e fluxos de trabalho pelo
 
 Antes de usar a integração com o Jira, certifique-se de ter:
 
-- Uma conta [CrewAI Enterprise](https://app.crewai.com) com assinatura ativa
+- Uma conta [CrewAI AMP](https://app.crewai.com) com assinatura ativa
 - Uma conta Jira com permissões adequadas para o projeto
 - Sua conta Jira conectada pela [Página de Integrações](https://app.crewai.com/crewai_plus/connectors)
 
@@ -21,7 +21,7 @@ Antes de usar a integração com o Jira, certifique-se de ter:
 
 ### 1. Conectar Sua Conta Jira
 
-1. Acesse [Integrações CrewAI Enterprise](https://app.crewai.com/crewai_plus/connectors)
+1. Acesse [Integrações CrewAI AMP](https://app.crewai.com/crewai_plus/connectors)
 2. Encontre **Jira** na seção de Integrações de Autenticação
 3. Clique em **Conectar** e complete o fluxo do OAuth
 4. Conceda as permissões necessárias para gestão de issues e projetos
diff --git a/docs/pt-BR/enterprise/integrations/linear.mdx b/docs/pt-BR/enterprise/integrations/linear.mdx
index ff5132ecd..8f7948d33 100644
--- a/docs/pt-BR/enterprise/integrations/linear.mdx
+++ b/docs/pt-BR/enterprise/integrations/linear.mdx
@@ -13,7 +13,7 @@ Permita que seus agentes gerenciem issues, projetos e fluxos de trabalho de dese
 
 Antes de utilizar a integração com o Linear, certifique-se de que você possui:
 
-- Uma conta [CrewAI Enterprise](https://app.crewai.com) com uma assinatura ativa
+- Uma conta [CrewAI AMP](https://app.crewai.com) com uma assinatura ativa
 - Uma conta Linear com permissões apropriadas no workspace
 - Conectou sua conta Linear através da [página de Integrações](https://app.crewai.com/crewai_plus/connectors)
 
@@ -21,7 +21,7 @@ Antes de utilizar a integração com o Linear, certifique-se de que você possui
 
 ### 1. Conecte sua Conta Linear
 
-1. Navegue até [Integrações CrewAI Enterprise](https://app.crewai.com/crewai_plus/connectors)
+1. Navegue até [Integrações CrewAI AMP](https://app.crewai.com/crewai_plus/connectors)
 2. Encontre **Linear** na seção Integrações de Autenticação
 3. Clique em **Conectar** e complete o fluxo OAuth
 4. Conceda as permissões necessárias para gerenciamento de issues e projetos
diff --git a/docs/pt-BR/enterprise/integrations/notion.mdx b/docs/pt-BR/enterprise/integrations/notion.mdx
index 169b0a370..d0e8b1ff4 100644
--- a/docs/pt-BR/enterprise/integrations/notion.mdx
+++ b/docs/pt-BR/enterprise/integrations/notion.mdx
@@ -13,7 +13,7 @@ Permita que seus agentes gerenciem páginas, bancos de dados e conteúdos atrav
 
 Antes de usar a integração com o Notion, certifique-se de que você tem:
 
-- Uma conta [CrewAI Enterprise](https://app.crewai.com) com assinatura ativa
+- Uma conta [CrewAI AMP](https://app.crewai.com) com assinatura ativa
 - Uma conta Notion com permissões adequadas no workspace
 - Sua conta Notion conectada através da [página de Integrações](https://app.crewai.com/crewai_plus/connectors)
 
@@ -21,7 +21,7 @@ Antes de usar a integração com o Notion, certifique-se de que você tem:
 
 ### 1. Conecte sua Conta Notion
 
-1. Acesse [Integrações do CrewAI Enterprise](https://app.crewai.com/crewai_plus/connectors)
+1. Acesse [Integrações do CrewAI AMP](https://app.crewai.com/crewai_plus/connectors)
 2. Procure por **Notion** na seção de Integrações de Autenticação
 3. Clique em **Conectar** e complete o fluxo de OAuth
 4. Conceda as permissões necessárias para gerenciamento de páginas e bancos de dados
diff --git a/docs/pt-BR/enterprise/integrations/salesforce.mdx b/docs/pt-BR/enterprise/integrations/salesforce.mdx
index 177fe0dfc..c39ead179 100644
--- a/docs/pt-BR/enterprise/integrations/salesforce.mdx
+++ b/docs/pt-BR/enterprise/integrations/salesforce.mdx
@@ -13,7 +13,7 @@ Permita que seus agentes gerenciem relacionamentos com clientes, processos de ve
 
 Antes de usar a integração Salesforce, certifique-se de que você possui:
 
-- Uma conta [CrewAI Enterprise](https://app.crewai.com) com assinatura ativa
+- Uma conta [CrewAI AMP](https://app.crewai.com) com assinatura ativa
 - Uma conta Salesforce com permissões apropriadas
 - Sua conta Salesforce conectada via a [página de Integrações](https://app.crewai.com/integrations)
 
diff --git a/docs/pt-BR/enterprise/integrations/shopify.mdx b/docs/pt-BR/enterprise/integrations/shopify.mdx
index 895d08739..0496f8a5e 100644
--- a/docs/pt-BR/enterprise/integrations/shopify.mdx
+++ b/docs/pt-BR/enterprise/integrations/shopify.mdx
@@ -13,7 +13,7 @@ Permita que seus agentes gerenciem operações de e-commerce através do Shopify
 
 Antes de utilizar a integração com o Shopify, certifique-se de que você possui:
 
-- Uma conta [CrewAI Enterprise](https://app.crewai.com) com uma assinatura ativa
+- Uma conta [CrewAI AMP](https://app.crewai.com) com uma assinatura ativa
 - Uma loja Shopify com permissões administrativas adequadas
 - Sua loja Shopify conectada através da [página de Integrações](https://app.crewai.com/integrations)
 
diff --git a/docs/pt-BR/enterprise/integrations/slack.mdx b/docs/pt-BR/enterprise/integrations/slack.mdx
index c2f6e9edb..d0c6026e1 100644
--- a/docs/pt-BR/enterprise/integrations/slack.mdx
+++ b/docs/pt-BR/enterprise/integrations/slack.mdx
@@ -13,7 +13,7 @@ Permita que seus agentes gerenciem a comunicação da equipe pelo Slack. Envie m
 
 Antes de usar a integração com o Slack, certifique-se de que você tenha:
 
-- Uma conta [CrewAI Enterprise](https://app.crewai.com) com assinatura ativa
+- Uma conta [CrewAI AMP](https://app.crewai.com) com assinatura ativa
 - Um workspace do Slack com permissões apropriadas
 - Seu workspace do Slack conectado por meio da [página de Integrações](https://app.crewai.com/integrations)
 
diff --git a/docs/pt-BR/enterprise/integrations/stripe.mdx b/docs/pt-BR/enterprise/integrations/stripe.mdx
index 2e917caa4..7b20dccb3 100644
--- a/docs/pt-BR/enterprise/integrations/stripe.mdx
+++ b/docs/pt-BR/enterprise/integrations/stripe.mdx
@@ -13,7 +13,7 @@ Permita que seus agentes gerenciem pagamentos, assinaturas e faturamento de clie
 
 Antes de usar a integração com o Stripe, certifique-se de que você tem:
 
-- Uma conta [CrewAI Enterprise](https://app.crewai.com) com uma assinatura ativa
+- Uma conta [CrewAI AMP](https://app.crewai.com) com uma assinatura ativa
 - Uma conta Stripe com permissões apropriadas de API
 - Sua conta Stripe conectada através da [página de Integrações](https://app.crewai.com/integrations)
 
diff --git a/docs/pt-BR/enterprise/integrations/zendesk.mdx b/docs/pt-BR/enterprise/integrations/zendesk.mdx
index 3177e9dd1..8f6f0026e 100644
--- a/docs/pt-BR/enterprise/integrations/zendesk.mdx
+++ b/docs/pt-BR/enterprise/integrations/zendesk.mdx
@@ -13,7 +13,7 @@ Permita que seus agentes gerenciem operações de suporte ao cliente através do
 
 Antes de usar a integração com o Zendesk, certifique-se de que você possui:
 
-- Uma conta [CrewAI Enterprise](https://app.crewai.com) com uma assinatura ativa
+- Uma conta [CrewAI AMP](https://app.crewai.com) com uma assinatura ativa
 - Uma conta Zendesk com permissões apropriadas de API
 - Sua conta Zendesk conectada através da [página de Integrações](https://app.crewai.com/integrations)
 
diff --git a/docs/pt-BR/enterprise/introduction.mdx b/docs/pt-BR/enterprise/introduction.mdx
index bd50ac1f4..f85dfe14d 100644
--- a/docs/pt-BR/enterprise/introduction.mdx
+++ b/docs/pt-BR/enterprise/introduction.mdx
@@ -1,5 +1,5 @@
 ---
-title: "CrewAI Enterprise"
+title: "CrewAI AMP"
 description: "Implemente, monitore e escale seus fluxos de trabalho de agentes de IA"
 icon: "globe"
 mode: "wide"
@@ -7,13 +7,13 @@ mode: "wide"
 
 ## Introdução
 
-CrewAI Enterprise fornece uma plataforma para implementar, monitorar e escalar seus crews e agentes em um ambiente de produção.
+CrewAI AMP fornece uma plataforma para implementar, monitorar e escalar seus crews e agentes em um ambiente de produção.
 
 <Frame>
-  <img src="/images/enterprise/crewai-enterprise-dashboard.png" alt="CrewAI Enterprise Dashboard" />
+  <img src="/images/enterprise/crewai-enterprise-dashboard.png" alt="CrewAI AMP Dashboard" />
 </Frame>
 
-CrewAI Enterprise expande o poder do framework open-source com funcionalidades projetadas para implantações em produção, colaboração e escalabilidade. Implemente seus crews em uma infraestrutura gerenciada e monitore sua execução em tempo real.
+CrewAI AMP expande o poder do framework open-source com funcionalidades projetadas para implantações em produção, colaboração e escalabilidade. Implemente seus crews em uma infraestrutura gerenciada e monitore sua execução em tempo real.
 
 ## Principais Funcionalidades
 
diff --git a/docs/pt-BR/enterprise/resources/frequently-asked-questions.mdx b/docs/pt-BR/enterprise/resources/frequently-asked-questions.mdx
index 414a854ba..c197a00cd 100644
--- a/docs/pt-BR/enterprise/resources/frequently-asked-questions.mdx
+++ b/docs/pt-BR/enterprise/resources/frequently-asked-questions.mdx
@@ -1,6 +1,6 @@
 ---
 title: FAQs
-description: "Perguntas frequentes sobre CrewAI Enterprise"
+description: "Perguntas frequentes sobre CrewAI AMP"
 icon: "circle-question"
 mode: "wide"
 ---
diff --git a/docs/pt-BR/installation.mdx b/docs/pt-BR/installation.mdx
index 05f3652b6..12f88a05f 100644
--- a/docs/pt-BR/installation.mdx
+++ b/docs/pt-BR/installation.mdx
@@ -163,7 +163,7 @@ Recomendamos utilizar o template de scaffolding `YAML` para uma abordagem estrut
 <Note type="info">
 Para equipes e organizações, o CrewAI oferece opções de implantação corporativa que eliminam a complexidade da configuração:
 
-### CrewAI Enterprise (SaaS)
+### CrewAI AMP (SaaS)
 - Zero instalação necessária - basta se cadastrar gratuitamente em [app.crewai.com](https://app.crewai.com)
 - Atualizações e manutenção automáticas
 - Infraestrutura e escalabilidade gerenciadas
diff --git a/docs/pt-BR/learn/human-input-on-execution.mdx b/docs/pt-BR/learn/human-input-on-execution.mdx
index cc7167076..847923f38 100644
--- a/docs/pt-BR/learn/human-input-on-execution.mdx
+++ b/docs/pt-BR/learn/human-input-on-execution.mdx
@@ -1,7 +1,7 @@
 ---
 title: Input Humano na Execução
 description: Integrando o CrewAI com input humano durante a execução em processos complexos de tomada de decisão e aproveitando ao máximo todos os atributos e ferramentas do agente.
-icon: user-check
+icon: user-plus
 mode: "wide"
 ---
 
diff --git a/docs/pt-BR/learn/llm-selection-guide.mdx b/docs/pt-BR/learn/llm-selection-guide.mdx
index 66b721dba..fc0a25af8 100644
--- a/docs/pt-BR/learn/llm-selection-guide.mdx
+++ b/docs/pt-BR/learn/llm-selection-guide.mdx
@@ -394,7 +394,7 @@ Em vez de repetir o framework estratégico, segue um checklist tático para impl
   
   <Step title="Valide com Testes Empresariais" icon="test-tube">
     **Após colocar os agentes em produção:**
-    - Use [CrewAI Enterprise platform](https://app.crewai.com) para testar seleções de modelo A/B
+    - Use [CrewAI AMP platform](https://app.crewai.com) para testar seleções de modelo A/B
     - Execute múltiplas iterações com inputs reais para medir consistência e performance
     - Compare custo vs performance na configuração otimizada
     - Compartilhe resultados com o time para tomada coletiva de decisão
@@ -541,7 +541,7 @@ Foque em entender seus requisitos primeiro, e então escolha modelos que melhor
 
 ### Validação de Modelos em Nível Enterprise
 
-Para equipes sérias sobre otimização, a **plataforma CrewAI Enterprise** oferece testes sofisticados que vão além do CLI. Ela permite avaliação completa para decisões orientadas por dados na estratégia de LLM.
+Para equipes sérias sobre otimização, a **plataforma CrewAI AMP** oferece testes sofisticados que vão além do CLI. Ela permite avaliação completa para decisões orientadas por dados na estratégia de LLM.
 
 <Frame>
   ![Enterprise Testing Interface](/images/enterprise/enterprise-testing.png)
diff --git a/docs/pt-BR/observability/neatlogs.mdx b/docs/pt-BR/observability/neatlogs.mdx
new file mode 100644
index 000000000..24b17cfce
--- /dev/null
+++ b/docs/pt-BR/observability/neatlogs.mdx
@@ -0,0 +1,134 @@
+---
+title: Neatlogs Integration
+description: Understand, debug, and share your CrewAI agent runs
+icon: magnifying-glass-chart
+mode: "wide"
+---
+
+# Introduction
+
+Neatlogs helps you **see what your agent did**, **why**, and **share it**.
+
+It captures every step: thoughts, tool calls, responses, evaluations. No raw logs. Just clear, structured traces. Great for debugging and collaboration.
+
+## Why use Neatlogs?
+
+CrewAI agents use multiple tools and reasoning steps. When something goes wrong, you need context — not just errors.
+
+Neatlogs lets you:
+
+- Follow the full decision path
+- Add feedback directly on steps
+- Chat with the trace using AI assistant
+- Share runs publicly for feedback
+- Turn insights into tasks
+
+All in one place.
+
+Manage your traces effortlessly
+
+![Traces](/images/neatlogs-1.png)
+![Trace Response](/images/neatlogs-2.png)
+
+The best UX to view a CrewAI trace. Post comments anywhere you want. Use AI to debug.
+
+![Trace Details](/images/neatlogs-3.png)
+![Ai Chat Bot With A Trace](/images/neatlogs-4.png)
+![Comments Drawer](/images/neatlogs-5.png)
+
+## Core Features
+
+- **Trace Viewer**: Track thoughts, tools, and decisions in sequence
+- **Inline Comments**: Tag teammates on any trace step
+- **Feedback & Evaluation**: Mark outputs as correct or incorrect
+- **Error Highlighting**: Automatic flagging of API/tool failures
+- **Task Conversion**: Convert comments into assigned tasks
+- **Ask the Trace (AI)**: Chat with your trace using Neatlogs AI bot
+- **Public Sharing**: Publish trace links to your community
+
+## Quick Setup with CrewAI
+
+<Steps>
+  <Step title="Sign Up & Get API Key">
+    Visit [neatlogs.com](https://neatlogs.com/?utm_source=crewAI-docs), create a project, copy the API key.
+  </Step>
+  <Step title="Install SDK">
+    ```bash
+    pip install neatlogs
+    ```
+    (Latest version 0.8.0, Python 3.8+; MIT license)
+  </Step>
+  <Step title="Initialize Neatlogs">
+    Before starting Crew agents, add:
+
+    ```python
+    import neatlogs
+    neatlogs.init("YOUR_PROJECT_API_KEY")
+    ```
+
+    Agents run as usual. Neatlogs captures everything automatically.
+
+  </Step>
+</Steps>
+
+
+
+## Under the Hood
+
+According to GitHub, Neatlogs:
+
+- Captures thoughts, tool calls, responses, errors, and token stats
+- Supports AI-powered task generation and robust evaluation workflows
+
+All with just two lines of code.
+
+
+
+## Watch It Work
+
+### 🔍 Full Demo (4 min)
+
+<iframe
+  className="w-full aspect-video rounded-xl"
+  src="https://www.youtube.com/embed/8KDme9T2I7Q?si=b8oHteaBwFNs_Duk"
+  title="NeatLogs overview"
+  frameBorder="0"
+  allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture"
+  allowFullScreen
+></iframe>
+
+### ⚙️ CrewAI Integration (30 s)
+
+<iframe
+  className="w-full aspect-video rounded-xl"
+  src="https://www.loom.com/embed/9c78b552af43452bb3e4783cb8d91230?sid=e9d7d370-a91a-49b0-809e-2f375d9e801d"
+  title="Loom video player"
+  frameBorder="0"
+  allowFullScreen
+></iframe>
+
+
+
+## Links & Support
+
+- 📘 [Neatlogs Docs](https://docs.neatlogs.com/)
+- 🔐 [Dashboard & API Key](https://app.neatlogs.com/)
+- 🐦 [Follow on Twitter](https://twitter.com/neatlogs)
+- 📧 Contact: hello@neatlogs.com
+- 🛠 [GitHub SDK](https://github.com/NeatLogs/neatlogs)
+
+
+
+## TL;DR
+
+With just:
+
+```bash
+pip install neatlogs
+
+import neatlogs
+neatlogs.init("YOUR_API_KEY")
+
+You can now capture, understand, share, and act on your CrewAI agent runs in seconds.
+No setup overhead. Full trace transparency. Full team collaboration.
+```
diff --git a/docs/pt-BR/quickstart.mdx b/docs/pt-BR/quickstart.mdx
index 9f9b622a2..763cc9e52 100644
--- a/docs/pt-BR/quickstart.mdx
+++ b/docs/pt-BR/quickstart.mdx
@@ -204,9 +204,9 @@ Siga os passos abaixo para começar a tripular! 🚣‍♂️
   </Step>
 
   <Step title="Alternativa para Empresas: Crie no Crew Studio">
-  Para usuários do CrewAI Enterprise, você pode criar a mesma tripulação sem escrever código:
+  Para usuários do CrewAI AMP, você pode criar a mesma tripulação sem escrever código:
 
-  1. Faça login na sua conta CrewAI Enterprise (crie uma conta gratuita em [app.crewai.com](https://app.crewai.com))
+  1. Faça login na sua conta CrewAI AMP (crie uma conta gratuita em [app.crewai.com](https://app.crewai.com))
   2. Abra o Crew Studio
   3. Digite qual automação deseja construir
   4. Crie suas tarefas visualmente e conecte-as em sequência
@@ -214,8 +214,8 @@ Siga os passos abaixo para começar a tripular! 🚣‍♂️
 
   ![Crew Studio Quickstart](/images/enterprise/crew-studio-interface.png)
 
-  <Card title="Experimente o CrewAI Enterprise" icon="rocket" href="https://app.crewai.com">
-    Comece sua conta gratuita no CrewAI Enterprise
+  <Card title="Experimente o CrewAI AMP" icon="rocket" href="https://app.crewai.com">
+    Comece sua conta gratuita no CrewAI AMP
   </Card>
   </Step>
   <Step title="Veja seu relatório final">
@@ -335,9 +335,9 @@ email_summarizer_task:
 
 ## Fazendo o Deploy da Sua Tripulação
 
-A forma mais fácil de fazer deploy da sua tripulação em produção é através da [CrewAI Enterprise](http://app.crewai.com).
+A forma mais fácil de fazer deploy da sua tripulação em produção é através da [CrewAI AMP](http://app.crewai.com).
 
-Assista a este vídeo tutorial para uma demonstração detalhada de como fazer deploy da sua tripulação na [CrewAI Enterprise](http://app.crewai.com) usando a CLI.
+Assista a este vídeo tutorial para uma demonstração detalhada de como fazer deploy da sua tripulação na [CrewAI AMP](http://app.crewai.com) usando a CLI.
 
 <iframe
   className="w-full aspect-video rounded-xl"
@@ -354,7 +354,7 @@ Assista a este vídeo tutorial para uma demonstração detalhada de como fazer d
     icon="rocket"
     href="http://app.crewai.com"
   >
-    Comece com o CrewAI Enterprise e faça o deploy da sua tripulação em ambiente de produção com apenas alguns cliques.
+    Comece com o CrewAI AMP e faça o deploy da sua tripulação em ambiente de produção com apenas alguns cliques.
   </Card>
   <Card
     title="Junte-se à Comunidade"
diff --git a/docs/pt-BR/tools/automation/zapieractionstool.mdx b/docs/pt-BR/tools/automation/zapieractionstool.mdx
new file mode 100644
index 000000000..468b77eda
--- /dev/null
+++ b/docs/pt-BR/tools/automation/zapieractionstool.mdx
@@ -0,0 +1,59 @@
+---
+title: Zapier Actions Tool
+description: The `ZapierActionsAdapter` exposes Zapier actions as CrewAI tools for automation.
+icon: bolt
+mode: "wide"
+---
+
+# `ZapierActionsAdapter`
+
+## Description
+
+Use the Zapier adapter to list and call Zapier actions as CrewAI tools. This enables agents to trigger automations across thousands of apps.
+
+## Installation
+
+This adapter is included with `crewai-tools`. No extra install required.
+
+## Environment Variables
+
+- `ZAPIER_API_KEY` (required): Zapier API key. Get one from the Zapier Actions dashboard at https://actions.zapier.com/ (create an account, then generate an API key). You can also pass `zapier_api_key` directly when constructing the adapter.
+
+## Example
+
+```python Code
+from crewai import Agent, Task, Crew
+from crewai_tools.adapters.zapier_adapter import ZapierActionsAdapter
+
+adapter = ZapierActionsAdapter(api_key="your_zapier_api_key")
+tools = adapter.tools()
+
+agent = Agent(
+    role="Automator",
+    goal="Execute Zapier actions",
+    backstory="Automation specialist",
+    tools=tools,
+    verbose=True,
+)
+
+task = Task(
+    description="Create a new Google Sheet and add a row using Zapier actions",
+    expected_output="Confirmation with created resource IDs",
+    agent=agent,
+)
+
+crew = Crew(agents=[agent], tasks=[task])
+result = crew.kickoff()
+```
+
+## Notes & limits
+
+- The adapter lists available actions for your key and creates `BaseTool` wrappers dynamically.
+- Handle action‑specific required fields in your task instructions or tool call.
+- Rate limits depend on your Zapier plan; see the Zapier Actions docs.
+
+## Notes
+
+- The adapter fetches available actions and generates `BaseTool` wrappers dynamically.
+
+
diff --git a/docs/pt-BR/tools/cloud-storage/bedrockinvokeagenttool.mdx b/docs/pt-BR/tools/cloud-storage/bedrockinvokeagenttool.mdx
deleted file mode 100644
index 5b17b8862..000000000
--- a/docs/pt-BR/tools/cloud-storage/bedrockinvokeagenttool.mdx
+++ /dev/null
@@ -1,188 +0,0 @@
----
-title: Ferramenta Bedrock Invoke Agent
-description: Permite que agentes CrewAI invoquem Amazon Bedrock Agents e aproveitem suas capacidades em seus fluxos de trabalho
-icon: aws
-mode: "wide"
----
-
-# `BedrockInvokeAgentTool`
-
-A `BedrockInvokeAgentTool` permite que agentes CrewAI invoquem Amazon Bedrock Agents e aproveitem suas capacidades em seus fluxos de trabalho.
-
-## Instalação
-
-```bash
-uv pip install 'crewai[tools]'
-```
-
-## Requisitos
-
-- Credenciais AWS configuradas (através de variáveis de ambiente ou AWS CLI)
-- Pacotes `boto3` e `python-dotenv`
-- Acesso aos Amazon Bedrock Agents
-
-## Uso
-
-Veja como usar a ferramenta com um agente CrewAI:
-
-```python {2, 4-8}
-from crewai import Agent, Task, Crew
-from crewai_tools.aws.bedrock.agents.invoke_agent_tool import BedrockInvokeAgentTool
-
-# Initialize the tool
-agent_tool = BedrockInvokeAgentTool(
-    agent_id="your-agent-id",
-    agent_alias_id="your-agent-alias-id"
-)
-
-# Create a CrewAI agent that uses the tool
-aws_expert = Agent(
-    role='AWS Service Expert',
-    goal='Help users understand AWS services and quotas',
-    backstory='I am an expert in AWS services and can provide detailed information about them.',
-    tools=[agent_tool],
-    verbose=True
-)
-
-# Create a task for the agent
-quota_task = Task(
-    description="Find out the current service quotas for EC2 in us-west-2 and explain any recent changes.",
-    agent=aws_expert
-)
-
-# Create a crew with the agent
-crew = Crew(
-    agents=[aws_expert],
-    tasks=[quota_task],
-    verbose=2
-)
-
-# Run the crew
-result = crew.kickoff()
-print(result)
-```
-
-## Argumentos da Ferramenta
-
-| Argumento | Tipo | Obrigatório | Padrão   | Descrição                                           |
-|:----------|:-----|:------------|:---------|:----------------------------------------------------|
-| **agent_id** | `str` | Sim       | None     | O identificador único do agente Bedrock              |
-| **agent_alias_id** | `str` | Sim  | None     | O identificador único do alias do agente             |
-| **session_id** | `str` | Não     | timestamp | O identificador único da sessão                      |
-| **enable_trace** | `bool` | Não  | False    | Define se o trace deve ser habilitado para debug     |
-| **end_session** | `bool` | Não   | False    | Define se a sessão deve ser encerrada após invocação |
-| **description** | `str` | Não    | None     | Descrição personalizada para a ferramenta            |
-
-## Variáveis de Ambiente
-
-```bash
-BEDROCK_AGENT_ID=your-agent-id           # Alternativa para passar agent_id
-BEDROCK_AGENT_ALIAS_ID=your-agent-alias-id # Alternativa para passar agent_alias_id
-AWS_REGION=your-aws-region               # Padrão é us-west-2
-AWS_ACCESS_KEY_ID=your-access-key        # Necessário para autenticação AWS
-AWS_SECRET_ACCESS_KEY=your-secret-key    # Necessário para autenticação AWS
-```
-
-## Uso Avançado
-
-### Fluxo de Trabalho Multiagente com Gerenciamento de Sessão
-
-```python {2, 4-22}
-from crewai import Agent, Task, Crew, Process
-from crewai_tools.aws.bedrock.agents.invoke_agent_tool import BedrockInvokeAgentTool
-
-# Initialize tools with session management
-initial_tool = BedrockInvokeAgentTool(
-    agent_id="your-agent-id",
-    agent_alias_id="your-agent-alias-id",
-    session_id="custom-session-id"
-)
-
-followup_tool = BedrockInvokeAgentTool(
-    agent_id="your-agent-id",
-    agent_alias_id="your-agent-alias-id",
-    session_id="custom-session-id"
-)
-
-final_tool = BedrockInvokeAgentTool(
-    agent_id="your-agent-id",
-    agent_alias_id="your-agent-alias-id",
-    session_id="custom-session-id",
-    end_session=True
-)
-
-# Create agents for different stages
-researcher = Agent(
-    role='AWS Service Researcher',
-    goal='Gather information about AWS services',
-    backstory='I am specialized in finding detailed AWS service information.',
-    tools=[initial_tool]
-)
-
-analyst = Agent(
-    role='Service Compatibility Analyst',
-    goal='Analyze service compatibility and requirements',
-    backstory='I analyze AWS services for compatibility and integration possibilities.',
-    tools=[followup_tool]
-)
-
-summarizer = Agent(
-    role='Technical Documentation Writer',
-    goal='Create clear technical summaries',
-    backstory='I specialize in creating clear, concise technical documentation.',
-    tools=[final_tool]
-)
-
-# Create tasks
-research_task = Task(
-    description="Find all available AWS services in us-west-2 region.",
-    agent=researcher
-)
-
-analysis_task = Task(
-    description="Analyze which services support IPv6 and their implementation requirements.",
-    agent=analyst
-)
-
-summary_task = Task(
-    description="Create a summary of IPv6-compatible services and their key features.",
-    agent=summarizer
-)
-
-# Create a crew with the agents and tasks
-crew = Crew(
-    agents=[researcher, analyst, summarizer],
-    tasks=[research_task, analysis_task, summary_task],
-    process=Process.sequential,
-    verbose=2
-)
-
-# Run the crew
-result = crew.kickoff()
-```
-
-## Casos de Uso
-
-### Colaborações Híbridas Multiagente
-- Crie fluxos de trabalho onde agentes CrewAI colaboram com agentes Bedrock gerenciados executando como serviços na AWS
-- Permita cenários em que o processamento de dados sensíveis ocorre dentro do seu ambiente AWS enquanto outros agentes operam externamente
-- Conecte agentes CrewAI on-premises a agentes Bedrock baseados na nuvem para fluxos de trabalho distribuídos de inteligência
-
-### Soberania e Conformidade de Dados
-- Mantenha fluxos de trabalho agentivos sensíveis a dados dentro do seu ambiente AWS enquanto permite que agentes CrewAI externos orquestrem tarefas
-- Mantenha conformidade com requisitos de residência de dados processando informações sensíveis somente em sua conta AWS
-- Permita colaborações multiagentes seguras onde alguns agentes não podem acessar dados privados da sua organização
-
-### Integração Transparente com Serviços AWS
-- Acesse qualquer serviço AWS por meio do Amazon Bedrock Actions sem escrever código de integração complexo
-- Permita que agentes CrewAI interajam com serviços AWS usando solicitações em linguagem natural
-- Aproveite as capacidades pré-construídas dos agentes Bedrock para interagir com serviços AWS como Bedrock Knowledge Bases, Lambda e outros
-
-### Arquiteturas de Agentes Híbridos Escaláveis
-- Realize tarefas computacionalmente intensivas em agentes Bedrock gerenciados enquanto tarefas leves rodam em CrewAI
-- Escale o processamento de agentes distribuindo cargas de trabalho entre agentes CrewAI locais e agentes Bedrock na nuvem
-
-### Colaboração de Agentes Entre Organizações
-- Permita colaboração segura entre agentes CrewAI da sua organização e agentes Bedrock de organizações parceiras
-- Crie fluxos de trabalho onde a expertise externa de agentes Bedrock pode ser incorporada sem expor dados sensíveis
-- Construa ecossistemas de agentes que abrangem fronteiras organizacionais mantendo segurança e controle de dados
\ No newline at end of file
diff --git a/docs/pt-BR/tools/database-data/mongodbvectorsearchtool.mdx b/docs/pt-BR/tools/database-data/mongodbvectorsearchtool.mdx
new file mode 100644
index 000000000..09c5ee518
--- /dev/null
+++ b/docs/pt-BR/tools/database-data/mongodbvectorsearchtool.mdx
@@ -0,0 +1,169 @@
+---
+title: MongoDB Vector Search Tool
+description: The `MongoDBVectorSearchTool` performs vector search on MongoDB Atlas with optional indexing helpers.
+icon: "leaf"
+mode: "wide"
+---
+
+# `MongoDBVectorSearchTool`
+
+## Description
+
+Perform vector similarity queries on MongoDB Atlas collections. Supports index creation helpers and bulk insert of embedded texts.
+
+MongoDB Atlas supports native vector search. Learn more:
+https://www.mongodb.com/docs/atlas/atlas-vector-search/vector-search-overview/
+
+## Installation
+
+Install with the MongoDB extra:
+
+```shell
+pip install crewai-tools[mongodb]
+```
+
+or
+
+```shell
+uv add crewai-tools --extra mongodb
+```
+
+## Parameters
+
+### Initialization
+
+- `connection_string` (str, required)
+- `database_name` (str, required)
+- `collection_name` (str, required)
+- `vector_index_name` (str, default `vector_index`)
+- `text_key` (str, default `text`)
+- `embedding_key` (str, default `embedding`)
+- `dimensions` (int, default `1536`)
+
+### Run Parameters
+
+- `query` (str, required): Natural language query to embed and search.
+
+## Quick start
+
+```python Code
+from crewai_tools import MongoDBVectorSearchTool
+
+tool = MongoDBVectorSearchTool(
+  connection_string="mongodb+srv://...",
+  database_name="mydb",
+  collection_name="docs",
+)
+
+print(tool.run(query="how to create vector index"))
+```
+
+## Index creation helpers
+
+Use `create_vector_search_index(...)` to provision an Atlas Vector Search index with the correct dimensions and similarity.
+
+## Common issues
+
+- Authentication failures: ensure your Atlas IP Access List allows your runner and the connection string includes credentials.
+- Index not found: create the vector index first; name must match `vector_index_name`.
+- Dimensions mismatch: align embedding model dimensions with `dimensions`.
+
+## More examples
+
+### Basic initialization
+
+```python Code
+from crewai_tools import MongoDBVectorSearchTool
+
+tool = MongoDBVectorSearchTool(
+    database_name="example_database",
+    collection_name="example_collection",
+    connection_string="<your_mongodb_connection_string>",
+)
+```
+
+### Custom query configuration
+
+```python Code
+from crewai_tools import MongoDBVectorSearchConfig, MongoDBVectorSearchTool
+
+query_config = MongoDBVectorSearchConfig(limit=10, oversampling_factor=2)
+tool = MongoDBVectorSearchTool(
+    database_name="example_database",
+    collection_name="example_collection",
+    connection_string="<your_mongodb_connection_string>",
+    query_config=query_config,
+    vector_index_name="my_vector_index",
+)
+
+rag_agent = Agent(
+    name="rag_agent",
+    role="You are a helpful assistant that can answer questions with the help of the MongoDBVectorSearchTool.",
+    goal="...",
+    backstory="...",
+    tools=[tool],
+)
+```
+
+### Preloading the database and creating the index
+
+```python Code
+import os
+from crewai_tools import MongoDBVectorSearchTool
+
+tool = MongoDBVectorSearchTool(
+    database_name="example_database",
+    collection_name="example_collection",
+    connection_string="<your_mongodb_connection_string>",
+)
+
+# Load text content from a local folder and add to MongoDB
+texts = []
+for fname in os.listdir("knowledge"):
+    path = os.path.join("knowledge", fname)
+    if os.path.isfile(path):
+        with open(path, "r", encoding="utf-8") as f:
+            texts.append(f.read())
+
+tool.add_texts(texts)
+
+# Create the Atlas Vector Search index (e.g., 3072 dims for text-embedding-3-large)
+tool.create_vector_search_index(dimensions=3072)
+```
+
+## Example
+
+```python Code
+from crewai import Agent, Task, Crew
+from crewai_tools import MongoDBVectorSearchTool
+
+tool = MongoDBVectorSearchTool(
+    connection_string="mongodb+srv://...",
+    database_name="mydb",
+    collection_name="docs",
+)
+
+agent = Agent(
+    role="RAG Agent",
+    goal="Answer using MongoDB vector search",
+    backstory="Knowledge retrieval specialist",
+    tools=[tool],
+    verbose=True,
+)
+
+task = Task(
+    description="Find relevant content for 'indexing guidance'",
+    expected_output="A concise answer citing the most relevant matches",
+    agent=agent,
+)
+
+crew = Crew(
+    agents=[agent], 
+    tasks=[task],
+    verbose=True,
+)
+
+result = crew.kickoff()
+```
+
+
diff --git a/docs/pt-BR/tools/database-data/singlestoresearchtool.mdx b/docs/pt-BR/tools/database-data/singlestoresearchtool.mdx
new file mode 100644
index 000000000..8275c12f9
--- /dev/null
+++ b/docs/pt-BR/tools/database-data/singlestoresearchtool.mdx
@@ -0,0 +1,62 @@
+---
+title: SingleStore Search Tool
+description: The `SingleStoreSearchTool` safely executes SELECT/SHOW queries on SingleStore with pooling.
+icon: circle
+mode: "wide"
+---
+
+# `SingleStoreSearchTool`
+
+## Description
+
+Execute read‑only queries (`SELECT`/`SHOW`) against SingleStore with connection pooling and input validation.
+
+## Installation
+
+```shell
+uv add crewai-tools[singlestore]
+```
+
+## Environment Variables
+
+Variables like `SINGLESTOREDB_HOST`, `SINGLESTOREDB_USER`, `SINGLESTOREDB_PASSWORD`, etc., can be used, or `SINGLESTOREDB_URL` as a single DSN.
+
+Generate the API key from the SingleStore dashboard, [docs here](https://docs.singlestore.com/cloud/reference/management-api/#generate-an-api-key).
+
+## Example
+
+```python Code
+from crewai import Agent, Task, Crew
+from crewai_tools import SingleStoreSearchTool
+
+tool = SingleStoreSearchTool(
+    tables=["products"], 
+    host="host", 
+    user="user", 
+    password="pass", 
+    database="db",
+)
+
+agent = Agent(
+    role="Analyst", 
+    goal="Query SingleStore", 
+    tools=[tool], 
+    verbose=True,
+)
+
+task = Task(
+    description="List 5 products", 
+    expected_output="5 rows as JSON/text", 
+    agent=agent,
+)
+
+crew = Crew(
+    agents=[agent], 
+    tasks=[task],
+    verbose=True,
+)
+
+result = crew.kickoff()
+```
+
+
diff --git a/docs/pt-BR/tools/file-document/ocrtool.mdx b/docs/pt-BR/tools/file-document/ocrtool.mdx
new file mode 100644
index 000000000..162ca7834
--- /dev/null
+++ b/docs/pt-BR/tools/file-document/ocrtool.mdx
@@ -0,0 +1,90 @@
+---
+title: OCR Tool
+description: The `OCRTool` extracts text from local images or image URLs using an LLM with vision.
+icon: image
+mode: "wide"
+---
+
+# `OCRTool`
+
+## Description
+
+Extract text from images (local path or URL). Uses a vision‑capable LLM via CrewAI’s LLM interface.
+
+## Installation
+
+No extra install beyond `crewai-tools`. Ensure your selected LLM supports vision.
+
+## Parameters
+
+### Run Parameters
+
+- `image_path_url` (str, required): Local image path or HTTP(S) URL.
+
+## Examples
+
+### Direct usage
+
+```python Code
+from crewai_tools import OCRTool
+
+print(OCRTool().run(image_path_url="/tmp/receipt.png"))
+```
+
+### With an agent
+
+```python Code
+from crewai import Agent, Task, Crew
+from crewai_tools import OCRTool
+
+ocr = OCRTool()
+
+agent = Agent(
+    role="OCR", 
+    goal="Extract text", 
+    tools=[ocr],
+)
+
+task = Task(
+    description="Extract text from https://example.com/invoice.jpg", 
+    expected_output="All detected text in plain text",
+    agent=agent,
+)
+
+crew = Crew(agents=[agent], tasks=[task])
+result = crew.kickoff()
+```
+
+## Notes
+
+- Ensure the selected LLM supports image inputs.
+- For large images, consider downscaling to reduce token usage.
+ - You can pass a specific LLM instance to the tool (e.g., `LLM(model="gpt-4o")`) if needed, matching the README guidance.
+
+## Example
+
+```python Code
+from crewai import Agent, Task, Crew
+from crewai_tools import OCRTool
+
+tool = OCRTool()
+
+agent = Agent(
+    role="OCR Specialist",
+    goal="Extract text from images",
+    backstory="Vision‑enabled analyst",
+    tools=[tool],
+    verbose=True,
+)
+
+task = Task(
+    description="Extract text from https://example.com/receipt.png",
+    expected_output="All detected text in plain text",
+    agent=agent,
+)
+
+crew = Crew(agents=[agent], tasks=[task])
+result = crew.kickoff()
+```
+
+
diff --git a/docs/pt-BR/tools/file-document/pdf-text-writing-tool.mdx b/docs/pt-BR/tools/file-document/pdf-text-writing-tool.mdx
new file mode 100644
index 000000000..3e387a7b2
--- /dev/null
+++ b/docs/pt-BR/tools/file-document/pdf-text-writing-tool.mdx
@@ -0,0 +1,77 @@
+---
+title: PDF Text Writing Tool
+description: The `PDFTextWritingTool` writes text to specific positions in a PDF, supporting custom fonts.
+icon: file-pdf
+mode: "wide"
+---
+
+# `PDFTextWritingTool`
+
+## Description
+
+Write text at precise coordinates on a PDF page, optionally embedding a custom TrueType font.
+
+## Parameters
+
+### Run Parameters
+
+- `pdf_path` (str, required): Path to the input PDF.
+- `text` (str, required): Text to add.
+- `position` (tuple[int, int], required): `(x, y)` coordinates.
+- `font_size` (int, default `12`)
+- `font_color` (str, default `"0 0 0 rg"`)
+- `font_name` (str, default `"F1"`)
+- `font_file` (str, optional): Path to `.ttf` file.
+- `page_number` (int, default `0`)
+
+## Example
+
+```python Code
+from crewai import Agent, Task, Crew
+from crewai_tools import PDFTextWritingTool
+
+tool = PDFTextWritingTool()
+
+agent = Agent(
+    role="PDF Editor",
+    goal="Annotate PDFs",
+    backstory="Documentation specialist",
+    tools=[tool],
+    verbose=True,
+)
+
+task = Task(
+    description="Write 'CONFIDENTIAL' at (72, 720) on page 1 of ./sample.pdf",
+    expected_output="Confirmation message",
+    agent=agent,
+)
+
+crew = Crew(
+    agents=[agent], 
+    tasks=[task],
+    verbose=True,
+)
+
+result = crew.kickoff()
+```
+
+### Direct usage
+
+```python Code
+from crewai_tools import PDFTextWritingTool
+
+PDFTextWritingTool().run(
+  pdf_path="./input.pdf",
+  text="CONFIDENTIAL",
+  position=(72, 720),
+  font_size=18,
+  page_number=0,
+)
+```
+
+## Tips
+
+- Coordinate origin is the bottom‑left corner.
+- If using a custom font (`font_file`), ensure it is a valid `.ttf`.
+
+
diff --git a/docs/pt-BR/tools/search-research/arxivpapertool.mdx b/docs/pt-BR/tools/search-research/arxivpapertool.mdx
new file mode 100644
index 000000000..f952ed348
--- /dev/null
+++ b/docs/pt-BR/tools/search-research/arxivpapertool.mdx
@@ -0,0 +1,113 @@
+---
+title: Arxiv Paper Tool
+description: The `ArxivPaperTool` searches arXiv for papers matching a query and optionally downloads PDFs.
+icon: box-archive
+mode: "wide"
+---
+
+# `ArxivPaperTool`
+
+## Description
+
+The `ArxivPaperTool` queries the arXiv API for academic papers and returns compact, readable results. It can also optionally download PDFs to disk.
+
+## Installation
+
+This tool has no special installation beyond `crewai-tools`.
+
+```shell
+uv add crewai-tools
+```
+
+No API key is required. This tool uses the public arXiv Atom API.
+
+## Steps to Get Started
+
+1. Initialize the tool.
+2. Provide a `search_query` (e.g., "transformer neural network").
+3. Optionally set `max_results` (1–100) and enable PDF downloads in the constructor.
+
+## Example
+
+```python Code
+from crewai import Agent, Task, Crew
+from crewai_tools import ArxivPaperTool
+
+tool = ArxivPaperTool(
+    download_pdfs=False,
+    save_dir="./arxiv_pdfs",
+    use_title_as_filename=True,
+)
+
+agent = Agent(
+    role="Researcher",
+    goal="Find relevant arXiv papers",
+    backstory="Expert at literature discovery",
+    tools=[tool],
+    verbose=True,
+)
+
+task = Task(
+    description="Search arXiv for 'transformer neural network' and list top 5 results.",
+    expected_output="A concise list of 5 relevant papers with titles, links, and summaries.",
+    agent=agent,
+)
+
+crew = Crew(agents=[agent], tasks=[task])
+result = crew.kickoff()
+```
+
+### Direct usage (without Agent)
+
+```python Code
+from crewai_tools import ArxivPaperTool
+
+tool = ArxivPaperTool(
+    download_pdfs=True, 
+    save_dir="./arxiv_pdfs",
+)
+print(tool.run(search_query="mixture of experts", max_results=3))
+```
+
+## Parameters
+
+### Initialization Parameters
+
+- `download_pdfs` (bool, default `False`): Whether to download PDFs.
+- `save_dir` (str, default `./arxiv_pdfs`): Directory to save PDFs.
+- `use_title_as_filename` (bool, default `False`): Use paper titles for filenames.
+
+### Run Parameters
+
+- `search_query` (str, required): The arXiv search query.
+- `max_results` (int, default `5`, range 1–100): Number of results.
+
+## Output format
+
+The tool returns a human‑readable list of papers with:
+- Title
+- Link (abs page)
+- Snippet/summary (truncated)
+
+When `download_pdfs=True`, PDFs are saved to disk and the summary mentions saved files.
+
+## Usage Notes
+
+- The tool returns formatted text with key metadata and links.
+- When `download_pdfs=True`, PDFs will be stored in `save_dir`.
+
+## Troubleshooting
+
+- If you receive a network timeout, re‑try or reduce `max_results`.
+- Invalid XML errors indicate an arXiv response parse issue; try a simpler query.
+- File system errors (e.g., permission denied) may occur when saving PDFs; ensure `save_dir` is writable.
+
+## Related links
+
+- arXiv API docs: https://info.arxiv.org/help/api/index.html
+
+## Error Handling
+
+- Network issues, invalid XML, and OS errors are handled with informative messages.
+
+
diff --git a/docs/pt-BR/tools/search-research/databricks-query-tool.mdx b/docs/pt-BR/tools/search-research/databricks-query-tool.mdx
new file mode 100644
index 000000000..709ba383e
--- /dev/null
+++ b/docs/pt-BR/tools/search-research/databricks-query-tool.mdx
@@ -0,0 +1,81 @@
+---
+title: Databricks SQL Query Tool
+description: The `DatabricksQueryTool` executes SQL queries against Databricks workspace tables.
+icon: trowel-bricks
+mode: "wide"
+---
+
+# `DatabricksQueryTool`
+
+## Description
+
+Run SQL against Databricks workspace tables with either CLI profile or direct host/token authentication.
+
+## Installation
+
+```shell
+uv add crewai-tools[databricks-sdk]
+```
+
+## Environment Variables
+
+- `DATABRICKS_CONFIG_PROFILE` or (`DATABRICKS_HOST` + `DATABRICKS_TOKEN`)
+
+Create a personal access token and find host details in the Databricks workspace under User Settings → Developer. 
+Docs: https://docs.databricks.com/en/dev-tools/auth/pat.html
+
+## Example
+
+```python Code
+from crewai import Agent, Task, Crew
+from crewai_tools import DatabricksQueryTool
+
+tool = DatabricksQueryTool(
+    default_catalog="main", 
+    default_schema="default",
+)
+
+agent = Agent(
+    role="Data Analyst",
+    goal="Query Databricks",
+    tools=[tool],
+    verbose=True,
+)
+
+task = Task(
+    description="SELECT * FROM my_table LIMIT 10",
+    expected_output="10 rows", 
+    agent=agent,
+)
+
+crew = Crew(
+    agents=[agent], 
+    tasks=[task],
+    verbose=True,
+)
+result = crew.kickoff()
+
+print(result)
+```
+
+## Parameters
+
+- `query` (required): SQL query to execute
+- `catalog` (optional): Override default catalog
+- `db_schema` (optional): Override default schema
+- `warehouse_id` (optional): Override default SQL warehouse
+- `row_limit` (optional): Maximum rows to return (default: 1000)
+
+## Defaults on initialization
+
+- `default_catalog`
+- `default_schema`
+- `default_warehouse_id`
+
+### Error handling & tips
+
+- Authentication errors: verify `DATABRICKS_HOST` begins with `https://` and token is valid.
+- Permissions: ensure your SQL warehouse and schema are accessible by your token.
+- Limits: long‑running queries should be avoided in agent loops; add filters/limits.
+
+
diff --git a/docs/pt-BR/tools/search-research/serpapi-googlesearchtool.mdx b/docs/pt-BR/tools/search-research/serpapi-googlesearchtool.mdx
new file mode 100644
index 000000000..bf3e551e2
--- /dev/null
+++ b/docs/pt-BR/tools/search-research/serpapi-googlesearchtool.mdx
@@ -0,0 +1,66 @@
+---
+title: SerpApi Google Search Tool
+description: The `SerpApiGoogleSearchTool` performs Google searches using the SerpApi service.
+icon: google
+mode: "wide"
+---
+
+# `SerpApiGoogleSearchTool`
+
+## Description
+
+Use the `SerpApiGoogleSearchTool` to run Google searches with SerpApi and retrieve structured results. Requires a SerpApi API key.
+
+## Installation
+
+```shell
+uv add crewai-tools[serpapi]
+```
+
+## Environment Variables
+
+- `SERPAPI_API_KEY` (required): API key for SerpApi. Create one at https://serpapi.com/ (free tier available).
+
+## Example
+
+```python Code
+from crewai import Agent, Task, Crew
+from crewai_tools import SerpApiGoogleSearchTool
+
+tool = SerpApiGoogleSearchTool()
+
+agent = Agent(
+    role="Researcher",
+    goal="Answer questions using Google search",
+    backstory="Search specialist",
+    tools=[tool],
+    verbose=True,
+)
+
+task = Task(
+    description="Search for the latest CrewAI releases",
+    expected_output="A concise list of relevant results with titles and links",
+    agent=agent,
+)
+
+crew = Crew(agents=[agent], tasks=[task])
+result = crew.kickoff()
+```
+
+## Notes
+
+- Set `SERPAPI_API_KEY` in the environment. Create a key at https://serpapi.com/
+- See also Google Shopping via SerpApi: `/en/tools/search-research/serpapi-googleshoppingtool`
+
+## Parameters
+
+### Run Parameters
+
+- `search_query` (str, required): The Google query.
+- `location` (str, optional): Geographic location parameter.
+
+## Notes
+
+- This tool wraps SerpApi and returns structured search results.
+
+
diff --git a/docs/pt-BR/tools/search-research/serpapi-googleshoppingtool.mdx b/docs/pt-BR/tools/search-research/serpapi-googleshoppingtool.mdx
new file mode 100644
index 000000000..13138b6f4
--- /dev/null
+++ b/docs/pt-BR/tools/search-research/serpapi-googleshoppingtool.mdx
@@ -0,0 +1,62 @@
+---
+title: SerpApi Google Shopping Tool
+description: The `SerpApiGoogleShoppingTool` searches Google Shopping results using SerpApi.
+icon: cart-shopping
+mode: "wide"
+---
+
+# `SerpApiGoogleShoppingTool`
+
+## Description
+
+Leverage `SerpApiGoogleShoppingTool` to query Google Shopping via SerpApi and retrieve product-oriented results.
+
+## Installation
+
+```shell
+uv add crewai-tools[serpapi]
+```
+
+## Environment Variables
+
+- `SERPAPI_API_KEY` (required): API key for SerpApi. Create one at https://serpapi.com/ (free tier available).
+
+## Example
+
+```python Code
+from crewai import Agent, Task, Crew
+from crewai_tools import SerpApiGoogleShoppingTool
+
+tool = SerpApiGoogleShoppingTool()
+
+agent = Agent(
+    role="Shopping Researcher",
+    goal="Find relevant products",
+    backstory="Expert in product search",
+    tools=[tool],
+    verbose=True,
+)
+
+task = Task(
+    description="Search Google Shopping for 'wireless noise-canceling headphones'",
+    expected_output="Top relevant products with titles and links",
+    agent=agent,
+)
+
+crew = Crew(agents=[agent], tasks=[task])
+result = crew.kickoff()
+```
+
+## Notes
+
+- Set `SERPAPI_API_KEY` in the environment. Create a key at https://serpapi.com/
+- See also Google Web Search via SerpApi: `/en/tools/search-research/serpapi-googlesearchtool`
+
+## Parameters
+
+### Run Parameters
+
+- `search_query` (str, required): Product search query.
+- `location` (str, optional): Geographic location parameter.
+
+
diff --git a/docs/pt-BR/tools/search-research/tavilyextractortool.mdx b/docs/pt-BR/tools/search-research/tavilyextractortool.mdx
new file mode 100644
index 000000000..4b1d4b091
--- /dev/null
+++ b/docs/pt-BR/tools/search-research/tavilyextractortool.mdx
@@ -0,0 +1,140 @@
+---
+title: "Tavily Extractor Tool"
+description: "Extract structured content from web pages using the Tavily API"
+icon: square-poll-horizontal
+mode: "wide"
+---
+
+The `TavilyExtractorTool` allows CrewAI agents to extract structured content from web pages using the Tavily API. It can process single URLs or lists of URLs and provides options for controlling the extraction depth and including images.
+
+## Installation
+
+To use the `TavilyExtractorTool`, you need to install the `tavily-python` library:
+
+```shell
+pip install 'crewai[tools]' tavily-python
+```
+
+You also need to set your Tavily API key as an environment variable:
+
+```bash
+export TAVILY_API_KEY='your-tavily-api-key'
+```
+
+## Example Usage
+
+Here's how to initialize and use the `TavilyExtractorTool` within a CrewAI agent:
+
+```python
+import os
+from crewai import Agent, Task, Crew
+from crewai_tools import TavilyExtractorTool
+
+# Ensure TAVILY_API_KEY is set in your environment
+# os.environ["TAVILY_API_KEY"] = "YOUR_API_KEY"
+
+# Initialize the tool
+tavily_tool = TavilyExtractorTool()
+
+# Create an agent that uses the tool
+extractor_agent = Agent(
+    role='Web Content Extractor',
+    goal='Extract key information from specified web pages',
+    backstory='You are an expert at extracting relevant content from websites using the Tavily API.',
+    tools=[tavily_tool],
+    verbose=True
+)
+
+# Define a task for the agent
+extract_task = Task(
+    description='Extract the main content from the URL https://example.com using basic extraction depth.',
+    expected_output='A JSON string containing the extracted content from the URL.',
+    agent=extractor_agent
+)
+
+# Create and run the crew
+crew = Crew(
+    agents=[extractor_agent],
+    tasks=[extract_task],
+    verbose=2
+)
+
+result = crew.kickoff()
+print(result)
+```
+
+## Configuration Options
+
+The `TavilyExtractorTool` accepts the following arguments:
+
+- `urls` (Union[List[str], str]): **Required**. A single URL string or a list of URL strings to extract data from.
+- `include_images` (Optional[bool]): Whether to include images in the extraction results. Defaults to `False`.
+- `extract_depth` (Literal["basic", "advanced"]): The depth of extraction. Use `"basic"` for faster, surface-level extraction or `"advanced"` for more comprehensive extraction. Defaults to `"basic"`.
+- `timeout` (int): The maximum time in seconds to wait for the extraction request to complete. Defaults to `60`.
+
+## Advanced Usage
+
+### Multiple URLs with Advanced Extraction
+
+```python
+# Example with multiple URLs and advanced extraction
+multi_extract_task = Task(
+    description='Extract content from https://example.com and https://anotherexample.org using advanced extraction.',
+    expected_output='A JSON string containing the extracted content from both URLs.',
+    agent=extractor_agent
+)
+
+# Configure the tool with custom parameters
+custom_extractor = TavilyExtractorTool(
+    extract_depth='advanced',
+    include_images=True,
+    timeout=120
+)
+
+agent_with_custom_tool = Agent(
+    role="Advanced Content Extractor",
+    goal="Extract comprehensive content with images",
+    tools=[custom_extractor]
+)
+```
+
+### Tool Parameters
+
+You can customize the tool's behavior by setting parameters during initialization:
+
+```python
+# Initialize with custom configuration
+extractor_tool = TavilyExtractorTool(
+    extract_depth='advanced',  # More comprehensive extraction
+    include_images=True,       # Include image results
+    timeout=90                 # Custom timeout
+)
+```
+
+## Features
+
+- **Single or Multiple URLs**: Extract content from one URL or process multiple URLs in a single request
+- **Configurable Depth**: Choose between basic (fast) and advanced (comprehensive) extraction modes
+- **Image Support**: Optionally include images in the extraction results
+- **Structured Output**: Returns well-formatted JSON containing the extracted content
+- **Error Handling**: Robust handling of network timeouts and extraction errors
+
+## Response Format
+
+The tool returns a JSON string representing the structured data extracted from the provided URL(s). The exact structure depends on the content of the pages and the `extract_depth` used.
+
+Common response elements include:
+- **Title**: The page title
+- **Content**: Main text content of the page
+- **Images**: Image URLs and metadata (when `include_images=True`)
+- **Metadata**: Additional page information like author, description, etc.
+
+## Use Cases
+
+- **Content Analysis**: Extract and analyze content from competitor websites
+- **Research**: Gather structured data from multiple sources for analysis
+- **Content Migration**: Extract content from existing websites for migration
+- **Monitoring**: Regular extraction of content for change detection
+- **Data Collection**: Systematic extraction of information from web sources
+
+Refer to the [Tavily API documentation](https://docs.tavily.com/docs/tavily-api/python-sdk#extract) for detailed information about the response structure and available options.
\ No newline at end of file
diff --git a/docs/pt-BR/tools/search-research/tavilysearchtool.mdx b/docs/pt-BR/tools/search-research/tavilysearchtool.mdx
new file mode 100644
index 000000000..0d3af2ba3
--- /dev/null
+++ b/docs/pt-BR/tools/search-research/tavilysearchtool.mdx
@@ -0,0 +1,125 @@
+---
+title: "Tavily Search Tool"
+description: "Perform comprehensive web searches using the Tavily Search API"
+icon: "magnifying-glass"
+mode: "wide"
+---
+
+The `TavilySearchTool` provides an interface to the Tavily Search API, enabling CrewAI agents to perform comprehensive web searches. It allows for specifying search depth, topics, time ranges, included/excluded domains, and whether to include direct answers, raw content, or images in the results.
+
+## Installation
+
+To use the `TavilySearchTool`, you need to install the `tavily-python` library:
+
+```shell
+pip install 'crewai[tools]' tavily-python
+```
+
+## Environment Variables
+
+Ensure your Tavily API key is set as an environment variable:
+
+```bash
+export TAVILY_API_KEY='your_tavily_api_key'
+```
+
+Get an API key at https://app.tavily.com/ (sign up, then create a key).
+
+## Example Usage
+
+Here's how to initialize and use the `TavilySearchTool` within a CrewAI agent:
+
+```python
+import os
+from crewai import Agent, Task, Crew
+from crewai_tools import TavilySearchTool
+
+# Ensure the TAVILY_API_KEY environment variable is set
+# os.environ["TAVILY_API_KEY"] = "YOUR_TAVILY_API_KEY"
+
+# Initialize the tool
+tavily_tool = TavilySearchTool()
+
+# Create an agent that uses the tool
+researcher = Agent(
+    role='Market Researcher',
+    goal='Find information about the latest AI trends',
+    backstory='An expert market researcher specializing in technology.',
+    tools=[tavily_tool],
+    verbose=True
+)
+
+# Create a task for the agent
+research_task = Task(
+    description='Search for the top 3 AI trends in 2024.',
+    expected_output='A JSON report summarizing the top 3 AI trends found.',
+    agent=researcher
+)
+
+# Form the crew and kick it off
+crew = Crew(
+    agents=[researcher],
+    tasks=[research_task],
+    verbose=2
+)
+
+result = crew.kickoff()
+print(result)
+```
+
+## Configuration Options
+
+The `TavilySearchTool` accepts the following arguments during initialization or when calling the `run` method:
+
+- `query` (str): **Required**. The search query string.
+- `search_depth` (Literal["basic", "advanced"], optional): The depth of the search. Defaults to `"basic"`.
+- `topic` (Literal["general", "news", "finance"], optional): The topic to focus the search on. Defaults to `"general"`.
+- `time_range` (Literal["day", "week", "month", "year"], optional): The time range for the search. Defaults to `None`.
+- `days` (int, optional): The number of days to search back. Relevant if `time_range` is not set. Defaults to `7`.
+- `max_results` (int, optional): The maximum number of search results to return. Defaults to `5`.
+- `include_domains` (Sequence[str], optional): A list of domains to prioritize in the search. Defaults to `None`.
+- `exclude_domains` (Sequence[str], optional): A list of domains to exclude from the search. Defaults to `None`.
+- `include_answer` (Union[bool, Literal["basic", "advanced"]], optional): Whether to include a direct answer synthesized from the search results. Defaults to `False`.
+- `include_raw_content` (bool, optional): Whether to include the raw HTML content of the searched pages. Defaults to `False`.
+- `include_images` (bool, optional): Whether to include image results. Defaults to `False`.
+- `timeout` (int, optional): The request timeout in seconds. Defaults to `60`.
+
+## Advanced Usage
+
+You can configure the tool with custom parameters:
+
+```python
+# Example: Initialize with specific parameters
+custom_tavily_tool = TavilySearchTool(
+    search_depth='advanced',
+    max_results=10,
+    include_answer=True
+)
+
+# The agent will use these defaults
+agent_with_custom_tool = Agent(
+    role="Advanced Researcher",
+    goal="Conduct detailed research with comprehensive results",
+    tools=[custom_tavily_tool]
+)
+```
+
+## Features
+
+- **Comprehensive Search**: Access to Tavily's powerful search index
+- **Configurable Depth**: Choose between basic and advanced search modes
+- **Topic Filtering**: Focus searches on general, news, or finance topics
+- **Time Range Control**: Limit results to specific time periods
+- **Domain Control**: Include or exclude specific domains
+- **Direct Answers**: Get synthesized answers from search results
+- **Content Filtering**: Prevent context window issues with automatic content truncation
+
+## Response Format
+
+The tool returns search results as a JSON string containing:
+- Search results with titles, URLs, and content snippets
+- Optional direct answers to queries
+- Optional image results
+- Optional raw HTML content (when enabled)
+
+Content for each result is automatically truncated to prevent context window issues while maintaining the most relevant information.
\ No newline at end of file
diff --git a/docs/pt-BR/tools/tool-integrations/overview.mdx b/docs/pt-BR/tools/tool-integrations/overview.mdx
new file mode 100644
index 000000000..6f59ca471
--- /dev/null
+++ b/docs/pt-BR/tools/tool-integrations/overview.mdx
@@ -0,0 +1,31 @@
+---
+title: Overview
+description: Integrations for deploying and automating crews with external platforms
+icon: face-smile
+mode: "wide"
+---
+
+## Available Integrations
+
+<CardGroup cols={2}>
+  <Card
+    title="Bedrock Invoke Agent Tool"
+    icon="cloud"
+    href="/en/tools/tool-integrations/bedrockinvokeagenttool"
+    color="#0891B2"
+  >
+    Invoke Amazon Bedrock Agents from CrewAI to orchestrate actions across AWS services.
+  </Card>
+
+  <Card
+    title="CrewAI Automation Tool"
+    icon="bolt"
+    href="/en/tools/tool-integrations/crewaiautomationtool"
+    color="#7C3AED"
+  >
+    Automate deployment and operations by integrating CrewAI with external platforms and workflows.
+  </Card>
+</CardGroup>
+
+Use these integrations to connect CrewAI with your infrastructure and workflows.
+
diff --git a/docs/pt-BR/tools/web-scraping/brightdata-tools.mdx b/docs/pt-BR/tools/web-scraping/brightdata-tools.mdx
new file mode 100644
index 000000000..36da3c461
--- /dev/null
+++ b/docs/pt-BR/tools/web-scraping/brightdata-tools.mdx
@@ -0,0 +1,112 @@
+---
+title: Bright Data Tools
+description: Bright Data integrations for SERP search, Web Unlocker scraping, and Dataset API.
+icon: spider
+mode: "wide"
+---
+
+# Bright Data Tools
+
+This set of tools integrates Bright Data services for web extraction.
+
+## Installation
+
+```shell
+uv add crewai-tools requests aiohttp
+```
+
+## Environment Variables
+
+- `BRIGHT_DATA_API_KEY` (required)
+- `BRIGHT_DATA_ZONE` (for SERP/Web Unlocker)
+
+Create credentials at https://brightdata.com/ (sign up, then create an API token and zone). 
+See their docs: https://developers.brightdata.com/
+
+## Included Tools
+
+- `BrightDataSearchTool`: SERP search (Google/Bing/Yandex) with geo/language/device options.
+- `BrightDataWebUnlockerTool`: Scrape pages with anti-bot bypass and rendering.
+- `BrightDataDatasetTool`: Run Dataset API jobs and fetch results.
+
+## Examples
+
+### SERP Search
+
+```python Code
+from crewai_tools import BrightDataSearchTool
+
+tool = BrightDataSearchTool(
+    query="CrewAI", 
+    country="us",
+)
+
+print(tool.run())
+```
+
+### Web Unlocker
+
+```python Code
+from crewai_tools import BrightDataWebUnlockerTool
+
+tool = BrightDataWebUnlockerTool(
+    url="https://example.com", 
+    format="markdown",
+)
+
+print(tool.run(url="https://example.com"))
+```
+
+### Dataset API
+
+```python Code
+from crewai_tools import BrightDataDatasetTool
+
+tool = BrightDataDatasetTool(
+    dataset_type="ecommerce", 
+    url="https://example.com/product",
+)
+
+print(tool.run())
+```
+
+## Troubleshooting
+
+- 401/403: verify `BRIGHT_DATA_API_KEY` and `BRIGHT_DATA_ZONE`.
+- Empty/blocked content: enable rendering or try a different zone.
+
+## Example
+
+```python Code
+from crewai import Agent, Task, Crew
+from crewai_tools import BrightDataSearchTool
+
+tool = BrightDataSearchTool(
+    query="CrewAI", 
+    country="us",
+)
+
+agent = Agent(
+    role="Web Researcher",
+    goal="Search with Bright Data",
+    backstory="Finds reliable results",
+    tools=[tool],
+    verbose=True,
+)
+
+task = Task(
+    description="Search for CrewAI and summarize top results",
+    expected_output="Short summary with links",
+    agent=agent,
+)
+
+crew = Crew(
+    agents=[agent], 
+    tasks=[task],
+    verbose=True,
+)
+
+result = crew.kickoff()
+```
+
+
diff --git a/docs/pt-BR/tools/web-scraping/serperscrapewebsitetool.mdx b/docs/pt-BR/tools/web-scraping/serperscrapewebsitetool.mdx
new file mode 100644
index 000000000..105492388
--- /dev/null
+++ b/docs/pt-BR/tools/web-scraping/serperscrapewebsitetool.mdx
@@ -0,0 +1,101 @@
+---
+title: Serper Scrape Website
+description: The `SerperScrapeWebsiteTool` is designed to scrape websites and extract clean, readable content using Serper's scraping API.
+icon: globe
+mode: "wide"
+---
+
+# `SerperScrapeWebsiteTool`
+
+## Description
+
+This tool is designed to scrape website content and extract clean, readable text from any website URL. It utilizes the [serper.dev](https://serper.dev) scraping API to fetch and process web pages, optionally including markdown formatting for better structure and readability.
+
+## Installation
+
+To effectively use the `SerperScrapeWebsiteTool`, follow these steps:
+
+1. **Package Installation**: Confirm that the `crewai[tools]` package is installed in your Python environment.
+2. **API Key Acquisition**: Acquire a `serper.dev` API key by registering for an account at `serper.dev`.
+3. **Environment Configuration**: Store your obtained API key in an environment variable named `SERPER_API_KEY` to facilitate its use by the tool.
+
+To incorporate this tool into your project, follow the installation instructions below:
+
+```shell
+pip install 'crewai[tools]'
+```
+
+## Example
+
+The following example demonstrates how to initialize the tool and scrape a website:
+
+```python Code
+from crewai_tools import SerperScrapeWebsiteTool
+
+# Initialize the tool for website scraping capabilities
+tool = SerperScrapeWebsiteTool()
+
+# Scrape a website with markdown formatting
+result = tool.run(url="https://example.com", include_markdown=True)
+```
+
+## Arguments
+
+The `SerperScrapeWebsiteTool` accepts the following arguments:
+
+- **url**: Required. The URL of the website to scrape.
+- **include_markdown**: Optional. Whether to include markdown formatting in the scraped content. Defaults to `True`.
+
+## Example with Parameters
+
+Here is an example demonstrating how to use the tool with different parameters:
+
+```python Code
+from crewai_tools import SerperScrapeWebsiteTool
+
+tool = SerperScrapeWebsiteTool()
+
+# Scrape with markdown formatting (default)
+markdown_result = tool.run(
+    url="https://docs.crewai.com",
+    include_markdown=True
+)
+
+# Scrape without markdown formatting for plain text
+plain_result = tool.run(
+    url="https://docs.crewai.com",
+    include_markdown=False
+)
+
+print("Markdown formatted content:")
+print(markdown_result)
+
+print("\nPlain text content:")
+print(plain_result)
+```
+
+## Use Cases
+
+The `SerperScrapeWebsiteTool` is particularly useful for:
+
+- **Content Analysis**: Extract and analyze website content for research purposes
+- **Data Collection**: Gather structured information from web pages
+- **Documentation Processing**: Convert web-based documentation into readable formats
+- **Competitive Analysis**: Scrape competitor websites for market research
+- **Content Migration**: Extract content from existing websites for migration purposes
+
+## Error Handling
+
+The tool includes comprehensive error handling for:
+
+- **Network Issues**: Handles connection timeouts and network errors gracefully
+- **API Errors**: Provides detailed error messages for API-related issues
+- **Invalid URLs**: Validates and reports issues with malformed URLs
+- **Authentication**: Clear error messages for missing or invalid API keys
+
+## Security Considerations
+
+- Always store your `SERPER_API_KEY` in environment variables, never hardcode it in your source code
+- Be mindful of rate limits imposed by the Serper API
+- Respect robots.txt and website terms of service when scraping content
+- Consider implementing delays between requests for large-scale scraping operations
\ No newline at end of file
diff --git a/lib/crewai-tools/src/crewai_tools/tools/generate_crewai_automation_tool/README.md b/lib/crewai-tools/src/crewai_tools/tools/generate_crewai_automation_tool/README.md
index c70741ca4..4e5e8a580 100644
--- a/lib/crewai-tools/src/crewai_tools/tools/generate_crewai_automation_tool/README.md
+++ b/lib/crewai-tools/src/crewai_tools/tools/generate_crewai_automation_tool/README.md
@@ -6,7 +6,7 @@ The GenerateCrewaiAutomationTool integrates with CrewAI Studio API to generate c
 
 ## Environment Variables
 
-Set your CrewAI Personal Access Token (CrewAI Enterprise > Settings > Account > Personal Access Token):
+Set your CrewAI Personal Access Token (CrewAI AMP > Settings > Account > Personal Access Token):
 
 ```bash
 export CREWAI_PERSONAL_ACCESS_TOKEN="your_personal_access_token_here"
diff --git a/lib/crewai-tools/src/crewai_tools/tools/generate_crewai_automation_tool/generate_crewai_automation_tool.py b/lib/crewai-tools/src/crewai_tools/tools/generate_crewai_automation_tool/generate_crewai_automation_tool.py
index 05b47cce4..e575b129a 100644
--- a/lib/crewai-tools/src/crewai_tools/tools/generate_crewai_automation_tool/generate_crewai_automation_tool.py
+++ b/lib/crewai-tools/src/crewai_tools/tools/generate_crewai_automation_tool/generate_crewai_automation_tool.py
@@ -12,7 +12,7 @@ class GenerateCrewaiAutomationToolSchema(BaseModel):
     )
     organization_id: Optional[str] = Field(
         default=None,
-        description="The identifier for the CrewAI Enterprise organization. If not specified, a default organization will be used.",
+        description="The identifier for the CrewAI AMP organization. If not specified, a default organization will be used.",
     )
 
 
@@ -26,21 +26,21 @@ class GenerateCrewaiAutomationTool(BaseTool):
     args_schema: Type[BaseModel] = GenerateCrewaiAutomationToolSchema
     crewai_enterprise_url: str = Field(
         default_factory=lambda: os.getenv("CREWAI_PLUS_URL", "https://app.crewai.com"),
-        description="The base URL of CrewAI Enterprise. If not provided, it will be loaded from the environment variable CREWAI_PLUS_URL with default https://app.crewai.com.",
+        description="The base URL of CrewAI AMP. If not provided, it will be loaded from the environment variable CREWAI_PLUS_URL with default https://app.crewai.com.",
     )
     personal_access_token: Optional[str] = Field(
         default_factory=lambda: os.getenv("CREWAI_PERSONAL_ACCESS_TOKEN"),
-        description="The user's Personal Access Token to access CrewAI Enterprise API. If not provided, it will be loaded from the environment variable CREWAI_PERSONAL_ACCESS_TOKEN.",
+        description="The user's Personal Access Token to access CrewAI AMP API. If not provided, it will be loaded from the environment variable CREWAI_PERSONAL_ACCESS_TOKEN.",
     )
     env_vars: List[EnvVar] = [
         EnvVar(
             name="CREWAI_PERSONAL_ACCESS_TOKEN",
-            description="Personal Access Token for CrewAI Enterprise API",
+            description="Personal Access Token for CrewAI AMP API",
             required=True,
         ),
         EnvVar(
             name="CREWAI_PLUS_URL",
-            description="Base URL for CrewAI Enterprise API",
+            description="Base URL for CrewAI AMP API",
             required=False,
         ),
     ]
diff --git a/lib/crewai-tools/tool.specs.json b/lib/crewai-tools/tool.specs.json
index c9cb7a2cd..f7b71384a 100644
--- a/lib/crewai-tools/tool.specs.json
+++ b/lib/crewai-tools/tool.specs.json
@@ -3195,13 +3195,13 @@
       "env_vars": [
         {
           "default": null,
-          "description": "Personal Access Token for CrewAI Enterprise API",
+          "description": "Personal Access Token for CrewAI AMP API",
           "name": "CREWAI_PERSONAL_ACCESS_TOKEN",
           "required": true
         },
         {
           "default": null,
-          "description": "Base URL for CrewAI Enterprise API",
+          "description": "Base URL for CrewAI AMP API",
           "name": "CREWAI_PLUS_URL",
           "required": false
         }
@@ -3247,7 +3247,7 @@
         },
         "properties": {
           "crewai_enterprise_url": {
-            "description": "The base URL of CrewAI Enterprise. If not provided, it will be loaded from the environment variable CREWAI_PLUS_URL with default https://app.crewai.com.",
+            "description": "The base URL of CrewAI AMP. If not provided, it will be loaded from the environment variable CREWAI_PLUS_URL with default https://app.crewai.com.",
             "title": "Crewai Enterprise Url",
             "type": "string"
           },
@@ -3260,7 +3260,7 @@
                 "type": "null"
               }
             ],
-            "description": "The user's Personal Access Token to access CrewAI Enterprise API. If not provided, it will be loaded from the environment variable CREWAI_PERSONAL_ACCESS_TOKEN.",
+            "description": "The user's Personal Access Token to access CrewAI AMP API. If not provided, it will be loaded from the environment variable CREWAI_PERSONAL_ACCESS_TOKEN.",
             "title": "Personal Access Token"
           }
         },
@@ -3281,7 +3281,7 @@
               }
             ],
             "default": null,
-            "description": "The identifier for the CrewAI Enterprise organization. If not specified, a default organization will be used.",
+            "description": "The identifier for the CrewAI AMP organization. If not specified, a default organization will be used.",
             "title": "Organization Id"
           },
           "prompt": {
diff --git a/lib/crewai/README.md b/lib/crewai/README.md
index 3d3eb3324..f821ac6aa 100644
--- a/lib/crewai/README.md
+++ b/lib/crewai/README.md
@@ -62,9 +62,9 @@
 With over 100,000 developers certified through our community courses at [learn.crewai.com](https://learn.crewai.com), CrewAI is rapidly becoming the
 standard for enterprise-ready AI automation.
 
-# CrewAI Enterprise Suite
+# CrewAI AMP Suite
 
-CrewAI Enterprise Suite is a comprehensive bundle tailored for organizations that require secure, scalable, and easy-to-manage agent-driven automation.
+CrewAI AMP Suite is a comprehensive bundle tailored for organizations that require secure, scalable, and easy-to-manage agent-driven automation.
 
 You can try one part of the suite the [Crew Control Plane for free](https://app.crewai.com)
 
@@ -76,9 +76,9 @@ You can try one part of the suite the [Crew Control Plane for free](https://app.
 - **Advanced Security**: Built-in robust security and compliance measures ensuring safe deployment and management.
 - **Actionable Insights**: Real-time analytics and reporting to optimize performance and decision-making.
 - **24/7 Support**: Dedicated enterprise support to ensure uninterrupted operation and quick resolution of issues.
-- **On-premise and Cloud Deployment Options**: Deploy CrewAI Enterprise on-premise or in the cloud, depending on your security and compliance requirements.
+- **On-premise and Cloud Deployment Options**: Deploy CrewAI AMP on-premise or in the cloud, depending on your security and compliance requirements.
 
-CrewAI Enterprise is designed for enterprises seeking a powerful, reliable solution to transform complex business processes into efficient,
+CrewAI AMP is designed for enterprises seeking a powerful, reliable solution to transform complex business processes into efficient,
 intelligent automations.
 
 ## Table of contents
@@ -674,9 +674,9 @@ CrewAI is released under the [MIT License](https://github.com/crewAIInc/crewAI/b
 
 ### Enterprise Features
 
-- [What additional features does CrewAI Enterprise offer?](#q-what-additional-features-does-crewai-enterprise-offer)
-- [Is CrewAI Enterprise available for cloud and on-premise deployments?](#q-is-crewai-enterprise-available-for-cloud-and-on-premise-deployments)
-- [Can I try CrewAI Enterprise for free?](#q-can-i-try-crewai-enterprise-for-free)
+- [What additional features does CrewAI AMP offer?](#q-what-additional-features-does-crewai-enterprise-offer)
+- [Is CrewAI AMP available for cloud and on-premise deployments?](#q-is-crewai-enterprise-available-for-cloud-and-on-premise-deployments)
+- [Can I try CrewAI AMP for free?](#q-can-i-try-crewai-enterprise-for-free)
 
 ### Q: What exactly is CrewAI?
 
@@ -732,17 +732,17 @@ A: Check out practical examples in the [CrewAI-examples repository](https://gith
 
 A: Contributions are warmly welcomed! Fork the repository, create your branch, implement your changes, and submit a pull request. See the Contribution section of the README for detailed guidelines.
 
-### Q: What additional features does CrewAI Enterprise offer?
+### Q: What additional features does CrewAI AMP offer?
 
-A: CrewAI Enterprise provides advanced features such as a unified control plane, real-time observability, secure integrations, advanced security, actionable insights, and dedicated 24/7 enterprise support.
+A: CrewAI AMP provides advanced features such as a unified control plane, real-time observability, secure integrations, advanced security, actionable insights, and dedicated 24/7 enterprise support.
 
-### Q: Is CrewAI Enterprise available for cloud and on-premise deployments?
+### Q: Is CrewAI AMP available for cloud and on-premise deployments?
 
-A: Yes, CrewAI Enterprise supports both cloud-based and on-premise deployment options, allowing enterprises to meet their specific security and compliance requirements.
+A: Yes, CrewAI AMP supports both cloud-based and on-premise deployment options, allowing enterprises to meet their specific security and compliance requirements.
 
-### Q: Can I try CrewAI Enterprise for free?
+### Q: Can I try CrewAI AMP for free?
 
-A: Yes, you can explore part of the CrewAI Enterprise Suite by accessing the [Crew Control Plane](https://app.crewai.com) for free.
+A: Yes, you can explore part of the CrewAI AMP Suite by accessing the [Crew Control Plane](https://app.crewai.com) for free.
 
 ### Q: Does CrewAI support fine-tuning or training custom models?
 
@@ -762,7 +762,7 @@ A: CrewAI is highly scalable, supporting simple automations and large-scale ente
 
 ### Q: Does CrewAI offer debugging and monitoring tools?
 
-A: Yes, CrewAI Enterprise includes advanced debugging, tracing, and real-time observability features, simplifying the management and troubleshooting of your automations.
+A: Yes, CrewAI AMP includes advanced debugging, tracing, and real-time observability features, simplifying the management and troubleshooting of your automations.
 
 ### Q: What programming languages does CrewAI support?
 
diff --git a/lib/crewai/src/crewai/agents/agent_builder/base_agent.py b/lib/crewai/src/crewai/agents/agent_builder/base_agent.py
index 5705313eb..c6a03c935 100644
--- a/lib/crewai/src/crewai/agents/agent_builder/base_agent.py
+++ b/lib/crewai/src/crewai/agents/agent_builder/base_agent.py
@@ -78,8 +78,8 @@ class BaseAgent(ABC, BaseModel):
         knowledge_sources: Knowledge sources for the agent.
         knowledge_storage: Custom knowledge storage for the agent.
         security_config: Security configuration for the agent, including fingerprinting.
-        apps: List of enterprise applications that the agent can access through CrewAI Enterprise Tools.
-        actions: List of actions that the agent can access through CrewAI Enterprise Tools.
+        apps: List of enterprise applications that the agent can access through CrewAI AMP Tools.
+        actions: List of actions that the agent can access through CrewAI AMP Tools.
 
 
     Methods:
diff --git a/lib/crewai/src/crewai/cli/authentication/main.py b/lib/crewai/src/crewai/cli/authentication/main.py
index 8eab80c9b..a5d7f2020 100644
--- a/lib/crewai/src/crewai/cli/authentication/main.py
+++ b/lib/crewai/src/crewai/cli/authentication/main.py
@@ -63,7 +63,7 @@ class AuthenticationCommand:
 
     def login(self) -> None:
         """Sign up to CrewAI+"""
-        console.print("Signing in to CrewAI Enterprise...\n", style="bold blue")
+        console.print("Signing in to CrewAI AMP...\n", style="bold blue")
 
         device_code_data = self._get_device_code()
         self._display_auth_instructions(device_code_data)
@@ -121,7 +121,7 @@ class AuthenticationCommand:
                 self._login_to_tool_repository()
 
                 console.print(
-                    "\n[bold green]Welcome to CrewAI Enterprise![/bold green]\n"
+                    "\n[bold green]Welcome to CrewAI AMP![/bold green]\n"
                 )
                 return
 
diff --git a/lib/crewai/src/crewai/cli/cli.py b/lib/crewai/src/crewai/cli/cli.py
index 991082de0..a202a5e73 100644
--- a/lib/crewai/src/crewai/cli/cli.py
+++ b/lib/crewai/src/crewai/cli/cli.py
@@ -271,7 +271,7 @@ def update():
 
 @crewai.command()
 def login():
-    """Sign Up/Login to CrewAI Enterprise."""
+    """Sign Up/Login to CrewAI AMP."""
     Settings().clear_user_settings()
     AuthenticationCommand().login()
 
@@ -440,7 +440,7 @@ def enterprise():
 @enterprise.command("configure")
 @click.argument("enterprise_url")
 def enterprise_configure(enterprise_url: str):
-    """Configure CrewAI Enterprise OAuth2 settings from the provided Enterprise URL."""
+    """Configure CrewAI AMP OAuth2 settings from the provided Enterprise URL."""
     enterprise_command = EnterpriseConfigureCommand()
     enterprise_command.configure(enterprise_url)
 
diff --git a/lib/crewai/src/crewai/cli/config.py b/lib/crewai/src/crewai/cli/config.py
index e4ed1fad5..15cda9488 100644
--- a/lib/crewai/src/crewai/cli/config.py
+++ b/lib/crewai/src/crewai/cli/config.py
@@ -99,7 +99,7 @@ HIDDEN_SETTINGS_KEYS = [
 class Settings(BaseModel):
     enterprise_base_url: str | None = Field(
         default=DEFAULT_CLI_SETTINGS["enterprise_base_url"],
-        description="Base URL of the CrewAI Enterprise instance",
+        description="Base URL of the CrewAI AMP instance",
     )
     tool_repository_username: str | None = Field(
         None, description="Username for interacting with the Tool Repository"
diff --git a/lib/crewai/src/crewai/cli/enterprise/main.py b/lib/crewai/src/crewai/cli/enterprise/main.py
index 0a867a2f7..4c25fb1c7 100644
--- a/lib/crewai/src/crewai/cli/enterprise/main.py
+++ b/lib/crewai/src/crewai/cli/enterprise/main.py
@@ -25,7 +25,7 @@ class EnterpriseConfigureCommand(BaseCommand):
             self._update_oauth_settings(enterprise_url, oauth_config)
 
             console.print(
-                f"✅ Successfully configured CrewAI Enterprise with OAuth2 settings from {enterprise_url}",
+                f"✅ Successfully configured CrewAI AMP with OAuth2 settings from {enterprise_url}",
                 style="bold green",
             )
 
diff --git a/lib/crewai/tests/cli/authentication/test_auth_main.py b/lib/crewai/tests/cli/authentication/test_auth_main.py
index fafbc7edd..d5d309ca9 100644
--- a/lib/crewai/tests/cli/authentication/test_auth_main.py
+++ b/lib/crewai/tests/cli/authentication/test_auth_main.py
@@ -53,7 +53,7 @@ class TestAuthenticationCommand:
         self.auth_command.login()
 
         mock_console_print.assert_called_once_with(
-            "Signing in to CrewAI Enterprise...\n", style="bold blue"
+            "Signing in to CrewAI AMP...\n", style="bold blue"
         )
         mock_get_device.assert_called_once()
         mock_display.assert_called_once_with(
@@ -298,7 +298,7 @@ class TestAuthenticationCommand:
             expected_calls = [
                 call("\nWaiting for authentication... ", style="bold blue", end=""),
                 call("Success!", style="bold green"),
-                call("\n[bold green]Welcome to CrewAI Enterprise![/bold green]\n"),
+                call("\n[bold green]Welcome to CrewAI AMP![/bold green]\n"),
             ]
             mock_console_print.assert_has_calls(expected_calls)