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.

review - Prompt - OpenSmartRoute

Prompt file imported from BrianMF7/HackNight (.cursor/commands/review.md). Copyright stays with the author.

Read and follow .cursor/skills/code-review-and-quality/SKILL.md.

This command is the quality verdict. Do not treat /ponytail-review as a substitute. Ponytail does not edit this review's findings.

Review the current changes (staged or recent commits) across all five axes:

Correctness — Does it match the spec? Edge cases handled? Tests adequate?
Readability — Clear names? Straightforward logic? Well-organized?
Architecture — Follows existing patterns? Clean boundaries? Right abstraction level?
Security — Input validated? Secrets safe? Auth checked? (Use .cursor/skills/security-and-hardening/SKILL.md)
Performance — No N+1 queries? No unbounded ops? (Use .cursor/skills/performance-optimization/SKILL.md)

Categorize findings as Critical, Important, or Suggestion. Output a structured review with specific file:line references and fix recommendations.

When a finding is a keep (must stay), say so clearly so /ponytail-review cannot mark it for deletion.

Read and follow `.cursor/skills/code-review-and-quality/SKILL.md`. This command is the quality verdict. Do not treat `/ponytail-review` as a substitute. Ponytail does not edit this review's findings. Review the current changes (staged or recent commits) across all five axes: 1. **Correctness** — Does it match the spec? Edge cases handled? Tests adequate? 2. **Readability** — Clear names? Straightforward logic? Well-organized? 3. **Architecture** — Follows existing patterns? Clean boundaries? Right abstraction level? 4. **Security** — Input validated? Secrets safe? Auth checked? (Use `.cursor/skills/security-and-hardening/SKILL.md`) 5. **Performance** — No N+1 queries? No unbounded ops? (Use `.cursor/skills/performance-optimization/SKILL.md`) Categorize findings as Critical, Important, or Suggestion. Output a structured review with specific file:line references and fix recommendations. When a finding is a keep (must stay), say so clearly so `/ponytail-review` cannot mark it for deletion.

Install review 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.

review

About

Use it

Install review 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

Manifest

Reviews