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.

test-1 - Persona - OpenSmartRoute

Chat mode imported from jefeish/split-token-app (.github/chatmodes/test-1.chatmode.md). Copyright stays with the author.

name: Custom Test Chat Mode

description: >

A brief summary of what this chat mode is for.

instructions: >

Custom instructions for Copilot’s behavior in this mode (e.g., tone, style, rules).

context:

Specifies what context Copilot should use (e.g., open files, workspace, selection).

Example:

files: [".js", ".md"]

workspace: true

tools:

List of enabled/disabled tools (e.g., terminal, file editing, code search).

Example:

enable: ["terminal", "file-edit"]

disable: ["code-search"]

triggers:

Keywords or actions that activate this chat mode.

Example:

- "test"

- "debug"

prompts:

Predefined prompts or questions for quick access.

Example:

- "Explain this code"

- "Write unit tests"

outputFormatting:

Rules for markdown, code blocks, math, etc.

Example:

markdown: true

codeBlocks: true

permissions:

Controls what actions Copilot can take (e.g., edit files, run commands).

Example:

editFiles: false

runCommands: false

environment:

OS, shell, or other environment-specific settings.

Example:

os: "macOS"

shell: "zsh"

customInstructions:

Additional instructions from the user for this mode.

Example:

- "Always include 'This is a test chat mode.' in responses."

# 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 test-1 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.

About

description: >

A brief summary of what this chat mode is for.

instructions: >

Custom instructions for Copilot’s behavior in this mode (e.g., tone, style, rules).

context:

Specifies what context Copilot should use (e.g., open files, workspace, selection).

Example:

files: [".js", ".md"]

workspace: true

tools:

List of enabled/disabled tools (e.g., terminal, file editing, code search).

Example:

enable: ["terminal", "file-edit"]

disable: ["code-search"]

triggers:

Keywords or actions that activate this chat mode.

Example:

- "test"

- "debug"

prompts:

Predefined prompts or questions for quick access.

Example:

- "Explain this code"

- "Write unit tests"

outputFormatting:

Rules for markdown, code blocks, math, etc.

Example:

markdown: true

codeBlocks: true

permissions:

Controls what actions Copilot can take (e.g., edit files, run commands).

Example:

editFiles: false

runCommands: false

environment:

OS, shell, or other environment-specific settings.

Example:

os: "macOS"

shell: "zsh"

customInstructions:

Additional instructions from the user for this mode.

Example:

- "Always include 'This is a test chat mode.' in responses."

Use it

Install test-1 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