​

Authentication

​

Overview

​

User Identification

• Purpose: Associates conversations with specific users for persistence
• Format: String identifier (e.g., “user123”, “anonymous”)
• Scope: Conversation threads and memory management

​

Security Considerations

• API Key Authentication: Bearer token in Authorization header
• OAuth 2.0: Third-party authentication integration
• JWT Tokens: Stateless authentication with claims
• Rate Limiting: Per-user request limits

​

Request Headers

// Optional authentication headers for future implementation
{
  "Authorization": "Bearer your-api-key",
  "X-API-Key": "your-api-key"
}

​

User Context

{
  "resourceId": "user-123",  // User identifier
  "runtimeContext": {
    "metadata": {
      "userId": "user-123"  // Alternative user specification
    }
  }
}