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.

90 days of the enterprise, pro and team plans free, no card needed. See the plans

OpenSmartRoute

nex:notify - Prompt - OpenSmartRoute

Promptv1.0.0

nex:notify

Name: nex:notify
Author: najmuzzaman-mohammad

View and manage Nex notifications, preferences, and custom notification rules

by najmuzzaman-mohammad(0) 0 installs

Free

Free account. Installing gives you the manifest plus copy-paste snippets.

See reviews

About

Prompt file imported from najmuzzaman-mohammad/gawkbot (.windsurf/workflows/nex-notify.md). Copyright stays with the author.

Use the Nex MCP tools to manage notifications based on the user's request.

For viewing notifications: use nex_get_notifications to list recent notifications. For preferences: use nex_get_notification_preferences to view or nex_set_notification_preferences to update (frequency, enabled types, digest toggle). For custom rules: use nex_create_notification_rule to create, nex_list_notification_rules to list, or nex_delete_notification_rule to remove.

Present notifications clearly, highlighting type, importance, and content.

Use it

Copy one of these into your project. Installing also returns the manifest and these snippets.

Use the Nex MCP tools to manage notifications based on the user's request.

For viewing notifications: use `nex_get_notifications` to list recent notifications.
For preferences: use `nex_get_notification_preferences` to view or `nex_set_notification_preferences` to update (frequency, enabled types, digest toggle).
For custom rules: use `nex_create_notification_rule` to create, `nex_list_notification_rules` to list, or `nex_delete_notification_rule` to remove.

Present notifications clearly, highlighting type, importance, and content.

Installed into a catalogue, chosen by a router

Install nex:notify 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.

Photo: RDNE Stock project

For the business

What it costs to adopt - in engineering time.

Same client, same code
One base URL
The OpenAI-compatible endpoint answers your existing SDK calls; model=auto lets the router choose.
The SDKs
One URL, every vendor
No vendor lock-in
Point your OpenAI-compatible client at one address; add, swap or retire providers in the catalogue without touching application code.
Every vendor side by side
Next eligible model answers
Failover built in
When a provider is down or over quota the request moves on; the trace says it did.

najmuzzaman-mohammad-gawkbot-nex-notify-workflow.prompt.jsonjson

{
  "prompt": "Use the Nex MCP tools to manage notifications based on the user's request.\n\nFor viewing notifications: use `nex_get_notifications` to list recent notifications.\nFor preferences: use `nex_get_notification_preferences` to view or `nex_set_notification_preferences` to update (frequency, enabled types, digest toggle).\nFor custom rules: use `nex_create_notification_rule` to create, `nex_list_notification_rules` to list, or `nex_delete_notification_rule` to remove.\n\nPresent notifications clearly, highlighting type, importance, and content.",
  "variables": [],
  "notes": "View and manage Nex notifications, preferences, and custom notification rules",
  "metadata": {
    "source": {
      "provider": "github-windsurf-workflows",
      "repository": "https://github.com/najmuzzaman-mohammad/gawkbot",
      "path": ".windsurf/workflows/nex-notify.md",
      "ref": "f68d7086ed02a54db2023ae44253abf5d6f94a71",
      "url": "https://github.com/najmuzzaman-mohammad/gawkbot/blob/f68d7086ed02a54db2023ae44253abf5d6f94a71/.windsurf/workflows/nex-notify.md",
      "key": "najmuzzaman-mohammad/gawkbot/.windsurf/workflows/nex-notify.md"
    }
  }
}

Fetch it by URL: GET /api/v1/registry/najmuzzaman-mohammad-gawkbot-nex-notify-workflow/manifest?version=1.0.0

nex:notify

About

Use it

Install nex:notify 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