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.

vxrt-playtest - Prompt - OpenSmartRoute

Name: vxrt-playtest
Author: Ag3497120

Prompt file imported from Ag3497120/VeRantyx (.cursor/commands/vxrt-playtest.md). Copyright stays with the author.

Help the user playtest <the game named after the command> on VXRuntime, then turn what went wrong into the next work.

If no game was named, list the installed games (vxrt MCP list_games) and ask which one; stop until the user answers.
A playtest is the user's: they run it in their own Terminal, with the headset on and their controllers: python3 tools/vxrt_playtest.py <game> (the quality tuned for this Mac is used if there is one). Tell them: click both sticks together for about a second where something goes wrong (or press Enter in the Terminal, with a note); quit the game or press Ctrl-C to end; then answer the checklist. Do not start it yourself, and do not run other games meanwhile.
When they are done, read it: vxrt MCP read_playtests (or python3 tools/vxrt_playtest.py --show <game>, and runs/<id>/playtest.json). Look at every problem: each mark's frame (runs/<id>/mark_N.png) and the game's log at that moment, the "no" answers, crashes, slow stretches, lost tracking.
Report: playable or not (which condition failed), and the problems in the order they happened, each with what you think it is (say when it is only a suspicion). Offer /vxrt-support <game> for the ones in VXRuntime, /vxrt-tune <game> for slow stretches, and python3 tools/vxrt_playtest.py --apply runs/<id> (the user's choice) to record it in the game's profile.
Talk to the user in their language.

Help the user playtest `<the game named after the command>` on VXRuntime, then turn what went wrong into the next work. 1. If no game was named, list the installed games (vxrt MCP `list_games`) and ask which one; stop until the user answers. 2. A playtest is the user's: they run it in their own Terminal, with the headset on and their controllers: `python3 tools/vxrt_playtest.py <game>` (the quality tuned for this Mac is used if there is one). Tell them: click both sticks together for about a second where something goes wrong (or press Enter in the Terminal, with a note); quit the game or press Ctrl-C to end; then answer the checklist. Do not start it yourself, and do not run other games meanwhile. 3. When they are done, read it: vxrt MCP `read_playtests` (or `python3 tools/vxrt_playtest.py --show <game>`, and `runs/<id>/playtest.json`). Look at every problem: each mark's frame (`runs/<id>/mark_N.png`) and the game's log at that moment, the "no" answers, crashes, slow stretches, lost tracking. 4. Report: playable or not (which condition failed), and the problems in the order they happened, each with what you think it is (say when it is only a suspicion). Offer `/vxrt-support <game>` for the ones in VXRuntime, `/vxrt-tune <game>` for slow stretches, and `python3 tools/vxrt_playtest.py --apply runs/<id>` (the user's choice) to record it in the game's profile. 5. Talk to the user in their language.

Install vxrt-playtest 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.

{ "prompt": "\nHelp the user playtest `<the game named after the command>` on VXRuntime, then turn what went wrong into the next work.\n\n1. If no game was named, list the installed games (vxrt MCP `list_games`) and ask which one; stop until the user answers.\n2. A playtest is the user's: they run it in their own Terminal, with the headset on and their controllers: `python3 tools/vxrt_playtest.py <game>` (the quality tuned for this Mac is used if there is one). Tell them: click both sticks together for about a second where something goes wrong (or press Enter in the Terminal, with a note); quit the game or press Ctrl-C to end; then answer the checklist. Do not start it yourself, and do not run other games meanwhile.\n3. When they are done, read it: vxrt MCP `read_playtests` (or `python3 tools/vxrt_playtest.py --show <game>`, and `runs/<id>/playtest.json`). Look at every problem: each mark's frame (`runs/<id>/mark_N.png`) and the game's log at that moment, the \"no\" answers, crashes, slow stretches, lost tracking.\n4. Report: playable or not (which condition failed), and the problems in the order they happened, each with what you think it is (say when it is only a suspicion). Offer `/vxrt-support <game>` for the ones in VXRuntime, `/vxrt-tune <game>` for slow stretches, and `python3 tools/vxrt_playtest.py --apply runs/<id>` (the user's choice) to record it in the game's profile.\n5. Talk to the user in their language.", "variables": [], "notes": "1. If no game was named, list the installed games (vxrt MCP `list_games`) and ask which one; stop until the user answers. 2. A playtest is the user's: they run it in their own Terminal, with the headset on and their controllers: `python3 tools/vxrt_playtest.py <game>` (the quality tuned for this Mac is used if there is one). Tell them: click both sticks together for about a second where something goes wrong (or press Enter in the Terminal, with a note); quit the game or press Ctrl-C to end; then answer the checklist. Do not start it yourself, and do not run other games meanwhile. 3. When they are done, read it: vxrt MCP `read_playtests` (or `python3 tools/vxrt_playtest.py --show <game>`, and `runs/<id>/playtest.json`). Look at every problem: each mark's frame (`runs/<id>/mark_N.png`) and the game's log at that moment, the \"no\" answers, crashes, slow stretches, lost tracking. 4. Report: playable or not (which condition failed), and the problems in the order they happened, each with what you think it is (say wh", "metadata": { "source": { "provider": "github-cursor-commands", "repository": "https://github.com/Ag3497120/VeRantyx", "path": ".cursor/commands/vxrt-playtest.md", "ref": "719fe61f224483f041b6451b25e6f93a43cb74ff", "url": "https://github.com/Ag3497120/VeRantyx/blob/719fe61f224483f041b6451b25e6f93a43cb74ff/.cursor/commands/vxrt-playtest.md", "key": "Ag3497120/VeRantyx/.cursor/commands/vxrt-playtest.md" } } }

vxrt-playtest

About

Use it

Install vxrt-playtest 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