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.

Check Project - Prompt - OpenSmartRoute

Name: Check Project
Author: KrasherPlay

Prompt file imported from KrasherPlay/maksym_tupis_ki_2023_lpnu_ua (.github/prompts/check.prompt.md). Fill in {{projectRoot}}, {{mavenGoal}} before use. Copyright stays with the author.

Perform final verification for {{projectRoot}}.

Procedure

Inspect git status --short and list the files changed by this workflow.
Verify expected Maven paths, pom.xml, JUnit 5 test sources, Maven wrapper, and .github/workflows.
Run mvn validate and {{mavenGoal}} using the wrapper when available.
Confirm test reports exist and tests were not skipped.
Review GitHub Actions YAML for Windows, Linux, and macOS matrix entries, correct wrapper commands, minimal permissions, and absence of secrets.
Report a PASS only if every check succeeds.

Success criteria

Structure, Maven validation, tests, packaging/verification, and CI configuration are all valid.
No files were deleted and no unrelated changes were introduced.
The final report lists commands, results, changed files, and any warnings.

Failure handling

On the first failed check, stop the verification sequence, report the exact failure and remediation, and return FAIL. Do not claim success based on partial checks.

Perform final verification for `{{projectRoot}}`. ## Procedure 1. Inspect `git status --short` and list the files changed by this workflow. 2. Verify expected Maven paths, `pom.xml`, JUnit 5 test sources, Maven wrapper, and `.github/workflows`. 3. Run `mvn validate` and `{{mavenGoal}}` using the wrapper when available. 4. Confirm test reports exist and tests were not skipped. 5. Review GitHub Actions YAML for Windows, Linux, and macOS matrix entries, correct wrapper commands, minimal permissions, and absence of secrets. 6. Report a PASS only if every check succeeds. ## Success criteria - Structure, Maven validation, tests, packaging/verification, and CI configuration are all valid. - No files were deleted and no unrelated changes were introduced. - The final report lists commands, results, changed files, and any warnings. ## Failure handling On the first failed check, stop the verification sequence, report the exact failure and remediation, and return `FAIL`. Do not claim success based on partial checks.

Install Check Project 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": "Perform final verification for `{{projectRoot}}`.\n\n## Procedure\n\n1. Inspect `git status --short` and list the files changed by this workflow.\n2. Verify expected Maven paths, `pom.xml`, JUnit 5 test sources, Maven wrapper, and `.github/workflows`.\n3. Run `mvn validate` and `{{mavenGoal}}` using the wrapper when available.\n4. Confirm test reports exist and tests were not skipped.\n5. Review GitHub Actions YAML for Windows, Linux, and macOS matrix entries, correct wrapper commands, minimal permissions, and absence of secrets.\n6. Report a PASS only if every check succeeds.\n\n## Success criteria\n\n- Structure, Maven validation, tests, packaging/verification, and CI configuration are all valid.\n- No files were deleted and no unrelated changes were introduced.\n- The final report lists commands, results, changed files, and any warnings.\n\n## Failure handling\n\nOn the first failed check, stop the verification sequence, report the exact failure and remediation, and return `FAIL`. Do not claim success based on partial checks.", "variables": [ "projectRoot", "mavenGoal" ], "notes": "Run final structural, Maven, test, and CI configuration checks for a Java project. Tools: read, search, execute. Arguments: Provide the project root and Maven verification goal..", "metadata": { "source": { "provider": "github-prompts", "repository": "https://github.com/KrasherPlay/maksym_tupis_ki_2023_lpnu_ua", "path": ".github/prompts/check.prompt.md", "ref": "9930e2dbe9314c10d695cf600ad9eaa4caa1b7c9", "url": "https://github.com/KrasherPlay/maksym_tupis_ki_2023_lpnu_ua/blob/9930e2dbe9314c10d695cf600ad9eaa4caa1b7c9/.github/prompts/check.prompt.md", "key": "KrasherPlay/maksym_tupis_ki_2023_lpnu_ua/.github/prompts/check.prompt.md" } } }

Check Project

About

Procedure

Success criteria

Failure handling

Use it

Install Check Project 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