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.

core - Skill - OpenSmartRoute

Name: core
Author: InKCre

Imported from InKCre/impl-ts (packages/core/AGENTS.md). Install upstream with npx skills add InKCre/impl-ts --skill core. Copyright stays with the author.

@inkcre/core

Shared models, Peer protocols, storage/resolver mechanics, and native Extension Host contracts.

Owners

Package role and cross-package flows: ../../ARCHITECTURE.md.
Client runtime and delegation: ../../docs/30-unit-tdd/client-runtime-and-delegation.md.
Info-Base hydration, storage, Resolver outcomes, and browser handles: ../../docs/30-unit-tdd/info-base.md.
Native Extension Host and lifecycle: ../../docs/30-unit-tdd/native-extension-runtime.md.
Shared cross-unit contracts: ../../docs/_shared/20-product-tdd/.

Local Hazards

Keep one domain model and request/response authority. UI consumers import core contracts instead of reconstructing parallel shapes.
Keep Peer transport generic and capability managers domain-specific. Never retry ambiguous dispatch or silently substitute a different exact target.
Preserve exact, versioned Resolver IDs and the distinction between unknown, unsupported, supported-null, and authored-empty outcomes.
Treat storage content as opaque bytes/pointers; Resolver semantics and browser runtime handles remain separate.
database.generated.ts is generated from impl-py's admitted schema artifact; generated.ts and runtime-contract adapters are the stable local boundary. Do not hand-edit generated projections.
Keep runtime source and ESM distribution free of environment profiles, service origins, Peer identity, and credentials. Do not add CommonJS without a named consumer and explicit contract change.
Preserve Extension lifecycle compensation across initialize, activate, deactivate, and dispose.

Checks

pnpm --filter @inkcre/core type-check
pnpm --filter @inkcre/core build
pnpm lint:type-aware
pnpm type-check
pnpm check

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

core

About

@inkcre/core

Owners

Local Hazards

Checks

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