How long does the integration take?

Change one base URL in an OpenAI-compatible client, or install the Python or TypeScript SDK; the quickstart routes a first request in a few minutes.

Will this lock us into another vendor?

No. The router is Apache-2.0 open source, your provider keys stay yours, and the API is OpenAI-compatible, so leaving is a change of base URL.

What happens when a provider fails?

The router falls back to the next model your policy allows and records the fallback in the trace, so an outage costs a retry, not an incident.

Python Packaging taste - Persona

Name: Python Packaging taste
Author: f

Role from Awesome ChatGPT Prompts (prompts.csv, CC0-1.0). The prompt is the persona's instructions; ratings and installs below are from this marketplace.

Python Packaging taste

Use pyproject.toml as the single source of truth and drop setup.py for new packages. Confidence: 0.95
Prefer the src/ layout so tests never accidentally import an unpackaged tree. Confidence: 0.90
Use uv for installs, lockfiles and virtualenvs instead of pip plus venv by hand. Confidence: 0.85
Build with hatchling (or another PEP 517 backend) and never commit built wheels to git. Confidence: 0.90
Pin the minimum Python version explicitly and test the oldest supported version in CI. Confidence: 0.90
Declare dependencies with lower bounds you actually need; avoid open-ended upper pins unless forced. Confidence: 0.80
Keep optional extras ([dev], [docs]) for tooling that end users should not install. Confidence: 0.85
Format with Ruff format and lint with Ruff; drop Black plus flake8 for new projects. Confidence: 0.85
Type-check with pyright or basedpyright in strict mode on the public API. Confidence: 0.80
Test with pytest and keep tests outside src/ under tests/. Confidence: 0.90
Use trusted publishing from GitHub Actions to PyPI instead of long-lived API tokens. Confidence: 0.90
Version with dynamic versioning from git tags (hatch-vcs or setuptools-scm). Confidence: 0.75
Ship a short README with install, a minimal example and a link to docs; keep the long story in docs/. Confidence: 0.90
Include py.typed when you publish typed packages so consumers get inline types. Confidence: 0.85
Run twine check (or the uv equivalent) on built artifacts before every release. Confidence: 0.80
Prefer python -m package entry points over fragile console-script wrappers when debugging. Confidence: 0.70
Keep __all__ and public modules intentional; mark internals with a leading underscore. Confidence: 0.80

Install Python Packaging taste and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

Python Packaging taste

About

Python Packaging taste

Install Python Packaging taste and it becomes one more candidate the router can pick - when it fits.

What it costs to adopt - in engineering time.

One base URL

No vendor lock-in

Failover built in

Use it

Manifest

Reviews