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.

fav - Skill - OpenSmartRoute

Imported from synle/fav (AGENTS.md). Install upstream with npx skills add synle/fav. Copyright stays with the author.

AGENTS.md

Cross-Agent File Layout

Store skills in .agents/skills/<name>/SKILL.md, not .claude/skills/.
Use AGENTS.md for agent context. When CLAUDE.md exists without an AGENTS.md in the same directory, rename it to AGENTS.md. If both exist, merge their instructions into AGENTS.md without losing distinct guidance before removing CLAUDE.md.
Update references to migrated skill paths and renamed context files.

GitHub Raw File URLs

When fetching raw file content from GitHub repos, always use the ?raw=1 blob URL format:

https://github.com/{owner}/{repo}/blob/head/{path}?raw=1

Do NOT use:

https://api.github.com/repos/{owner}/{repo}/contents/{path} (GitHub Contents API)
https://raw.githubusercontent.com/{owner}/{repo}/{branch}/{path}

Git / PR Merge Policy

Always use squash and merge when merging PRs. Never use merge commits or rebase merges. This keeps the git history clean with one commit per PR.
You may git merge origin/main or git merge origin/master locally to sync branches, but PR merges must always be squash merges.

# after Install: the listing is in your workspace's routing pool - a plan picks it for its slot curl -s -X POST https://api.opensmartroute.ai/api/v1/route -H 'Authorization: Bearer $OSR_API_KEY' -H 'Content-Type: application/json' -d '{"text": "...", "plan": true}'

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

fav

About

AGENTS.md

Cross-Agent File Layout

GitHub Raw File URLs

Git / PR Merge Policy

Use it

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