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.
event-dispatcher - Skill - OpenSmartRoute
Skillv1.0.0
event-dispatcher
This repository owns fast-forward/event-dispatcher. Read Composer metadata, source and tests before changing public integration. Preserve unrelated work.
Imported from php-fast-forward/event-dispatcher (AGENTS.md). Install upstream with npx skills add php-fast-forward/event-dispatcher. Copyright stays with the author.
fast-forward-event-dispatcher maintenance
This repository owns fast-forward/event-dispatcher. Read Composer metadata, source and
tests before changing public integration. Preserve unrelated work. Run
composer install, composer validate --strict and composer dev-tools.
Keep merge, release and deployment decisions with the maintainer. Ordinary
source/resources share this root contract; consumer procedures live in SKILL.md.
Bundled consumer skill
Read the consumer skill when changing application integration
examples, consumer guides or the skill. Keep its version contract, references
and executable examples aligned with the supported public API. The canonical
distributable source is resources/skills; it needs no installed copy or host
alias. Repository maintenance continues to follow this AGENTS.md.
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 event-dispatcher 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.
