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.
HireHeat Jobs: Career Site Job Listings from 12,000+ Companies - Tool - OpenSmartRoute
Toolv1.0.0
HireHeat Jobs: Career Site Job Listings from 12,000+ Companies
HireHeat Jobs: search jobs on 12,000+ company career sites (Greenhouse, Ashby, Workable…).
Imported from the official MCP registry - entry io.github.CyberMax-tools/career-site-jobs v1.0.0. Ratings and installs below are from this marketplace.
HireHeat Jobs: Career Site Job Listings from 12,000+ Companies
HireHeat Jobs: search jobs on 12,000+ company career sites (Greenhouse, Ashby, Workable…).
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://osr-api.kindrock-caaab1a2.centralindia.azurecontainerapps.io/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": "mcp-io-github-cybermax-tools-career-site-jobs", ...}
Installed into a catalogue, chosen by a router
Install HireHeat Jobs: Career Site Job Listings from 12,000+ Companies 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.
