feat(api): add endpoint restrictions for client API keys

[hijak]

Summary

• Add allowedEndpoints field to API keys that restricts which endpoint categories a key can access
• Supports 14 categories: chat, search, embeddings, images, audio, video, music, rerank, models, moderations, batches, files, web-fetch, agents
• Empty array = all endpoints allowed (backward compatible with existing keys)
• Policy enforcement is centralized in enforceApiKeyPolicy() — no individual route handler changes needed
• Dashboard UI: new "Allowed Endpoints" section in the permissions modal with All/Restrict toggle and per-category checkboxes

Changes

Area	Files	Description
Constants	src/shared/constants/endpointCategories.ts (new)	14 endpoint categories + resolveEndpointCategory() resolver
DB	src/lib/db/apiKeys.ts	allowed_endpoints TEXT column, parse/persist in metadata
Policy	src/shared/utils/apiKeyPolicy.ts	New endpoint check (Check 2.5) in policy pipeline
Validation	src/shared/validation/schemas.ts	Zod schema for allowedEndpoints
Dashboard	ApiManagerPageClient.tsx	Endpoint restriction UI in permissions modal
i18n	src/i18n/messages/en.json	3 new translation strings
Tests	tests/unit/endpoint-categories.test.ts (new)	24 pure unit tests for category resolution
Tests	tests/unit/endpoint-restrictions-policy.test.ts (new)	DB-backed tests for policy enforcement + persistence

Test plan

• 24 unit tests for resolveEndpointCategory() pass
• npm run typecheck:core — no new errors
• npx eslint on changed files — 0 errors
• Manual: create API key, set allowedEndpoints: ["search"], verify /v1/search works but /v1/chat/completions returns 403
• Manual: verify existing keys without allowedEndpoints still work on all endpoints
• Manual: check dashboard permissions modal shows new endpoint restriction section

[gemini-code-assist]

Code Review

This pull request introduces API key endpoint restrictions, allowing keys to be restricted to specific categories of API endpoints (e.g., chat, search, embeddings). The changes span database schema updates, policy enforcement checks, UI components for managing permissions, and comprehensive unit tests. The review feedback highlights critical security and correctness issues: an authorization bypass in getApiKeyMetadata due to a missing camelCase conversion for allowed_endpoints, a potential bypass in relative URL parsing within the policy check, a case-sensitivity bypass in endpoint category resolution, and a recommendation to use a Zod enum to validate allowed endpoint categories.

[gemini-code-assist]

In getApiKeyMetadata, rowToCamel is not called on the database row. Therefore, the database column allowed_endpoints is not converted to camelCase. Accessing (record as JsonRecord).allowedEndpoints directly will always return undefined, resulting in an empty array and bypassing the endpoint restrictions for all API requests. You should check both record.allowed_endpoints and record.allowedEndpoints to ensure backward compatibility and correct behavior.

Suggested change

	allowedEndpoints: parseStringList((record as JsonRecord).allowedEndpoints),
	allowedEndpoints: parseStringList(record.allowed_endpoints ?? (record as JsonRecord).allowedEndpoints),

[gemini-code-assist]

If request.url is a relative path (e.g., in certain environments or testing setups), new URL(request.url) will throw a TypeError because it lacks a base URL. This will trigger the catch block and silently fail open, bypassing the endpoint restrictions. Providing a dummy base URL like 'http://localhost' ensures relative URLs are parsed safely without affecting absolute URLs.

Suggested change

	const url = new URL(request.url);
	const url = new URL(request.url, "http://localhost");

[gemini-code-assist]

The path matching is case-sensitive. If a client sends a request with mixed casing (e.g., /v1/Chat/Completions), and the underlying router is case-insensitive, the request will bypass the endpoint restriction because resolveEndpointCategory will return null. Normalizing the pathname to lowercase before matching prevents case-sensitivity bypasses.

Suggested change

	export function resolveEndpointCategory(pathname: string): string | null {
	for (const { prefix, categoryId } of SORTED_PREFIXES) {
	if (pathname === prefix || pathname.startsWith(prefix + "/")) {
	return categoryId;
	}
	}
	return null;
	}
	export function resolveEndpointCategory(pathname: string): string | null {
	const normalizedPath = pathname.toLowerCase();
	for (const { prefix, categoryId } of SORTED_PREFIXES) {
	if (normalizedPath === prefix || normalizedPath.startsWith(prefix + "/")) {
	return categoryId;
	}
	}
	return null;
	}

[gemini-code-assist]

The allowedEndpoints field accepts any arbitrary string up to 64 characters. To prevent invalid configurations or typos (e.g., saving 'shat' instead of 'chat'), it is highly recommended to restrict the allowed values to the valid endpoint category IDs using z.enum.

    allowedEndpoints: z.array(z.enum([
      "chat",
      "search",
      "embeddings",
      "images",
      "audio",
      "video",
      "music",
      "rerank",
      "models",
      "moderations",
      "batches",
      "files",
      "web-fetch",
      "agents"
    ])).max(20).optional(),

[kilo-code-bot]

Kilo Code Review could not run — your account is out of credits.

Add credits or switch to a free model to enable reviews on this change.

[diegosouzapw]

Thank you @hijak for this great contribution! We resolved a small snake_case mapping issue in getApiKeyMetadata and successfully merged it into release/v3.8.5. It will be included in the upcoming release. We appreciate your support!