Skip to main content

Multiplexer LLM (Python)

Unlock the Power of Distributed AI 🚀

A lightweight Python library that combines the quotas of multiple open source LLM providers with a single unified API. Seamlessly distribute your requests across various providers hosting open source models, ensuring maximum throughput and reliability.

The Problem: Limited AI Resources

  • ❌ Rate Limit Errors: "Rate limit exceeded" errors hinder your application's performance
  • ❌ Limited Throughput: Single provider constraints limit your AI capabilities
  • ❌ Unpredictable Failures: Rate limits can occur at critical moments
  • ❌ Manual Intervention: Switching providers requires code changes

The Solution: Unified Access to Multiple Providers

  • ✅ Increased Throughput: Combine quotas from multiple open source LLM providers
  • ✅ Error Resilience: Automatic failover when one provider hits rate limits
  • ✅ Seamless Integration: Compatible with OpenAI SDK for easy adoption
  • ✅ Smart Load Balancing: Weight-based distribution across providers for optimal performance

Key Benefits

  • 🚀 Scalable AI: Combine resources from multiple providers for enhanced capabilities
  • 🛡️ Error Prevention: Automatic failover minimizes rate limit failures
  • ⚡ High Availability: Seamless switching between providers ensures continuous operation
  • 🔌 OpenAI SDK Compatibility: Works with existing OpenAI SDK code
  • 📊 Usage Analytics: Track provider performance and rate limits

How It Works

Single Model:        [Model A: 10K RPM] ❌ Rate Limit Error at 10,001 requests
Multiple Providers:  [Provider 1: 10K] + [Provider 2: 15K] + [Provider 3: 20K] = 45,000 RPM ✅
Multiple Models:     [Model A: 10K] + [Model B: 50K] + [Model C: 15K] = 75,000 RPM ✅✅

Installation

pip install multiplexer-llm

The package requires Python 3.8+ and automatically installs the OpenAI Python SDK as a dependency.

Quick Start

import asyncio
import os
from multiplexer_llm import Multiplexer
from openai import AsyncOpenAI

async def main():
    # Create client instances for a few open source models
    model1 = AsyncOpenAI(
        api_key=os.getenv("MODEL1_API_KEY"),
        base_url="https://api.model1.com/v1/",
    )

    model2 = AsyncOpenAI(
        api_key=os.getenv("MODEL2_API_KEY"),
        base_url="https://api.model2.org/v1",
    )

    # Initialize multiplexer
    async with Multiplexer() as multiplexer:
        # Add models with weights
        multiplexer.add_model(model1, 5, "model1-large")
        multiplexer.add_model(model2, 3, "model2-base")

        # Use like a regular OpenAI client
        completion = await multiplexer.chat.completions.create(
            model="placeholder",  # Will be overridden by selected model
            messages=[
                {"role": "system", "content": "You are a helpful assistant."},
                {"role": "user", "content": "What is the capital of France?"},
            ],
        )

        print(completion.choices[0].message.content)
        print("Model usage stats:", multiplexer.get_stats())

# Run the async function
asyncio.run(main())

System One (Jev /v1/systemone) support

Alongside chat completions, the multiplexer routes requests that speak the Jev /v1/systemone wire contract — the standard System One API for atomic noul / choice / score decisions. Same weighted selection, capacity slots, and automatic failover as chat; only the payload shape changes. Point the endpoint clients at any server speaking the contract (e.g. a self-hosted Tachyone) — base_url should include the OpenAI-style /v1 prefix:

