a few fixes

Author: Noah Raynor

fern/observability/simulations-advanced.mdx

@@ -544,31 +544,6 @@ Test boundary conditions and unusual inputs your assistant might encounter.
 | Pre-production validation | Voice (`vapi.websocket`) | Full end-to-end |
 | Testing hooks/webhooks | Voice (`vapi.websocket`) | Hooks require voice |
 
-### Performance optimization
-
-**Minimize test execution time:**
-
-1. **Use chat mode for initial development:**
-   - `vapi.webchat` runs faster than voice
-   - Switch to voice for final validation
-
-2. **Keep instructions focused:**
-   - Clear, specific instructions complete faster
-   - Avoid overly complex multi-step scenarios
-
-3. **Batch related tests:**
-   - Group similar simulations in suites
-   - Run suites instead of individual simulations
-
-4. **Use iterations strategically:**
-   - `iterations: 1` for deterministic scenarios
-   - Higher iterations for testing consistency
-
-**Cost optimization:**
-- Chat mode costs less (no STT/TTS)
-- Simple personalities (smaller models) cost less
-- Shorter conversations cost less
-
 ## CI/CD integration
 
 Automate simulation runs in your deployment pipeline.

fern/observability/simulations-quickstart.mdx

@@ -35,15 +35,13 @@ Simulations support two transport modes:
 
 <CardGroup cols={2}>
   <Card title="Voice mode" icon="phone">
-    **`vapi.websocket`** - Full voice simulation with audio
-
+    - Full voice simulation with audio
     - Realistic end-to-end testing
     - Tests speech recognition and synthesis
     - Produces call recordings
   </Card>
   <Card title="Chat mode" icon="message">
-    **`vapi.webchat`** - Text-based chat simulation
-
+    - Text-based chat simulation
     - Faster execution
     - Lower cost (no audio processing)
     - Ideal for rapid iteration
@@ -572,17 +570,6 @@ curl -X GET "https://api.vapi.ai/eval/simulation/run/550e8400-e29b-41d4-a716-446
   </Tab>
 </Tabs>
 
-### Transport options
-
-| Provider | Description | Use Case |
-| --- | --- | --- |
-| `vapi.websocket` | Full voice simulation with audio bridge | Production validation, end-to-end testing |
-| `vapi.webchat` | Text-based chat simulation | Rapid iteration, development testing |
-
-<Warning>
-  **Hooks are only supported in voice mode.** If your scenario uses hooks (like `call.started` or `call.ended`), you must use `vapi.websocket` transport.
-</Warning>
-
 ## Step 6: Review results
 
 Analyze the results of your simulation runs to understand how your assistant performed.
@@ -690,63 +677,6 @@ curl -X GET "https://api.vapi.ai/eval/simulation/run?status=ended" \
   Full conversation transcripts are available for all simulation runs, making it easy to understand exactly what happened during each test.
 </Note>
 
-## Troubleshooting
-
-| Issue | Solution |
-| --- | --- |
-| Simulation always fails | Check that evaluations are achievable with your assistant's current capabilities |
-| Run stuck in "running" | Verify your assistant is properly configured and responding |
-| Evaluations not extracting data | Ensure structured output schemas match what your assistant can provide |
-| No audio in recording | Check that you're using `vapi.websocket` transport, not `vapi.webchat` |
-| Hooks not triggering | Hooks only work with `vapi.websocket` transport |
-| Suite won't start | Verify all simulations in the suite exist and have valid scenarios/personalities |
-
-### Common errors
-
-**"assistant-error" status:**
-
-- Check your assistant configuration (model, voice, tools)
-- Verify API keys are valid
-- Test the assistant manually before running simulations
-
-**Evaluation failures:**
-
-- Review the conversation transcript to understand what happened
-- Adjust structured output schemas to better match expected responses
-- Consider whether the personality is making the test unrealistically difficult
-
-<Warning>
-  If simulations consistently fail, test your assistant manually first to ensure it's working correctly before debugging the simulation configuration.
-</Warning>
-
-## API reference
-
-| Endpoint | Method | Description |
-| --- | --- | --- |
-| `/eval/simulation/personality` | POST | Create a personality |
-| `/eval/simulation/personality` | GET | List personalities |
-| `/eval/simulation/personality/:id` | GET | Get a personality |
-| `/eval/simulation/personality/:id` | PATCH | Update a personality |
-| `/eval/simulation/personality/:id` | DELETE | Delete a personality |
-| `/eval/simulation/scenario` | POST | Create a scenario |
-| `/eval/simulation/scenario` | GET | List scenarios |
-| `/eval/simulation/scenario/:id` | GET | Get a scenario |
-| `/eval/simulation/scenario/:id` | PATCH | Update a scenario |
-| `/eval/simulation/scenario/:id` | DELETE | Delete a scenario |
-| `/eval/simulation` | POST | Create a simulation |
-| `/eval/simulation` | GET | List simulations |
-| `/eval/simulation/:id` | GET | Get a simulation |
-| `/eval/simulation/:id` | PATCH | Update a simulation |
-| `/eval/simulation/:id` | DELETE | Delete a simulation |
-| `/eval/simulation/suite` | POST | Create a suite |
-| `/eval/simulation/suite` | GET | List suites |
-| `/eval/simulation/suite/:id` | GET | Get a suite |
-| `/eval/simulation/suite/:id` | PATCH | Update a suite |
-| `/eval/simulation/suite/:id` | DELETE | Delete a suite |
-| `/eval/simulation/run` | POST | Start a simulation run |
-| `/eval/simulation/run` | GET | List runs |
-| `/eval/simulation/run/:id` | GET | Get run details |
-
 ## Next steps
 
 <CardGroup cols={2}>