This directory contains Postman collections and environments for testing the AI Agents API with organized agent folders.
AgentsAPI.postman_collection.json- API collection with organized agent foldersShip_AI_Agents_Environment.postman_environment.json- Environment variablesREADME.md- This file
The collection is organized into folders for better testing:
- Health Check - Service status
- Root Endpoint - Welcome message
- API Documentation - Swagger docs
- Basic Chat - Chest Pain - Simple medical case
- Simple Case - Headache - Basic headache scenario
- Complex Case - Shortness of Breath - Multi-turn conversation
- Emergency Case - Severe Chest Pain - Critical medical scenario
- Plan Trip - New York to Paris - International trip planning
- Plan Trip - London to Tokyo - Long-distance trip planning
- Translate English to Spanish - Basic translation
- Translate French to English - Reverse translation
- Search Flights - NYC to LAX - Flight search and booking
- Search Hotels - Paris - Hotel search and booking
- Summarize Trip Plan - Trip plan summarization
- List Tables - Show available database tables
- Get Table Schema - Users - Display table structure
- Query Table - Products - Retrieve table records
- Search Records - Find User - Search specific records
- Get Table Statistics - Orders - Table analytics
- Complex Query - Product Analysis - Advanced database operations
- Invalid Agent - Test with non-existent agent
- Missing Required Fields - Test validation
- Invalid JSON - Test malformed requests
- Open Postman
- Click "Import" button
- Select
AgentsAPI.postman_collection.json - Select
Ship_AI_Agents_Environment.postman_environment.json
- Click the environment dropdown (top right)
- Select "AgentShip Environment"
- Verify variables are set correctly
- Select any request from the collection
- Click "Send"
- Check the response
- Base URL:
http://localhost:7001 - Health Check:
http://localhost:7001/health - API Docs (Swagger):
http://localhost:7001/swagger - API Docs (ReDoc):
http://localhost:7001/redoc - Framework Docs:
http://localhost:7001/docs(after building withmake docs-build)
- Base URL:
https://your-production-url.herokuapp.com(replace with your actual production URL) - Health Check:
https://your-production-url.herokuapp.com/health - API Docs (Swagger):
https://your-production-url.herokuapp.com/swagger - API Docs (ReDoc):
https://your-production-url.herokuapp.com/redoc - Framework Docs:
https://your-production-url.herokuapp.com/docs(if deployed)
- GET
/health - Description: Check if the service is running
- Response:
{"status": "running"}
- POST
/api/agents/chat - Description: Chat with AI agents
- Body: JSON with agent_name, user_id, session_id, query, features
- GET
/ - Description: Welcome message
- Response:
{"message": "Welcome to the AgentShip API!"}
base_url- Local development URLbase_url_production- Production URL
user_id- Test user ID (default: "user-123")session_id- Test session ID (default: "session-456")agent_name- Agent to test (default: "medical_followup")
GET {{base_url}}/health{
"agent_name": "medical_followup",
"user_id": "user-123",
"session_id": "session-456",
"query": [
{
"speaker": "Patient",
"text": "I have chest pain"
},
{
"speaker": "Doctor",
"text": "Can you describe it?"
},
{
"speaker": "Patient",
"text": "It's a sharp, stabbing pain that started after lifting heavy boxes"
}
],
"features": [
{
"feature_name": "max_followups",
"feature_value": 5
}
]
}{
"agent_name": "trip_planner_agent",
"user_id": "user-123",
"session_id": "session-456",
"query": {
"source": "New York",
"destination": "Paris"
},
"features": []
}{
"agent_name": "translation_agent",
"user_id": "user-123",
"session_id": "session-456",
"query": {
"text": "Hello, how are you?",
"from_language": "en",
"to_language": "es"
},
"features": []
}{
"agent_name": "database",
"user_id": "user-123",
"session_id": "session-456",
"query": "What tables are available in the database?",
"features": []
}{
"agent_name": "database",
"user_id": "user-123",
"session_id": "session-456",
"query": "Show me all electronics products and their details",
"features": []
}- Test if service is running
- Should return
{"status": "running"}
- New Session: Use a new session_id, should create new session and return followup questions
- Existing Session: Use same session_id, should continue conversation
- Different Cases: Test various medical scenarios (chest pain, headache, emergency)
- Trip Planning: Test with different source and destination pairs
- Complex Routes: Test multi-city or international trips
- Date Specifications: Test with specific travel dates
- Language Pairs: Test various language combinations
- Text Length: Test with short and long text
- Special Characters: Test with accented characters
- Route Search: Test flight searches between different cities
- Date Flexibility: Test with flexible date ranges
- Price Filters: Test with budget constraints
- Location Search: Test hotel searches in different cities
- Date Ranges: Test with specific check-in/check-out dates
- Amenities: Test with specific hotel requirements
- Trip Summaries: Test summarization of complex trip plans
- Key Points: Verify important details are captured
- Format: Test different summary formats
- List Tables: Should return available database tables
- Schema Queries: Get table structure and column information
- Data Queries: Retrieve records with limits and filters
- Search Operations: Find specific records by field values
- Statistics: Get table analytics and data insights
- Complex Queries: Test natural language database operations
- Test with invalid agent_name
- Test with malformed request body
- Test missing required fields
- Should return appropriate error messages
- Check if service is running locally:
curl http://localhost:7001/health - Verify environment variables are set correctly
- Check if port 7001 is available
- Verify the endpoint URL is correct
- Check if the service is deployed properly
- Ensure the route exists in the API
- Check service logs for detailed error information
- Verify API keys are set correctly
- Check database connection if using persistent sessions
- Verify API keys are valid and have sufficient credits
- Check if the service is configured correctly
- Ensure environment variables are set
{
"status": "running"
}{
"agent_name": "medical_followup",
"user_id": "user-123",
"session_id": "session-456",
"sender": "SYSTEM",
"success": true,
"agent_response": {
"followup_questions": [
"Have you experienced any shortness of breath?",
"Did the pain radiate to your arm or jaw?",
"Are you experiencing any nausea or sweating?"
],
"count": 3
}
}{
"agent_name": "database",
"user_id": "user-123",
"session_id": "session-456",
"sender": "SYSTEM",
"success": true,
"agent_response": "Based on the database query, here are the available tables:\n\n1. **users** - Contains user information (id, name, email, age)\n2. **products** - Contains product catalog (id, name, price, category)\n3. **orders** - Contains order information (id, user_id, product_id, quantity, total)\n\nEach table has sample data that you can query. Would you like me to show you the schema or data from any specific table?"
}{
"detail": "Agent 'invalid_agent' not found. Available agents: ['medical_followup_agent']"
}- Select "Ship AI Agents Environment"
- Ensure
base_urlis set tohttp://localhost:7001 - Make sure local service is running
- Select "Ship AI Agents Environment"
- Change
base_urlto your actual production URL (e.g.,https://your-app.herokuapp.com) - Or use
base_url_productionvariable
- Main README - High-level architecture
- Full Documentation - Complete documentation (when server is running)
- Heroku Deployment - Production deployment
- Database Setup - Database configuration