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.

qkrpc - Skill - OpenSmartRoute

Name: qkrpc
Author: QuickerHub

Instruction file imported from QuickerHub/quicker-rpc (.cursor/rules/qkrpc.mdc). Copyright stays with the author.

qkrpc agent rules

Canonical file — copied to workspace .cursor/rules/ via scripts/Sync-QkrpcAgentRules.ps1 and to Cursor plugin via qkrpc agent setup --cursor-plugin.

Scope gate

Apply this rule only when:

the user is editing Quicker actions / subprograms, or
files under the qkrpc disk root (.quicker/), or
you are calling qkrpc_* MCP / qkrpc CLI for authoring

Do not treat QuickerOrg/Quicker (or other product repos) as QKRPC_WORKSPACE_ROOT. Disk edits belong in the configured workspace (usually quicker-workspace). Prefer project .cursor/mcp.json over a user-global Cursor plugin.

Before editing

docs action=get topic overview, then authoring-workflow
Subprograms: subprogram-workflow
Disk layout: docs topic workspace-editing or MCP resource quicker://workspace/readme

Task routing

Goal	MCP (preferred)	CLI (`--json`)
Local edit action / global subprogram	`qkrpc_action_get` / `qkrpc_subprogram_get` → edit `.quicker/` → `workspace_program` `action=patch`	`action get` / `subprogram get` → edit → `apply`
Remote publish action (动作库)	—	`action publish` / `action update` (`--changelog` on update)
Remote publish subprogram (子程序库)	—	`subprogram publish` / `subprogram update` (`--changelog` on update)
Run / debug with step output	`qkrpc_action` `mode=debug`	`action run --trace`

Never action publish / action update for subprograms (wrong API). Never guess inputs without step-runner get.

data.json wire (write): short names only — key / inputs / outputs. Never stepKey. Legacy long names are read-compatible only. Domain topics (form-spec, icons, context-menu) stay in docs — do not invent formDef without form-spec.

MCP output (compact)

MCP tools return flat compact JSON — not { ok, data: { action, payload } }. Fields like actionId, editVersion, compressed sit at the top level. workspaceSync is only { ok, projectDir, editVersion }; read files from disk under projectDir. Verbose legacy: QKRPC_MCP_VERBOSE=1. See tools/qkrpc/docs/mcp-output-contract.md.

Hard rules

Disk edit: get → host file tools → patch; no inline patch JSON; deprecated qkrpc_sync
After patch: trust editVersion; no verify re-get
Connectivity: qkrpc_wait on failure — no repeated shell ping/probe
Prefer MCP qkrpc_* when configured; else shell qkrpc CLI
Remote library upload: ask user first; subprogram update requires --changelog
Destructive: qkrpc_action_delete, qkrpc_subprogram_delete need user confirmation

Scope

Cursor MCP: headless authoring (workspace_program, step-runner, run/debug). QuickerAgent or Quicker Designer: visual editor, embedded browser, shell automation.

quicker-workspace

Disk root: repo .quicker/ (QKRPC_WORKSPACE_ROOT = workspace root)
Human/agent map: workspace root docs/qkrpc-agent-usage.md
Developing tools/qkrpc/: after changes run build.ps1 -t (plugin reload + CLI install to user PATH); -SkipInstall only when user asks
Stuck: skill quicker-rpc-knowledge (tools/qkrpc/docs/skills/quicker-rpc-knowledge/)

Install qkrpc 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.

{ "ocm": "1", "id": "quickerhub-quicker-rpc-qkrpc-rule", "kind": "skill", "name": "qkrpc", "description": "Quicker/qkrpc headless authoring. Use only when editing Quicker actions/subprograms, .quicker/, or calling qkrpc MCP. Do not apply in QuickerOrg/Quicker app source or unrelated repos.", "publisher": "QuickerHub", "version": "1.0.0", "capabilities": { "domains": [ "coding", "observability" ], "tags": [ "skill-md", "github-cursor-rules" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "Quicker/qkrpc headless authoring. Use only when editing Quicker actions/subprograms, .quicker/, or calling qkrpc MCP. Do not apply in QuickerOrg/Quicker app source or unrelated repos." ], "primary": false, "metadata": { "source": { "provider": "github-cursor-rules", "repository": "https://github.com/QuickerHub/quicker-rpc", "path": ".cursor/rules/qkrpc.mdc", "ref": "cc3e5eef59a381b2124a09d0dbff273c291a9c6c", "url": "https://github.com/QuickerHub/quicker-rpc/blob/cc3e5eef59a381b2124a09d0dbff273c291a9c6c/.cursor/rules/qkrpc.mdc", "key": "QuickerHub/quicker-rpc/.cursor/rules/qkrpc.mdc" } }, "instructions": "# qkrpc agent rules\n\n**Canonical file** — copied to workspace `.cursor/rules/` via `scripts/Sync-QkrpcAgentRules.ps1` and to Cursor plugin via `qkrpc agent setup --cursor-plugin`.\n\n## Scope gate\n\nApply this rule **only** when:\n\n- the user is editing Quicker **actions / subprograms**, or\n- files under the qkrpc disk root (`.quicker/`), or\n- you are calling `qkrpc_*` MCP / `qkrpc` CLI for authoring\n\n**Do not** treat QuickerOrg/Quicker (or other product repos) as `QKRPC_WORKSPACE_ROOT`. Disk edits belong in the configured workspace (usually `quicker-workspace`). Prefer project `.cursor/mcp.json` ", "cost": { "context_tokens": 924 } }

qkrpc

About

qkrpc agent rules

Scope gate

Before editing

Task routing

MCP output (compact)

Hard rules

Scope

quicker-workspace

Install qkrpc 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

Use it

Manifest

Reviews