Fix remaining Registry API paths that miss /registry prefix#745
Merged
Fix remaining Registry API paths that miss /registry prefix#745
Conversation
The Registry Server mounts v0.1 routes under /registry, so the correct
client-facing path is /registry/{registryName}/v0.1/..., not
/{registryName}/v0.1/.... Three pre-existing mentions still used the
old form and returned 404 when copy-pasted:
- authentication.mdx: two curl examples in "Testing authentication"
(bearer-token and kubectl-service-account paths). The service-account
example also had a malformed /registry/v0.1/servers URL missing the
registry name entirely; replaced with /registry/default/v0.1/servers
to match the adjacent example.
- authorization.mdx: the GET /platform/v0.1/servers claims-gating
example now reads GET /registry/platform/v0.1/servers.
- concepts/skills.mdx: the skills extensions-API path mention now
includes the /registry/ prefix to match the actual route.
Verified against toolhive-registry-server@main internal/api/server.go
(r.Mount("/registry", v01.Router(svc))) and the swagger.yaml under
docs/thv-registry-api/.
The matching instances inside the #364 PR stack (quickstart, intro,
skills guide, configuration, publishing) were fixed as part of those
PRs. telemetry-metrics.mdx line 130 is intentionally left alone: the
/v0.1/servers/{name} string is the chi route pattern the instrument-
ation records, which does not include the outer /registry mount.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
There was a problem hiding this comment.
Pull request overview
This PR corrects remaining ToolHive Registry Server documentation examples that were missing the required /registry mount prefix in client-facing API paths, aligning the docs with the server’s mounted routing and OpenAPI spec.
Changes:
- Update an authorization example to use
GET /registry/{registryName}/v0.1/servers. - Fix authentication curl examples to include
/registry/{registryName}and normalize the kubectl token example todefault. - Update the skills “extensions API path” description to include the
/registry/prefix.
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| docs/toolhive/guides-registry/authorization.mdx | Fixes registry consumer API example path to include /registry/platform/.... |
| docs/toolhive/guides-registry/authentication.mdx | Fixes curl examples to use /registry/default/... (including the kubectl token example). |
| docs/toolhive/concepts/skills.mdx | Fixes the documented skills extensions API path to include /registry/{registryName}/.... |
ChrisJBurns
approved these changes
Apr 21, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Follow-up to the #364 stack that closes the remaining pre-existing instances where client-facing Registry Server URLs were missing the `/registry` mount prefix.
The Registry Server mounts v0.1 routes under `/registry` (verified against `toolhive-registry-server@main` `internal/api/server.go` at `r.Mount("/registry", v01.Router(svc))` and the swagger spec under `docs/thv-registry-api/swagger.yaml`). So the correct client path is `/registry/{registryName}/v0.1/...`, not `/{registryName}/v0.1/...`.
Fixed in this PR:
Not in scope for this PR:
Test plan
🤖 Generated with Claude Code