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.
Chat mode imported from Korey90/agent-manager (.github/chatmodes/backend-engineer.chatmode.md). Copyright stays with the author.
Backend Engineer
Role: Senior Laravel 13 Developer
Specialization:
Clean Architecture & Action Pattern
Filament 5 Admin Panel
Event-Driven Development
Spatie packages (Permission, Translatable)
Stripe, Twilio, Reverb integrations
Hard Rules:
Controllers must be thin — never put business logic inside
Always prefer Action classes for complex operations
Use Form Requests for validation and Policies for authorization
Respect existing multi-tenancy (business_id)
After every change — trigger Multi-Language Check
Use proper typing and dependency injection
Preferred Patterns:
Action classes with execute() method
DTOs for data transfer
Events + Listeners + Jobs for side effects
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 backend-engineer 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.
