[DennyHo0917]

Summary

Add an optional API Route memory provider preset using the existing OpenAI Chat Completions transport, following the merged Cheaper Inference preset (#420). I am affiliated with API Route.

• Endpoint/model defaults, API_ROUTE_API_KEY fallback, explicit env:// key configuration, and a distinct session tag.
• Factory, configuration validation, readiness detection, example/template, and all README languages updated.
• Tests cover authentication, request serialization, tool response extraction, overrides, environment-key resolution, and rejection of remote-provider changes from project configuration.
• No defaults change for existing users. Users opt in with their own key; documentation describes the destination for conversation data.

Test plan

• Exercised locally: real gpt-6.1-sol call through APIRouteProvider.executeToolCall successfully returned save_memories tool data.
• Known limitation documented: full bun test reports 842 passed, 6 skipped, 1 failed. The failure is the unchanged ONNX nested-layout fixture at tests/onnxruntime-resolve.test.ts:177, where Windows denies directory symlink creation (EPERM). All provider/configuration cases pass.

Checklist

• Branch based on main.
• Entire bun test passes (Windows symlink limitation above).
• bun run typecheck passes (included in check).
• bun run check passes (format, lint, typecheck).
• bun run build passes after installing the separate web dependencies.
• README / example configuration updated.

[EyJunge1]

Review follow-up

Pushed cf796b6 onto this branch (maintainer edit):

• Synced the translated READMEs so forceToolChoice troubleshooting also lists api-route (English README already had it).
• Fixed factory test wording: “creates an API Route provider”.
• Minor blank-line consistency in config-resolution tests.

Review verdict

The preset wiring matches the Cheaper Inference pattern (#420): factory, config validation, env-key fallback (API_ROUTE_API_KEY), readiness, session tag, docs/example, and tests look complete. Endpoint https://global.api-route.com/v1 responds as an OpenAI-compatible API (auth required). No functional blockers found beyond the doc/test nits above.