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.
swe-architect - Agent - OpenSmartRoute
Agentv1.0.0
swe-architect
Designs module boundaries, dependencies, and tradeoffs before implementation, judges finished work against that design, and serves as the architecture lens of a review pass, writing nothing but…
Claude Code subagent imported from wahidyankf/grind-in-public (.claude/agents/swe-architect.md). Copyright stays with the author.
Before acting, read the complete canonical agent definition at the repository-root path
.agents/agents/swe-architect.md
and follow it as authoritative. If it cannot be read, stop and report the missing path.
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 configurecurl-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": "wahidyankf-grind-in-public-swe-architect-subagent", ...}
Installed into a catalogue, chosen by a router
Install swe-architect 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.