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

agentlas-graph - Prompt - OpenSmartRoute

Promptv1.0.0

agentlas-graph

Name: agentlas-graph
Author: agentlas-ai

Build an Agentlas automation by describing it, list saved ones, or request a run.

by agentlas-ai(0) 0 installs

Free

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

See reviews

About

Prompt file imported from agentlas-ai/Agentlas-OS (.claude/commands/agentlas-graph.md). Copyright stays with the author.

/agentlas-graph

Identical to /hep-graph and /agentlas graph <request>. Locate the file named hep-graph.md in the exact same directory this file was loaded from, read it, and follow its instructions exactly — treating everything typed after /agentlas-graph as that command's request.

Do not improvise a separate workflow and do not summarize hep-graph.md from memory; that file is the sole authority for this command's behavior.

Use it

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

# /agentlas-graph

Identical to `/hep-graph` and `/agentlas graph <request>`. Locate the file named `hep-graph.md` in the exact same directory this file was loaded from, read it, and follow its instructions exactly — treating everything typed after `/agentlas-graph` as that command's request.

Do not improvise a separate workflow and do not summarize `hep-graph.md` from memory; that file is the sole authority for this command's behavior.

Manifest

The prompt text and its fill-in variables. Copy it or fetch it by URL from your own code.

Installed into a catalogue, chosen by a router

Install agentlas-graph 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.

agentlas-ai-agentlas-os-agentlas-graph-command.prompt.jsonjson

{
  "prompt": "# /agentlas-graph\n\nIdentical to `/hep-graph` and `/agentlas graph <request>`. Locate the file named `hep-graph.md` in the exact same directory this file was loaded from, read it, and follow its instructions exactly — treating everything typed after `/agentlas-graph` as that command's request.\n\nDo not improvise a separate workflow and do not summarize `hep-graph.md` from memory; that file is the sole authority for this command's behavior.",
  "variables": [],
  "notes": "Build an Agentlas automation by describing it, list saved ones, or request a run. Tools: Bash, Read. Arguments: [new <what you want> | list | show <name> | run <name>].",
  "metadata": {
    "source": {
      "provider": "github-claude-commands",
      "repository": "https://github.com/agentlas-ai/Agentlas-OS",
      "path": ".claude/commands/agentlas-graph.md",
      "ref": "c0acd99be22114569e20bca94bed4540ba046eb4",
      "url": "https://github.com/agentlas-ai/Agentlas-OS/blob/c0acd99be22114569e20bca94bed4540ba046eb4/.claude/commands/agentlas-graph.md",
      "key": "agentlas-ai/Agentlas-OS/.claude/commands/agentlas-graph.md"
    }
  }
}

Fetch it by URL: GET /api/v1/registry/agentlas-ai-agentlas-os-agentlas-graph-command/manifest?version=1.0.0

About

/agentlas-graph

Use it

Manifest

Install agentlas-graph 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

Reviews