Skip to content

feat(auth)!: split API keys from legacy tokens#112

Merged
Microck merged 1 commit into
mainfrom
feat/api-key-token-split
May 26, 2026
Merged

feat(auth)!: split API keys from legacy tokens#112
Microck merged 1 commit into
mainfrom
feat/api-key-token-split

Conversation

@Microck

@Microck Microck commented May 26, 2026

Copy link
Copy Markdown
Owner

Summary

  • add KAGI_API_KEY, [auth].api_key, and kagi auth set --api-key for current /api/v1 Search and Extract credentials
  • keep KAGI_API_TOKEN and [auth].api_token scoped to legacy /api/v0 commands
  • update auth wizard, validation, docs, and tests for the v1/v0 credential split

Breaking change

  • API-first base search now requires KAGI_API_KEY or [auth].api_key
  • KAGI_API_TOKEN and [auth].api_token no longer satisfy base Search API mode

Verification

  • cargo fmt --check
  • cargo test -q --locked

Add KAGI_API_KEY and auth.api_key for current /api/v1 Search and Extract endpoints while keeping KAGI_API_TOKEN and auth.api_token scoped to legacy /api/v0 commands.

Update auth validation, wizard flows, CLI docs, and tests so users can configure current API keys and legacy API tokens separately.

BREAKING CHANGE: API-first base search now requires KAGI_API_KEY or auth.api_key. KAGI_API_TOKEN and auth.api_token no longer satisfy base Search API mode.
@Microck Microck enabled auto-merge May 26, 2026 06:16
@Microck Microck merged commit 433783a into main May 26, 2026
6 checks passed
@Microck Microck deleted the feat/api-key-token-split branch May 26, 2026 06:17
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.

1 participant