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.
nextjs-core - Skill - OpenSmartRoute
Skillv1.0.0
nextjs-core
Core Next.js patterns for App Router development including Server Components, Server Actions, route handlers, data fetching, and caching strategies
Imported from bobmatnyc/claude-mpm-skills (toolchains/nextjs/nextjs-core/SKILL.md). Install upstream with npx skills add bobmatnyc/claude-mpm-skills --skill nextjs-core. Copyright stays with the author.
Next.js Core (App Router)
Server Components by default; minimal "use client".
Mutations in Server Actions (validate/authz; revalidate tags/paths).
Route handlers for APIs/webhooks; add loading/error boundaries.
Anti-patterns:
❌ Fetch initial data in useEffect.
❌ Cache or revalidate too broadly.
❌ Client-only authz.
References: see references/ (server actions, fetching, caching, routing, auth, testing).
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 nextjs-core 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.
