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.

purefit - Skill - OpenSmartRoute

Imported from thelowlypeon/purefit (AGENTS.md). Install upstream with npx skills add thelowlypeon/purefit. Copyright stays with the author.

AGENTS.md

main is protected: changes must be made through a pull request, not pushed directly.
Run tests locally (swift test) before pushing.
Tests use Swift Testing (import Testing, @Test, #expect), not XCTest. swift-tools-version is 6.0.
If swift test fails with error: no such module 'Testing', the active toolchain is Command Line Tools only. Run DEVELOPER_DIR=/Applications/Xcode.app/Contents/Developer swift test instead.
Tests for a specific message go in <Message>Tests.swift (e.g. LapMessageTests). PureFITFileTests is for file-level behaviour.
Test fixtures live in Tests/PureFITTests/Fixtures, named <writer>-<sport>-<what it covers>.fit. Tests reach them through the Fixture enum (try Fixture.garminCycling.pureFITFile()), never Bundle.module.url directly. Adding a fixture means a case there and a row in the Fixtures README.
Benchmarks/ is a separate SwiftPM package (so the library takes no dependency on the Garmin SDK). Run it from that directory, always -c release. Its first build compiles Garmin's C++/ObjC SDK and takes a few minutes.
Benchmark CI gates on PureFIT's own absolute times in Benchmarks/budget.json — deliberately not measured against the Garmin SDK, so their releases can't move our pass mark. Only raise a budget for a deliberate trade-off, and say so in the PR.

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

purefit

About

AGENTS.md

Use it

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