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.

requesto.mbt - Skill - OpenSmartRoute

Name: requesto.mbt
Author: gaato

Imported from gaato/requesto.mbt (AGENTS.md). Install upstream with npx skills add gaato/requesto.mbt. Copyright stays with the author.

Agent notes for gaato/requesto

Documentation

README.md is a symbolic link to src/overview.mbt.md, and mooncakes.io renders it as the module page. Write it for visitors: what the module is, how to install and use it, and what a caller must know (limits, errors, retries). Keep design rationale, internal mechanics, test procedures and facts that go stale (version pins, "since 0.x") out of it; they belong in RESOURCE_BOUNDS.md, TEST_COVERAGE.md, .notes/ or the changelog, because a visitor reads the page to decide whether and how to use the module.
Keep its examples in mbt check fences: the file compiles with the package's tests, so a stale example fails moon check instead of misleading a reader.
Run moon run scripts/docs_audit.mbtx --self-test (also run by scripts/gates.sh and CI) after changing docs or public declarations.
scripts/docs_audit.mbtx is identical in every gaato MoonBit repository. Copy it from gaato/discord.mbt rather than editing it here, so the repos do not drift; put repository differences in scripts/docs_audit.json and scripts/docs_audit.allow.
.moonignore lists what the package leaves out. A new repository-only file at the top level needs a line there, or it is published with the module.

# 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 requesto.mbt 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.

requesto.mbt

About

Agent notes for gaato/requesto

Documentation

Use it

Install requesto.mbt 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