Skip to main content

API and Product Coverage

This document summarizes what the kagi CLI implements today, which auth path it uses, and which product settings are now manageable from the terminal.

Currently Implemented

Current V1 OpenAPI Endpoints

These endpoints come from Kagi’s current OpenAPI contract at https://kagi.com/api/docs/openapi and use KAGI_API_KEY with Bearer auth: Current V1 Search optional fields not exposed by this CLI: workflow, API response format, lens_id, inline lens, timeout, page, search-result extract, safe_search, and explicit personalization rule objects. Subscriber web-product features cover some adjacent workflows, but they are not represented as V1 OpenAPI request fields.

Legacy V0 APIs

These commands use Kagi’s older public API surface with KAGI_API_TOKEN and Bot auth:

Subscriber Web Product Features

These features use the subscriber web product with KAGI_SESSION_TOKEN:

Public Product Endpoints

These require no authentication:

Command Coverage Summary

Output and Flag Coverage

Human-Readable Formats

Search Options

Assistant and Settings Options

Live Verification

Live subscriber CRUD and round-trip tests were run against the real product flows for:
  • custom assistants
  • lenses
  • custom bangs
  • redirect rules
  • assistant thread round-trip
After those tests, the account-level settings pages were checked directly to confirm cleanup and no leftover test data.

Not Available

Intentionally Excluded

  • Account-synced domain preference writes are not exposed because Kagi does not document a stable public write API for Personalized Results.
  • Kagi Translate document, image, website, proofread, dictionary, and voice modes are not exposed.
  • Search-time safe-search overrides are not exposed. Safe-search remains an account setting.

Notes

  • Base-search fallback to the session-token path only exists on kagi search and kagi batch, and only when API-first mode was selected.
  • Search filters and lens search remain session-only because they depend on Kagi’s live web-product flow.
  • Settings management currently targets Kagi’s authenticated settings forms, not public API endpoints.