API Authentication Infrastructure Fix

Summary

The legacy Unkey API (v1) used for utayomi's API authentication was deprecated, causing intermittent API request failures. This fix completes the migration to the latest Unkey API (v2), resolving the issue.

Issue

• The first API request succeeded, but subsequent requests failed
• HTTP status 401 (Unauthorized) or 429 (Too Many Requests) errors were returned
• Authentication errors occurred despite valid API keys

Cause

The Unkey API v1 (api.unkey.dev) used by utayomi reached End of Life, and aggressive rate limiting was enforced on v1 endpoints by the provider. This prevented normal API key verification.

Resolution

• Migrated Unkey SDK from v0.26 (v1 API) to v2.2 (v2 API)
• Changed authentication endpoint from api.unkey.dev to api.unkey.com

Impact on Users

• Existing API keys continue to work as-is (no reissue required)
• No changes to API usage or endpoints
• Requests will be processed normally after the fix is deployed