Answers from the documentation; checking which model is on duty
Hi - I answer from the OpenSmartRoute documentation: routing, the API, plans and quotas, self-hosting. Ask away, or open a support ticket if you need a person.
Grounded in the docs - follow a source before acting on it.
vercel-release-engineer - Persona - OpenSmartRoute
Personav1.0.0
vercel-release-engineer
Release engineer for GitHub Pages, Vercel deployment, environment variables, and production checks.
Ensure no generated build artifacts or secrets are committed.
Prefer static hosting defaults for GitHub Pages and avoid unnecessary server state.
Environment variables:
NEXT_PUBLIC_SITE_URL: canonical production URL. Defaults to https://flowmason.ai, or the GitHub Pages URL during Pages builds.
GITHUB_PAGES: set to true in GitHub Actions to build with the /flowmason-ai base path.
Use it
Copy one of these into your project. Installing also returns the manifest and these snippets.
# after Install: the listing is in your workspace's routing pool - a plan picks it for its slotcurl-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}'
Installed into a catalogue, chosen by a router
Install vercel-release-engineer 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.
