Follow up to #1803 to remove dynamic docs route. (#1818)

The base docs are going to be more stable and familiar for folks.
Dynamic route is currently in flux.

docs/modules/utils/examples/zapier.ipynb

@@ -7,7 +7,7 @@
    "source": [
     "## Zapier Natural Language Actions API\n",
     "\\\n",
-    "Full docs here: https://nla.zapier.com/api/v1/dynamic/docs\n",
+    "Full docs here: https://nla.zapier.com/api/v1/docs\n",
     "\n",
     "**Zapier Natural Language Actions** gives you access to the 5k+ apps, 20k+ actions on Zapier's platform through a natural language API interface.\n",
     "\n",
@@ -21,7 +21,7 @@
     "\n",
     "2. User-facing (Oauth): for production scenarios where you are deploying an end-user facing application and LangChain needs access to end-user's exposed actions and connected accounts on Zapier.com\n",
     "\n",
-    "This quick start will focus on the server-side use case for brevity. Review [full docs](https://nla.zapier.com/api/v1/dynamic/docs) or reach out to nla@zapier.com for user-facing oauth developer support.\n",
+    "This quick start will focus on the server-side use case for brevity. Review [full docs](https://nla.zapier.com/api/v1/docs) or reach out to nla@zapier.com for user-facing oauth developer support.\n",
     "\n",
     "This example goes over how to use the Zapier integration with a `SimpleSequentialChain`, then an `Agent`.\n",
     "In code, below:"

langchain/tools/zapier/tool.py

@@ -1,6 +1,6 @@
 """## Zapier Natural Language Actions API
 \
-Full docs here: https://nla.zapier.com/api/v1/dynamic/docs
+Full docs here: https://nla.zapier.com/api/v1/docs
 
 **Zapier Natural Language Actions** gives you access to the 5k+ apps, 20k+ actions
 on Zapier's platform through a natural language API interface.
@@ -24,7 +24,7 @@ NLA offers both API Key and OAuth for signing NLA API requests.
     connected accounts on Zapier.com
 
 This quick start will focus on the server-side use case for brevity.
-Review [full docs](https://nla.zapier.com/api/v1/dynamic/docs) or reach out to
+Review [full docs](https://nla.zapier.com/api/v1/docs) or reach out to
 nla@zapier.com for user-facing oauth developer support.
 
 Typically you'd use SequentialChain, here's a basic example:
@@ -92,7 +92,7 @@ class ZapierNLARunAction(BaseTool):
             (eg. "get the latest email from Mike Knoop" for "Gmail: find email" action)
         params: a dict, optional. Any params provided will *override* AI guesses
             from `instructions` (see "understanding the AI guessing flow" here:
-            https://nla.zapier.com/api/v1/dynamic/docs)
+            https://nla.zapier.com/api/v1/docs)
     """
 
     api_wrapper: ZapierNLAWrapper = Field(default_factory=ZapierNLAWrapper)

langchain/utilities/zapier.py

@@ -1,6 +1,6 @@
 """Util that can interact with Zapier NLA.
 
-Full docs here: https://nla.zapier.com/api/v1/dynamic/docs
+Full docs here: https://nla.zapier.com/api/v1/docs
 
 Note: this wrapper currently only implemented the `api_key` auth method for testing
 and server-side production use cases (using the developer's connected accounts on
@@ -24,7 +24,7 @@ from langchain.utils import get_from_dict_or_env
 class ZapierNLAWrapper(BaseModel):
     """Wrapper for Zapier NLA.
 
-    Full docs here: https://nla.zapier.com/api/v1/dynamic/docs
+    Full docs here: https://nla.zapier.com/api/v1/docs
 
     Note: this wrapper currently only implemented the `api_key` auth method for
     testingand server-side production use cases (using the developer's connected
@@ -97,7 +97,7 @@ class ZapierNLAWrapper(BaseModel):
         `params` will always contain an `instructions` key, the only required
         param. All others optional and if provided will override any AI guesses
         (see "understanding the AI guessing flow" here:
-        https://nla.zapier.com/api/v1/dynamic/docs)
+        https://nla.zapier.com/api/v1/docs)
         """
         session = self._get_session()
         response = session.get(self.zapier_nla_api_base + "exposed/")