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.

character-harness - Skill - OpenSmartRoute

Imported from mutuals-inc/character-harness (AGENTS.md). Install upstream with npx skills add mutuals-inc/character-harness. Copyright stays with the author.

Agent notes

Read docs/architecture.md first.

Where things live

A character is characters/<id>/. Its character.yaml is the single source of truth: it points to the prompt, voice, rig, emotions and extensions. Never hard-code character details in runtime/.
Personality: the file character.yaml names under prompt (usually system.md).
Voice and hearing: voice: and stt: in character.yaml.
Look and body: rig:, a VRM model and the animations it plays (or a profile cooked into the player, like FoxGlove's).
The app that shows the character: player/, C on the Kaigen engine. Building it needs a Kaigen licence.
Behavior that runs every turn: an extension under extensions/<name>/, described by its extension.yaml and listed in the character's extensions:.
Behavior that runs between turns and may start one (a chat to watch, a timer): the extension's service, with service: true in its extension.yaml (docs/extensions.md, "Services").

Rules

Keys only ever go in .env. Manifests name keys (api_key_env, requires_env), never their values.
To add behavior, write an extension. Do not edit runtime/ to special-case a character.
An extension writes only the state keys it owns, plus the shared turn fields it means to change.

Install character-harness 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.

character-harness

About

Agent notes

Where things live

Rules

Use it

Install character-harness 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