async def main():
    model1 = AsyncOpenAI(
        api_key=os.getenv("SYSTEMONE_API_KEY"),
        base_url="https://api.model1.com/v1",
    )

    async with Multiplexer() as multiplexer:
        multiplexer.add_model(model1, 5, "systemone-latest")

        result = await multiplexer.systemone.create(
            state="refund please",
            questions={
                "greeting": {
                    "type": "noul",
                    "instructions": "Is this a greeting?",
                },
                "topic": {
                    "type": "choice",
                    "instructions": "Pick a category.",
                    "criteria": {"billing": "billing issue", "other": None},
                },
                "sentiment": {
                    "type": "score",
                    "instructions": "Rate the sentiment.",
                    "criteria": ["very negative", "negative", "neutral", "positive", "very positive"],
                },
            },
        )

        # Answers come back keyed by question id, in the order asked
        print(result["answers"]["greeting"]["noul"])   # 0.97
        print(result["answers"]["topic"]["choice"])    # "billing"
        print(result["answers"]["sentiment"]["score"]) # 3.4
        print(result["usage"])                          # {"input_tokens": ..., "output_tokens": ...}

Notes:

  • model defaults to "placeholder" and is overridden by the selected endpoint's registered name, exactly like chat.completions.create.
  • The path defaults to /systemone and is merged onto each client's base_url; pass path="/v1/systemone" if your base_url does not already carry the /v1 prefix.
  • Failover matches the Jev error contract: 429 and 529 disable the endpoint for 60s and try the next one; connection errors and other 5xx disable for 15s. 401/422 propagate immediately.

How Primary and Fallback Models Work

The multiplexer operates with a two-tier system:

Primary Models (add_model)

  • First choice: Used when available
  • Weight-based selection: Higher weights = higher probability of selection

Fallback Models (add_fallback_model)

  • Backup safety net: Activated when all primary models hit rate limits

API Examples

Creating a Multiplexer

from multiplexer_llm import Multiplexer

# Create multiplexer instance
multiplexer = Multiplexer()

# Or use as async context manager (recommended)
async with Multiplexer() as multiplexer:
    # Your code here
    pass

Adding Models

# Add a primary model
multiplexer.add_model(client: AsyncOpenAI, weight: int, model_name: str)

# Add a fallback model
multiplexer.add_fallback_model(client: AsyncOpenAI, weight: int, model_name: str)

Contributing

Contributions are welcome! Please feel free to submit a Pull Request.

About Haven Network

Haven Network builds open-source tools to help online communities produce high-quality data for multi-modal AI, with a strong focus on local inference and data privacy.

Metadata

Release files for multiplexer-llm 0.3.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for multiplexer-llm 0.3.0
File Size Uploaded
multiplexer_llm-0.3.0.tar.gz 26.3 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for multiplexer-llm 0.3.0
File Interpreter ABI Platform
multiplexer_llm-0.3.0-py3-none-any.whl Python 3 none any Details

Total release size: 42.9 kB

Release files / multiplexer_llm-0.3.0.tar.gz

Download URL multiplexer_llm-0.3.0.tar.gz
Size 26.3 kB
Tags Source
SHA-256 checksum
How to use checksums
3fd6d14887dbafacb505c409d5efad256956d599055e053b7daeb6c92418255f
BLAKE2b-256 checksum
How to use checksums
09183616e9e261cbb1969698e27054d08d307f505b6776300979b3646a942f32
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 13, 2026.

Transparency log

Release files / multiplexer_llm-0.3.0-py3-none-any.whl

Download URL multiplexer_llm-0.3.0-py3-none-any.whl
Size 16.6 kB
Tags Python 3
SHA-256 checksum
How to use checksums
921fb0f1ddfa8c891ae7954f48ffe6d50db11dfae5ed717add9a1cb2597a6c00
BLAKE2b-256 checksum
How to use checksums
648eff2abda1a007045ebc4bb464d72a82c7827132d13f1368e263897d55f357
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 13, 2026.

Transparency log

Release history Release notifications | RSS feed

0.4.0

2 release files

This release

0.3.0 This release

2 release files

0.2.3

2 release files

0.2.2

2 release files

0.2.1

2 release files

0.2.0

2 release files

0.1.7

2 release files

0.1.6

2 release files

0.1.5

2 release files

0.1.4

2 release files

0.1.3

2 release files

0.1.2

2 release files

0.1.1

2 release files

0.1.0

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page