Amazon Chat Completions Server

A unified, provider-agnostic chat completions API server supporting OpenAI and AWS Bedrock

View the Project on GitHub teabranch/amazon-chat-completions-server

Amazon Chat Completions Server

A unified, provider-agnostic chat completions API server supporting OpenAI and AWS Bedrock.

Get started now View on GitHub


🚀 Quick Start

Installation & Setup

# Clone and install
git clone https://github.com/teabranch/amazon-chat-completions-server.git
cd amazon-chat-completions-server
uv pip install -e .

# Configure environment
amazon-chat config set

# Start server
amazon-chat serve --host 0.0.0.0 --port 8000

Basic Usage

# Test the unified endpoint
curl -X POST http://localhost:8000/v1/chat/completions \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer your-api-key" \
  -d '{
    "model": "gpt-4o-mini",
    "messages": [{"role": "user", "content": "Hello!"}],
    "stream": false
  }'

🔄 Unified Endpoint

Single Endpoint for Everything

The /v1/chat/completions endpoint is the only endpoint you need. It:

  1. Auto-detects your input format (OpenAI, Bedrock Claude, Bedrock Titan)
  2. Routes to the appropriate provider based on model ID
  3. Converts between formats as needed
  4. Streams responses in real-time when requested
  5. Returns responses in your preferred format

Format Combinations

All format combinations are supported through the unified endpoint:

Input Format Output Format Use Case Streaming
OpenAI OpenAI Standard OpenAI usage ✅
OpenAI Bedrock Claude OpenAI clients → Bedrock response ✅
OpenAI Bedrock Titan OpenAI clients → Titan response ✅
Bedrock Claude OpenAI Bedrock clients → OpenAI response ✅
Bedrock Claude Bedrock Claude Claude format preserved ✅
Bedrock Titan OpenAI Titan clients → OpenAI response ✅
Bedrock Titan Bedrock Titan Titan format preserved ✅

📚 Documentation

Core Documentation

Guides

Development


🎯 Key Features

Unified Interface

Enterprise Ready

Developer Friendly



📄 License

This project is licensed under the MIT License - see the LICENSE file for details.