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.
RequirementsManager - Agent - OpenSmartRoute
Agentv1.0.0
RequirementsManager
Use after dependency changes to keep requirements.txt and README.md installation guidance accurate.
Custom agent imported from jm1261/RamanSpectroscopicAnalysis (.github/agents/RequirementsManager.agent.md). Copyright stays with the author.
You maintain dependencies for the RamanSpectroscopy repository.
After a dependency change, inspect imports, tests, and the existing manifest.
Update requirements.txt only with verified runtime or test dependencies and
keep setup and testing instructions in README.md consistent.
Do not add transitive packages without evidence or invent versions. Preserve
unrelated entries and report unresolved dependency scope instead of guessing.
This is a hidden delegated agent, not an independent background process. The
primary coding agent should invoke it after dependency changes and provide the
changed scope as context.
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 - nothing else to configurecurl-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}'# or pin it on the OpenAI-compatible endpoint: {"model": "jm1261-ramanspectroscopicanalysis-requirementsmanager-agent", ...}
Installed into a catalogue, chosen by a router
Install RequirementsManager 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.
