Explorer
The Explorer calls the docs worker, the worker calls the library: repos.get, issues.list, pullRequests.list, commits.list, ciRuns.list, threads.list and users.get. Exactly what a script would do. Nothing on the page is a mock. A 404 is the platform's, and a 503 means the platform wants a token the worker does not have.
| Operation | What it answers | Tool equivalent |
|---|---|---|
| Repository | one Repository, minus the worker's own viewerPermission | forges_repos_get |
| Issues | up to ten open, closed or all issues, no bodies | forges_issues_list |
| Pull requests | up to ten, with branches, head SHA, draft and mergeability | forges_pull_requests_list |
| Commits | up to ten from the default branch, no files | forges_commits_list |
| CI runs | up to ten, with status and conclusion | forges_ci_runs_list |
| Threads | up to five review threads of one pull request, comments bounded | forges_threads_list |
| User | one profile, minus the email | forges_users_get |
| Platforms | which platforms the worker holds a token for | forges_users_authenticated |
Every query is a deep link. /explorer?op=pulls&platform=github&repo=nitrojs/nitro&state=open opens the page on that answer. For Gitea, host picks gitea.com or codeberg.org. Any other host is refused, the worker is not a proxy. The copy button next to the examples gives the same call as a tool invocation in JSON.
Caching and manners
Answers are cached on the worker, in KV in production: fifteen minutes for a repository, ten for a list. A thrown failure is never cached, so a typo or an outage does not stick. One address can start thirty new platform requests a minute, cache hits are free.
The worker passes an explicit token to every provider, the empty string when it has none, so the library never shells out to gh on a Worker. Anonymous GitHub reads share sixty requests an hour per address across everyone using the page. The cache is what makes that enough.
Where a token matters
- GitHub review threads go through GraphQL, no anonymous access.
- GitLab discussions answer 401 without a token, even on a public project.
- Gitea reads, review comments included, work anonymously on public repos.
The Platforms tab says which platforms the worker is authenticated to. Never a token, just yes or no.
The landing
The panels on the home page start from answers recorded through the library and labelled sample. As the page walks through three repositories on three hosts, each one is swapped for the worker's live answer and relabelled live. The recorded answers live in docs/app/utils/landing-fixtures.ts and are regenerated with docs/scripts/record-fixtures.mjs. Never by hand, hand edited fixtures drift and nobody notices.