How long does the integration take?

Change one base URL in an OpenAI-compatible client, or install the Python or TypeScript SDK; the quickstart routes a first request in a few minutes.

Will this lock us into another vendor?

No. The router is Apache-2.0 open source, your provider keys stay yours, and the API is OpenAI-compatible, so leaving is a change of base URL.

What happens when a provider fails?

The router falls back to the next model your policy allows and records the fallback in the trace, so an outage costs a retry, not an incident.

microplanner - Skill - OpenSmartRoute

Imported from macorisd/microplanner (AGENTS.md). Install upstream with npx skills add macorisd/microplanner. Copyright stays with the author.

Repository conventions

Always spell the product name microplanner in lowercase in UI text, documentation, pull requests, and conversation. Use ordinary language naming conventions for identifiers that do not contain the product name.
Write repository content in English, including documentation, comments, user-facing text, commit messages, and pull request titles and bodies.
Use descriptive branch names such as feature/google-auth-mongodb or fix/session-restore. Branch names and pull request text, including hidden release metadata, must not mention the development methodology or its tools.
Before version 1.0.0, new features increment the minor version and bug fixes increment the patch version. Do not introduce a major version before the user explicitly decides the application is ready for 1.0.0.
Keep credentials in ignored local configuration. Never commit, print, or package database credentials, OAuth secrets, or session tokens.
Preserve user data when rebuilding or updating the application.

# after Install: the listing is in your workspace's routing pool - a plan picks it for its slot 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}'

Install microplanner 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.

microplanner

About

Repository conventions

Use it

Install microplanner and it becomes one more candidate the router can pick - when it fits.

What it costs to adopt - in engineering time.

One base URL

No vendor lock-in

Failover built in

Manifest

Reviews