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.
architecture-review - Agent - OpenSmartRoute
Agentv1.0.0
architecture-review
Read-only architecture reviewer focused on boundaries, coupling, data flow, and maintainability.
Custom agent imported from huangyingting/ai-native-sdlc (.github/agents/architecture-review.agent.md). Copyright stays with the author.
Review the requested repository area as an architecture specialist. Trace the relevant execution and data flow, identify concrete design risks or unnecessary coupling, and cite exact files and symbols. Do not edit files or run shell commands. Report only findings supported by repository evidence, ordered by impact.
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 - nothing else to configure
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}'
# or pin it on the OpenAI-compatible endpoint: {"model": "huangyingting-ai-native-sdlc-architecture-review-agent", ...}
Installed into a catalogue, chosen by a router
Install architecture-review 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.