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

mem-search - Skill - OpenSmartRoute

Skillv1.0.0

mem-search

Name: mem-search
Author: thedotmack

Use this when the user asks to search memory, "did we already solve this?", "how did we do X last time?", or wants work from previous sessions.

by thedotmack(0) 0 installs

Free

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

See reviews

About

Imported from thedotmack/claude-mem (claude-mem-cursor/skills/mem-search/SKILL.md) via skills.sh. Install upstream with npx skills add thedotmack/claude-mem --skill mem-search. Copyright stays with the author.

mem-search

Layered workflow. Do not dump full observations until IDs are filtered, and do not reach for raw tool bodies until the summaries came up short.

search(query) — index with IDs
timeline(anchor=ID) — nearby context
get_observations(ids=[...]) — full details for those IDs only
get_tool_uses(ids=[...]) — the ORIGINAL tool_input / tool_response for specific tool calls. Last resort: these are unsummarized and can run to thousands of tokens each.

Stamp platformSource as cursor or grok-bot on writes for this host. When reading, do not drop the other host unless asked.

If MCP is missing, run the install skill first (npx claude-mem install --ide <host>).

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 slot
curl -s -X POST https://osr-api.kindrock-caaab1a2.centralindia.azurecontainerapps.io/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 mem-search 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.

Manifest

An Open Capability Manifest: the router reads it to know what this does, what it costs and when to pick it.

thedotmack-claude-mem-mem-search.ocm.jsonjson

{
  "ocm": "1",
  "id": "thedotmack-claude-mem-mem-search",
  "kind": "skill",
  "name": "mem-search",
  "description": "Use this when the user asks to search memory, \"did we already solve this?\", \"how did we do X last time?\", or wants work from previous sessions.",
  "publisher": "thedotmack",
  "version": "1.0.0",
  "capabilities": {
    "domains": [
      "data_analysis"
    ],
    "tags": [
      "skill-md",
      "skills-sh"
    ],
    "languages": [
      "en"
    ]
  },
  "quality_prior": 0.6,
  "examples": [
    "Use this when the user asks to search memory, \"did we already solve this?\", \"how did we do X last time?\", or wants work from previous sessions."
  ],
  "primary": false,
  "metadata": {
    "source": {
      "provider": "skills.sh",
      "repository": "https://github.com/thedotmack/claude-mem",
      "path": "claude-mem-cursor/skills/mem-search/SKILL.md",
      "ref": "HEAD",
      "url": "https://www.skills.sh/thedotmack/claude-mem/mem-search",
      "key": "thedotmack/claude-mem/claude-mem-cursor/skills/mem-search/SKILL.md"
    }
  },
  "instructions": "# mem-search\n\nLayered workflow. Do not dump full observations until IDs are filtered, and do not reach for raw tool bodies until the summaries came up short.\n\n1. `search(query)` — index with IDs\n2. `timeline(anchor=ID)` — nearby context\n3. `get_observations(ids=[...])` — full details for those IDs only\n4. `get_tool_uses(ids=[...])` — the ORIGINAL `tool_input` / `tool_response` for specific tool calls. Last resort: these are unsummarized and can run to thousands of tokens each.\n\nStamp `platformSource` as `cursor` or `grok-bot` on writes for this host. When reading, do not drop the other host un",
  "cost": {
    "context_tokens": 175
  }
}

Fetch it by URL: GET /api/v1/registry/thedotmack-claude-mem-mem-search/manifest?version=1.0.0

About

mem-search

Use it

Install mem-search 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