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.
Instruction file imported from wesleygruenberg/mvhs-swim-tracker (.github/instructions/meet_heat_sheet_lanes.instructions.md). Copyright stays with the author.
Reads a Lane Assignments sheet (use the provided CSV as the layout example).
Pulls entries from five Team tabs (CENT, MVHS, MER, EAGLE, TIMBER).
Builds a Relay Meet Heat Sheet (by event → by heat → lanes 1–5) and generates a nicely formatted Google Doc on demand via a custom menu.
Use the attached example heat sheet content to match semantics while improving formatting
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 slot
curl -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 meet_heat_sheet_lanes 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.
