plano/demos/llm_routing/model_alias_routing
Adil Hafeez 78f761ef75
Clean up dead demos and restructure directory layout
Phase 1 - Remove dead/duplicate content:
- Delete demos/samples_java/ (incomplete Java demo)
- Delete demos/shared/chatbot_ui/ (replaced by AnythingLLM)
- Delete demos/shared/grafana/, prometheus/, logfire/, honeycomb/, signoz/
  (legacy observability stacks; only jaeger is retained)
- Delete variant docker-compose files (honeycomb, logfire, signoz, jaeger)
- Delete demos/use_cases/spotify_bearer_auth/run_demo.sh (stale script)

Phase 2 - Restructure into semantic categories:
- getting_started/  : weather_forecast, llm_gateway
- agent_orchestration/ : travel_agents, multi_agent_crewai_langchain
- llm_routing/       : model_alias_routing, preference_based_routing, claude_code_router
- filter_chains/     : http_filter, mcp_filter
- integrations/      : ollama, spotify_bearer_auth
- advanced/          : model_choice_test_harness, multi_turn_rag,
                       currency_exchange, stock_quote

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2026-02-15 01:43:31 -08:00
..
config_with_aliases.yaml Clean up dead demos and restructure directory layout 2026-02-15 01:43:31 -08:00
README.md Clean up dead demos and restructure directory layout 2026-02-15 01:43:31 -08:00
run_demo.sh Clean up dead demos and restructure directory layout 2026-02-15 01:43:31 -08:00

Model Alias Demo Suite

This directory contains demos for the model alias feature in Plano.

Overview

Model aliases allow clients to use friendly, semantic names instead of provider-specific model names. For example:

  • arch.summarize.v14o-mini (fast, cheap model for summaries)
  • arch.reasoning.v1gpt-4o (capable model for complex reasoning)
  • creative-modelclaude-3-5-sonnet (creative tasks)

Configuration

The arch_config_with_aliases.yaml file defines several aliases:

# Model aliases - friendly names that map to actual provider names
model_aliases:
  # Alias for summarization tasks -> fast/cheap model
  arch.summarize.v1:
    target: gpt-4o-mini

  # Alias for general purpose tasks -> latest model
  arch.v1:
    target: o3

  # Alias for reasoning tasks -> capable model
  arch.reasoning.v1:
    target: gpt-4o

  # Alias for creative tasks -> Claude model
  arch.creative.v1:
    target: claude-3-5-sonnet-20241022

  # Alias for quick responses -> fast model
  arch.fast.v1:
    target: claude-3-haiku-20240307

  # Semantic aliases
  summary-model:
    target: gpt-4o-mini

  chat-model:
    target: gpt-4o

  creative-model:
    target: claude-3-5-sonnet-20241022

Prerequisites

  • Install all dependencies as described in the main Plano README (link)
  • Set your API keys in your environment:
    • export OPENAI_API_KEY=your-openai-key
    • export ANTHROPIC_API_KEY=your-anthropic-key (optional, but recommended for Anthropic tests)

How to Run

  1. Start the demo:

    sh run_demo.sh
    
    • This will create a .env file with your API keys (if not present).
    • Starts Plano gateway with model alias config (arch_config_with_aliases.yaml).
  2. To stop the demo:

    sh run_demo.sh down
    
    • This will stop Plano gateway and any related services.

Example Requests

OpenAI client with alias arch.summarize.v1

curl -sS -X POST "http://localhost:12000/v1/chat/completions" \
  -H "Authorization: Bearer test-key" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "arch.summarize.v1",
    "max_tokens": 50,
    "messages": [
      { "role": "user",
        "content": "Hello, please respond with exactly: Hello from alias arch.summarize.v1!"
      }
    ]
  }' | jq .

OpenAI client with alias arch.v1

curl -sS -X POST "http://localhost:12000/v1/chat/completions" \
  -H "Authorization: Bearer test-key" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "arch.v1",
    "max_tokens": 50,
    "messages": [
      { "role": "user",
        "content": "Hello, please respond with exactly: Hello from alias arch.v1!"
      }
    ]
  }' | jq .

Anthropic client with alias arch.summarize.v1

curl -sS -X POST "http://localhost:12000/v1/messages" \
  -H "x-api-key: test-key" \
  -H "anthropic-version: 2023-06-01" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "arch.summarize.v1",
    "max_tokens": 50,
    "messages": [
      { "role": "user",
        "content": "Hello, please respond with exactly: Hello from alias arch.summarize.v1 via Anthropic!"
      }
    ]
  }' | jq .

Anthropic client with alias arch.v1

curl -sS -X POST "http://localhost:12000/v1/messages" \
  -H "x-api-key: test-key" \
  -H "anthropic-version: 2023-06-01" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "arch.summarize.v1",
    "max_tokens": 50,
    "messages": [
      { "role": "user",
        "content": "Hello, please respond with exactly: Hello from alias arch.summarize.v1 via Anthropic!"
      }
    ]
  }' | jq .

Notes

  • The .env file will be created automatically if missing, with your API keys.
  • If ANTHROPIC_API_KEY is not set, Anthropic requests will not work.
  • You can add more aliases in arch_config_with_aliases.yaml.
  • All curl examples use jq . for pretty-printing JSON responses.

Troubleshooting

  • Ensure your API keys are set in your environment before running the demo.
  • If you see errors about missing keys, set them and re-run the script.
  • For more details, see the main Plano documentation.