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.

web - Skill - OpenSmartRoute

Imported from dsaub/PokeTeamCalculator (web/AGENTS.md). Install upstream with npx skills add dsaub/PokeTeamCalculator --skill web. Copyright stays with the author.

Repo Agent Context

This is the root routing contract for Claude Code and Codex. Load this before task-local artifacts.

Workflow Contract

Use first principles, one source of truth, and no steady-state compatibility paths.
Treat ../docs/web/spec.md as product truth; tasks/current.md is derived state and tasks/todos.md is the deferred-goal ledger.
Write a plan before cross-module changes, architecture changes, and dependency upgrades. Small changes do not need a plan.
Read .ai/context/capabilities.json and .ai/context/context-map.json before adding scoped agent context.
When a branch changes a capability's responsibility, entrypoints, relations or flows, run repo-harness architecture-projection check --json before review and follow repo-harness-architecture (assets/skill-commands/repo-harness-architecture/references/worker.md in the installed repo-harness skill: ~/.claude/skills/repo-harness/ or ~/.codex/skills/repo-harness/).
Write human-facing documents (../docs/web/, plans/prds/, design briefs) in the language set by .ai/harness/policy.json#documentation.language; keep section headers, field keys, and technical terms in English. Agent-facing artifacts stay English.
Keep _ref/ ignored external reference material and _ops/ ignored local operations state.

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

web

About

Repo Agent Context

Workflow Contract

Use it

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