This guide shows how all of EDDI's components work together to create a complete, functional agent. We'll build a real-world example step-by-step, explaining how each piece connects.
The Big Picture
EDDI agents are composed of interconnected components that flow through the Lifecycle Pipeline:
Dictionary → Parser → Behavior Rules → Actions → HTTP Calls / LLM → Output → User
↓ ↓ ↓ ↓ ↓ ↓
Define Extract Decide what Triggers Fetch data Format Response
words meaning to do execution or call AI response
Each component is a separate configuration that's combined into packages, which are assembled into agents.
Real-World Example: Hotel Booking Agent
Let's build an agent that helps users book hotel rooms. It will:
Greet users
Ask for city and dates
Check availability via API
Show options
Confirm booking via API
Component Overview
We'll need:
Dictionary: Define hotel-related vocabulary
Parser: Extract entities (cities, dates)
Behavior Rules: Conversation flow logic
Properties: Store user inputs
HTTP Calls: Check availability and create bookings
curl -X POST http://localhost:7070/outputstore/outputsets \
-H "Content-Type: application/json" \
-d '{
"outputSet": [
{
"action": "welcome",
"outputs": [
{
"valueAlternatives": [
{
"type": "text",
"text": "Welcome to Hotel Booking Agent! I can help you find and book hotel rooms. Which city are you interested in?"
}
]
}
]
},
{
"action": "httpcall(check-availability)",
"outputs": [
{
"valueAlternatives": [
{
"type": "text",
"text": "Great! I found {memory.current.httpCalls.availableRooms.rooms.size()} available rooms in {context.city}. Here are your options:"
}
]
}
]
},
{
"action": "booking_confirmed",
"outputs": [
{
"valueAlternatives": [
{
"type": "text",
"text": "🎉 Booking confirmed! Your booking ID is {context.bookingId}. Total price: ${context.totalPrice}. We'\''ve sent a confirmation email. Have a great stay!"
}
]
}
]
}
]
}'
{
"conversationId": "CONV_ID",
"conversationOutputs": [
{
"output": [
"Welcome to Hotel Booking Agent! I can help you find and book hotel rooms. Which city are you interested in?"
]
}
]
}
{
"conversationOutputs": [
{
"output": [
"🎉 Booking confirmed! Your booking ID is BK-12345. Total price: $450. We've sent a confirmation email. Have a great stay!"
]
}
]
}
User: "check availability in Paris"
↓
┌─────────────────────────────────────────────────────────────┐
│ 1. PARSER (uses Dictionary) │
│ Input: "check availability in Paris" │
│ Output: ["intent(check_availability)"] │
└─────────────────────────────────────────────────────────────┘
↓
┌─────────────────────────────────────────────────────────────┐
│ 2. BEHAVIOR RULES │
│ Condition: intent(check_availability) + context.city │
│ Match: YES │
│ Action: httpcall(check-availability) │
└─────────────────────────────────────────────────────────────┘
↓
┌─────────────────────────────────────────────────────────────┐
│ 3. HTTP CALLS │
│ Name: check-availability │
│ URL: GET /availability?city=Paris │
│ Response: {rooms: [{id: 101, name: "Deluxe"}, ...]} │
│ Stores: memory.current.httpCalls.availableRooms │
└─────────────────────────────────────────────────────────────┘
↓
┌─────────────────────────────────────────────────────────────┐
│ 4. QUICK REPLY BUILDER │
│ Iterates: availableRooms.rooms │
│ Creates: Quick reply buttons for each room │
└─────────────────────────────────────────────────────────────┘
↓
┌─────────────────────────────────────────────────────────────┐
│ 5. OUTPUT TEMPLATING │
│ Template: "I found {availableRooms.rooms.size()} │
│ rooms in {context.city}" │
│ Result: "I found 5 rooms in Paris" │
└─────────────────────────────────────────────────────────────┘
↓
Response to User with output + quick replies
