Skip to content

feat(providers): add Token Kiosk as an OpenAI-compatible provider - #10722

Merged
diegosouzapw merged 3 commits into
diegosouzapw:release/v3.8.50from
hgaib:feat/add-token-kiosk-provider
Aug 20, 2026
Merged

diegosouzapw merged 3 commits into
diegosouzapw:release/v3.8.50from
hgaib:feat/add-token-kiosk-provider

Conversation

@hgaib

@hgaib hgaib commented Aug 19, 2026 •

Copy link
Copy Markdown
Contributor

Summary

Adds Token Kiosk (https://agent-router.gaib.ai/v1) as a standard named OpenAI-style gateway provider in OmniRoute.

  • Registers token-kiosk (tk) in APIKEY_PROVIDERS and PROVIDER_ENDPOINTS
  • Adds modular provider registry entry under open-sse/config/providers/registry/token-kiosk/
  • Adds token-kiosk to NAMED_OPENAI_STYLE_PROVIDERS for live /v1/models discovery
  • Updates PROVIDER_REFERENCE.md and adds unit test tests/unit/token-kiosk-provider.test.ts

Verification

  • Unit test added verifying provider registration, base URL, format, and discovery set inclusion.

@hgaib
hgaib requested a review from diegosouzapw as a code owner August 19, 2026 06:54
@hgaib
hgaib force-pushed the feat/add-token-kiosk-provider branch from 6a5bce1 to bd27a8c Compare August 19, 2026 09:01
@hgaib
hgaib changed the base branch from main to release/v3.8.50 August 19, 2026 09:01
@hgaib hgaib changed the title feat(providers): add GAIB Token Kiosk as an OpenAI-compatible provider feat(providers): add Token Kiosk as an OpenAI-compatible provider Aug 19, 2026
…adge

Restore tokenrouter's authHint to its original wording (the change was
out of scope for this PR) and give token-kiosk its own textIcon (TKI)
to avoid a badge-fallback collision with the existing tokenrouter (TK)
entry.

Co-authored-by: hgaib <208897539+hgaib@users.noreply.github.com>
diegosouzapw added a commit that referenced this pull request Aug 20, 2026
…10797) + pre-existing chatBodyAdmission.ts drift

Co-authored-by: diegosouzapw <8016841+diegosouzapw@users.noreply.github.com>
giauphan pushed a commit to giauphan/OmniRoute that referenced this pull request Aug 20, 2026
…zapw#10722, diegosouzapw#10797) + pre-existing chatBodyAdmission.ts drift

Co-authored-by: diegosouzapw <8016841+diegosouzapw@users.noreply.github.com>
@diegosouzapw
diegosouzapw merged commit 08f23d0 into diegosouzapw:release/v3.8.50 Aug 20, 2026
3 checks passed
diegosouzapw added a commit that referenced this pull request Aug 20, 2026
…llision

#10722 (Token Kiosk) and #10729 (Cursor) each independently bumped the
gateways/specialty-media APIKEY_PROVIDERS count by one in the same merge-train
batch; neither PR could see the other's bump, so the merged tree landed at 230
while the surviving hardcoded assertion still said 229.

Co-authored-by: diegosouzapw <8016841+diegosouzapw@users.noreply.github.com>
diegosouzapw added a commit that referenced this pull request Aug 20, 2026
Today's merge-train batch1 (#10722 Token Kiosk, #10729 Cursor) each added one
new APIKEY_PROVIDERS entry, bringing the live provider count to 343 — the
hardcoded '342' in README.md, AGENTS.md, llm.txt, package.json's description,
PROVIDER_REFERENCE.md, and 4 hero/comparison SVGs went stale as a result.
check:docs-counts (STRICT) now passes; regenerated PROVIDER_REFERENCE.md via
npm run gen:provider-reference. The v3.8.50 growth-log table row in README.md
(line 66) is left as-is — it's a historical point-in-time snapshot, not a
live claim.

Co-authored-by: diegosouzapw <8016841+diegosouzapw@users.noreply.github.com>
muhamadgalihsaputra pushed a commit to niyatna/NiyatnaRoute that referenced this pull request Sep 27, 2026
…zapw#10722, diegosouzapw#10797) + pre-existing chatBodyAdmission.ts drift

Co-authored-by: diegosouzapw <8016841+diegosouzapw@users.noreply.github.com>
muhamadgalihsaputra pushed a commit to niyatna/NiyatnaRoute that referenced this pull request Sep 27, 2026
…egosouzapw#10722)

Merged via merge-train (release/v3.8.50, batch1 2026-08-20) — static gates (typecheck/file-size/complexity/cognitive/changelog) green on the combined tree; test:unit reds observed in the boarded run were verified pre-existing on the pure release tip (unrelated flake), not caused by this PR. Thanks for the contribution!
muhamadgalihsaputra pushed a commit to niyatna/NiyatnaRoute that referenced this pull request Sep 27, 2026
…llision

diegosouzapw#10722 (Token Kiosk) and diegosouzapw#10729 (Cursor) each independently bumped the
gateways/specialty-media APIKEY_PROVIDERS count by one in the same merge-train
batch; neither PR could see the other's bump, so the merged tree landed at 230
while the surviving hardcoded assertion still said 229.

Co-authored-by: diegosouzapw <8016841+diegosouzapw@users.noreply.github.com>
muhamadgalihsaputra pushed a commit to niyatna/NiyatnaRoute that referenced this pull request Sep 27, 2026
Today's merge-train batch1 (diegosouzapw#10722 Token Kiosk, diegosouzapw#10729 Cursor) each added one
new APIKEY_PROVIDERS entry, bringing the live provider count to 343 — the
hardcoded '342' in README.md, AGENTS.md, llm.txt, package.json's description,
PROVIDER_REFERENCE.md, and 4 hero/comparison SVGs went stale as a result.
check:docs-counts (STRICT) now passes; regenerated PROVIDER_REFERENCE.md via
npm run gen:provider-reference. The v3.8.50 growth-log table row in README.md
(line 66) is left as-is — it's a historical point-in-time snapshot, not a
live claim.

Co-authored-by: diegosouzapw <8016841+diegosouzapw@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants