chore: replace gpt-3.5-turbo occurrences with gpt-4o to stay up-to-date

Author: goosewin

fern/customization/custom-llm/tool-calling-integration.mdx

@@ -241,7 +241,7 @@ Once your endpoints are set up, try testing them with these cURL commands.
 curl -X POST https://custom-llm-url/chat/completions \
   -H "Content-Type: application/json" \
   -d '{
-        "model": "gpt-3.5-turbo",
+        "model": "gpt-4o",
         "messages": [
           {"role": "user", "content": "I need a payment link."}
         ],
@@ -268,7 +268,7 @@ Streaming chunks eventually include the result (e.g., a payment link) returned b
 curl -X POST https://custom-llm-url/chat/completions \
   -H "Content-Type: application/json" \
   -d '{
-        "model": "gpt-3.5-turbo",
+        "model": "gpt-4o",
         "messages": [
           {"role": "user", "content": "Please transfer my call."}
         ],
@@ -423,4 +423,4 @@ By building each layer step by step and testing with cURL, you can fine-tune you
 For your convenience, you can find the complete source code for this Custom LLM integration here:
 
 **[Custom LLM with Vapi Integration – Complete Code](https://codesandbox.io/p/devbox/gfwztp)**
-```
+```

fern/sdk/web.mdx

@@ -59,7 +59,7 @@ vapi.start({
   },
   model: {
     provider: "openai",
-    model: "gpt-3.5-turbo",
+    model: "gpt-4o",
     messages: [
       {
         role: "system",

fern/server-url/events.mdx

@@ -34,7 +34,7 @@ With each response, the assistant will automatically determine what functions to
   "name": "Ryan's Assistant",
   "model": {
     "provider": "openai",
-    "model": "gpt-3.5-turbo",
+    "model": "gpt-4o",
     "functions": [
       {
         "name": "sendEmail",
@@ -117,7 +117,7 @@ Alternatively, if you prefer to define a transient assistant dynamically, your s
     "firstMessage": "Hey Ryan, how are you?",
     "model": {
       "provider": "openai",
-      "model": "gpt-3.5-turbo",
+      "model": "gpt-4o",
       "messages": [
         {
           "role": "system",

fern/tools/default-tools.mdx

@@ -18,7 +18,7 @@ This function is provided when `transferCall` is included in the assistant's lis
 {
   "model": {
     "provider": "openai",
-    "model": "gpt-3.5-turbo",
+    "model": "gpt-4o",
     "messages": [
       {
         "role": "system",
@@ -48,7 +48,7 @@ This function is provided when `endCall` is included in the assistant's list of
 {
   "model": {
     "provider": "openai",
-    "model": "gpt-3.5-turbo",
+    "model": "gpt-4o",
     "messages": [
       {
         "role": "system",
@@ -72,7 +72,7 @@ This function is provided when `sms` is included in the assistant's list of avai
 {
   "model": {
     "provider": "openai",
-    "model": "gpt-3.5-turbo",
+    "model": "gpt-4o",
     "messages": [
       {
         "role": "system",
@@ -99,7 +99,7 @@ This function is provided when `dtmf` is included in the assistant's list of ava
 {
   "model": {
     "provider": "openai",
-    "model": "gpt-3.5-turbo",
+    "model": "gpt-4o",
     "messages": [
       {
         "role": "system",
@@ -192,4 +192,4 @@ At the assistant level, the `serverUrl` can be specified in the assistant config
 If the `serverUrl` is not defined either at the account level or the assistant level, the function call will simply be added to the chat history. This can be particularly useful when you want a function call to trigger an action on the frontend.
 
 For instance, the frontend can listen for specific function calls in the chat history and respond by updating the user interface or performing other actions. This allows for a dynamic and interactive user experience, where the frontend can react to changes in the conversation in real time.
-</Accordion>
+</Accordion>