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.
detect_buildings - Skill - OpenSmartRoute
Skillv1.0.0
detect_buildings
Detect buildings in a map area using on-device vision
Imported from nimbusxr/custos (skills/custos.detect_buildings/SKILL.md). Install upstream with npx skills add nimbusxr/custos --skill custos.detect_buildings. Copyright stays with the author.
Building Detection
Detects buildings using the on-device vision model. Places BLD-N markers
at detected locations.
When detecting within a GRG, call grg_bounds first to get the exact
bounds, then pass north/south/east/west to detect_buildings. Do NOT
compute bounds yourself — always call grg_bounds for GRG-scoped detection.
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 detect_buildings 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.
