Skip to content

api refactor: remove/merge admin endpoints to public#185

Merged
peterj merged 1 commit intomainfrom
api-refactor-5
Feb 18, 2026
Merged

api refactor: remove/merge admin endpoints to public#185
peterj merged 1 commit intomainfrom
api-refactor-5

Conversation

@ilackarms
Copy link
Copy Markdown
Contributor

No description provided.

Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull request overview

This PR consolidates the API structure by merging admin endpoints into the public API under a unified /v0 path prefix, eliminating the separate /admin/v0/ endpoint hierarchy.

Changes:

  • Merged admin and public endpoints under a single /v0 path prefix
  • Simplified client code by removing admin-specific request helpers
  • Updated middleware and routing logic to reflect the consolidated API structure

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated no comments.

File Description
internal/registry/api/server.go Removed /admin/v0/ path prefix from trailing slash middleware
internal/registry/api/router/v0.go Consolidated route registration - removed separate admin route functions and merged all endpoints under /v0
internal/registry/api/router/router.go Removed admin tag from OpenAPI configuration, removed /admin/v0/ checks from 404 handler, updated comments
internal/client/client.go Removed baseURLWithoutVersion() and newAdminRequest() helpers, updated all endpoints to use standard /v0 paths
Comments suppressed due to low confidence (1)

internal/registry/api/router/router.go:183

  • The "admin" tag was removed from the OpenAPI tags configuration, but the edit endpoint in internal/registry/api/handlers/v0/edit.go still references this tag in its Tags array (line 37). This will cause the OpenAPI documentation to reference an undefined tag. Additionally, "deployments" and "embeddings" tags are used by their respective endpoints but are missing from this tags list, which should be added for complete API documentation.
	api.OpenAPI().Tags = []*huma.Tag{
		{
			Name:        "servers",
			Description: "Operations for discovering and retrieving MCP servers",
		},
		{
			Name:        "agents",
			Description: "Operations for discovering and retrieving Agentic agents",
		},
		{
			Name:        "skills",
			Description: "Operations for discovering and retrieving Agentic skills",
		},
		{
			Name:        "publish",
			Description: "Operations for publishing MCP servers to the registry",
		},
		{
			Name:        "auth",
			Description: "Authentication operations for obtaining tokens to publish servers",
		},
		{
			Name:        "health",
			Description: "Health check endpoint for monitoring service availability",
		},
		{
			Name:        "ping",
			Description: "Simple ping endpoint for testing connectivity",
		},
		{
			Name:        "version",
			Description: "Version information endpoint for retrieving build and version details",
		},
	}

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@peterj peterj merged commit fb54b9f into main Feb 18, 2026
9 checks passed
aryehklein added a commit to aryehklein/agentregistry that referenced this pull request Feb 22, 2026
…actor

After PR agentregistry-dev#185 (commit fb54b9f), which removed /admin/v0 endpoints from
the backend, the UI was not updated and continues trying to call the
now-deleted endpoints. This causes all admin UI pages to fail with 404
errors.

This commit updates ui/lib/admin-api.ts to use /v0/* endpoints instead
of /admin/v0/*, matching the current backend API structure.

Changes:
- Replace all /admin/v0 references with /v0 in ui/lib/admin-api.ts
- Update comment to reflect correct API path

Testing:
- Verified UI can successfully fetch servers, agents, skills, and deployments
- Confirmed all admin UI pages load without 404 errors
- Tested against local registry server

Fixes the admin UI broken since PR agentregistry-dev#185.
timflannagan pushed a commit that referenced this pull request Feb 23, 2026
…actor (#208)

# Description

After PR #185 (commit fb54b9f), which removed `/admin/v0` endpoints from
the backend, the UI was not updated and continues trying to call the
now-deleted endpoints. This causes all admin UI pages to fail with 404
errors.

**What changed:**
- Updated `ui/lib/admin-api.ts` to use `/v0/*` endpoints instead of
`/admin/v0/*`, matching the current backend API structure
- Changed all 26 occurrences of `/admin/v0` to `/v0`
- Updated comment to reflect correct API path

**Testing:**
- ✅ Verified UI can successfully fetch servers, agents, skills, and
deployments
- ✅ Confirmed all admin UI pages load without 404 errors
- ✅ Tested against local registry server

Fixes the admin UI broken since PR #185.

# Change Type

/kind fix

# Changelog

```release-note
fix(ui): Update API client to use /v0 endpoints after backend refactor removed /admin/v0 routes
```

# Additional Notes

This is a critical bug fix - the admin UI has been completely
non-functional since the backend refactor in PR #185. All API calls were
returning 404 errors because the UI was calling endpoints that no longer
exist.
christian-posta pushed a commit to christian-posta/agentregistry that referenced this pull request Mar 9, 2026
christian-posta pushed a commit to christian-posta/agentregistry that referenced this pull request Mar 9, 2026
…actor (agentregistry-dev#208)

# Description

After PR agentregistry-dev#185 (commit fb54b9f), which removed `/admin/v0` endpoints from
the backend, the UI was not updated and continues trying to call the
now-deleted endpoints. This causes all admin UI pages to fail with 404
errors.

**What changed:**
- Updated `ui/lib/admin-api.ts` to use `/v0/*` endpoints instead of
`/admin/v0/*`, matching the current backend API structure
- Changed all 26 occurrences of `/admin/v0` to `/v0`
- Updated comment to reflect correct API path

**Testing:**
- ✅ Verified UI can successfully fetch servers, agents, skills, and
deployments
- ✅ Confirmed all admin UI pages load without 404 errors
- ✅ Tested against local registry server

Fixes the admin UI broken since PR agentregistry-dev#185.

# Change Type

/kind fix

# Changelog

```release-note
fix(ui): Update API client to use /v0 endpoints after backend refactor removed /admin/v0 routes
```

# Additional Notes

This is a critical bug fix - the admin UI has been completely
non-functional since the backend refactor in PR agentregistry-dev#185. All API calls were
returning 404 errors because the UI was calling endpoints that no longer
exist.
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