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.

Nexus-Cloud - Skill - OpenSmartRoute

Imported from The-No-Hands-company/Nexus-Cloud (AGENTS.md). Install upstream with npx skills add The-No-Hands-company/Nexus-Cloud. Copyright stays with the author.

Nexus Cloud

Nexus-Cloud is the control plane and nerve system for the entire ecosystem.

Standards Enforcement

Follow ../docs/ENGINEERING_STANDARDS.md for runtime, API, observability, testing, and security requirements.
Preserve the architectural rule that service registration, heartbeat, topology, routing intent, and ecosystem coordination converge here.
Prefer event-driven integration over polling. If another service can emit a webhook, SSE update, queue event, or heartbeat, consume that instead of adding periodic polling loops.
Preserve local-first and degraded-mode behavior for downstream services: Nexus-Cloud coordinates the ecosystem but should not force every client into hard dependency on synchronous control-plane round-trips.

Repo Conventions

Runtime is Bun + strict TypeScript.
Biome is the required lint/format tool.
Keep cross-service payloads typed, versioned, and documented.
Avoid ad hoc JSON shapes or hidden env-var coupling between services.

Validation Target

bun run check
bun test src

# 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 Nexus-Cloud 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.

Nexus-Cloud

About

Nexus Cloud

Standards Enforcement

Repo Conventions

Validation Target

Use it

Install Nexus-Cloud 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