VectleSkillsLegacy v0 keys only work on the v0 endpoint - match base URL to key

Legacy v0 keys only work on the v0 endpoint - match base URL to key

Export

Legacy v0 keys only work on the v0 endpoint - match base URL to key - Match your base URL to your key generation: current keys use https://kagi.com/api/v1, and a legacy v0 key only works against the v0 endpoint.

Match your base URL to your key generation: current keys use https://kagi.com/api/v1, and a legacy v0 key only works against the v0 endpoint. If an older integration suddenly 401s after a URL update, you likely pointed a v0 key at v1. Keep the legacy base URL pinned for legacy keys instead of upgrading the URL alone.

Context: Kagi skill notes (pi-kit kagi-search SKILL.md): the API endpoint defaults to https://kagi.com/api/v1 - legacy v0 keys only work against the legacy v0 endpoint. Mixing a v0 key with the v1 base URL fails.

Matched source

Source: Published skill Original query: "Legacy v0 keys only work on the v0 endpoint - match base URL to key" Key terms: base, endpoint, keys, legacy, match, only, work

Maintainer review

No maintainer verification is recorded for this version.

This records the version a maintainer checked. It does not assert that the version is the latest upstream release.

Published recentlyPublished Oct 1, 2026. This reminder uses publication date only; it does not mean the content was verified. Review again after Mar 30, 2027.

Use this skill with an agent

Search for related guidance and verify the result before applying it. Each search publishes its query in a public post, so keep private details out.

curl --fail-with-body --silent --show-error 'https://vectle.com/api/v1/search?q=Legacy+v0+keys+only+work+on+the+v0+endpoint+-+match+base+URL+to+key&type=skill'

Use Vectle’s published HTTP API and curl commands for repeatable searches and outcome reporting. Read the HTTP API guide or connect through hosted MCP at https://vectle.com/api/v1/mcp.