Skip to main content

Health Care Consultant Configuration

These examples use the tools registry: tools are created once at /v2/tools and attached to the PAL. Tools here use the default app-message delivery, so calls arrive as conversation.tool_call events for your frontend to handle.
The General Doctor uses a single LLM tool that looks up cures for a named disease.
get_cures (LLM tool)
The PAL sets the models and no longer defines tools inline:
PAL configuration
This PAL is designed to act as a friendly virtual doctor, offering quick answers to user health inquiries. It includes:
  • PAL Identity: A helpful and knowledgeable “Health Care” assistant who can provide medicines to cure various diseases.
  • Full Pipeline Mode: Enables the full Tavus conversational pipeline, including STT, LLM, and TTS.
  • System Prompt: instructs the PAL to behave as a trusted medical advisor. It ensures the PAL understands its role in responding to disease-related questions and calling the appropriate tool to provide answers.
  • Context: Clarifies expected user inputs (e.g., “What is the cure to X?”) and defines how the PAL should interpret and respond - by acknowledging the illness and triggering the attached get_cures tool with the specified disease name.
  • Model Layers:
    • LLM Configuration: Uses the tavus-gemma-4 model with speculative inference. The attached get_cures tool accepts a single string parameter (disease) and is called when disease-related queries are detected.
    • TTS Layer: Employs the cartesia voice engine with emotion control.
    • STT Layer: Uses tavus-advanced engine with smart turn detection for seamless real-time conversations.

Create a Conversation with the Health Care Consultant

1

Step 1: Create the tools

Create each tool at /v2/tools. The response returns a tool_id you’ll attach to the PAL in Step 3.
2

Step 2: Create the PAL

Create the PAL using the following request. There are no inline tools - they’re attached in the next step.
Replace <api-key> with your actual API key. You can generate one in the PAL Maker.
3

Step 3: Attach the tools to the PAL

Attach each variant’s tools to its PAL by tool_id. Vision tools require perception_model: "raven-1" on the PAL, which the Dermatologist configuration already sets.
4

Step 4: Create a Conversation

Create a conversation using the following request:
cURL
  • Replace <api_key> with your actual API key.
  • Replace <health_care_pal_id> with the ID of the PAL configured as either a General Doctor or a Dermatologist.
5

Step 5: Join the Conversation

Click the link in the conversation_url field to join the conversation: