Skip to content

Document TrustedRouter setup #594

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
jperla wants to merge 1 commit into from
Closed

Document TrustedRouter setup #594

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -67,6 +67,14 @@ for this exact support, so if you are having problems or if you have question, j
- Handle per-key failures during settings import
- Security updates: mermaid v11.15.0, axios v1.16.0

## TrustedRouter

TrustedRouter exposes an OpenRouter-compatible API. To use it in Zoo Code,
choose the OpenRouter-compatible/custom provider path, paste your
TrustedRouter API key, and set the API base URL to
`https://api.trustedrouter.com/v1`. Useful model aliases include
`trustedrouter/auto`, `trustedrouter/zdr`, and `trustedrouter/e2e`.
Comment on lines +70 to +76

@edelauna edelauna Jun 14, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This content would be a better fit in Zoo-Code-Docs under docs/providers/ — there are already individual provider pages for OpenRouter, Requesty, etc. that follow a consistent format (frontmatter with keywords/description, Getting an API Key, Configuration, Tips sections).

A new docs/providers/trustedrouter.md following the same template would be the natural home for this.

Also worth noting: the main repo README has 17 localized copies under locales/ (ca, de, es, fr, hi, id, it, ja, ko, nl, pl, pt-BR, ru, tr, vi, zh-CN, zh-TW). Adding a section here without updating those creates i18n drift — another reason to keep provider-specific setup in the docs site instead.


<details>
<summary>🌐 Available languages</summary>

Expand Down
Loading