Pi TypeSafe Router — npmjs.com

Choose a real provider and model in Pi first, then run /typesafe-router setup typesafe (or cloudflare, vercel, openrouter). That creates ~/.pi/agent/typesafe-router.json, initially off, using your selected model for all three routes; edit the mappings, set the key, and /reload.

It tests the classifier and configured models with synthetic requests, without sending your conversation, using tools, or changing the selected model. The README notes these checks may incur charges.

TypeSafe with TYPESAFE_API_KEY and model jev-1.13.0; Cloudflare AI Gateway with CLOUDFLARE_API_TOKEN plus account and gateway IDs; Vercel AI Gateway with AI_GATEWAY_API_KEY and typesafe-ai/jev; OpenRouter with OPENROUTER_API_KEY and typesafe/jev-1.13.

Run /typesafe-router doctor to verify the configuration, then /typesafe-router on to enable routing. The help subcommand prints a table explaining every command.

No. Setup creates the config file initially off, mapping all three routes to your selected model. You edit the mappings, set TYPESAFE_API_KEY in the environment that launches Pi, and run /reload before enabling.

Yes. npm run check runs offline tests, lint, formatting, and typechecking, and the tests directory uses a synthetic transport, policy, lifecycle, and real Pi SDK tests with no paid API calls. Live E2E needs the five credentials and TYPESAFE_ROUTER_LIVE_E2E=1.

src/classifier.ts holds transport adapters and response validation; config.ts, context.ts, and routing.ts hold the schema, bounded text projection, and deterministic policy; index.ts and settings.ts hold Pi lifecycle and commands; infra/github holds Pulumi-managed repository settings and docs record ADRs.