OKIT Usage Guide

01OKIT Desktop (open source)

The desktop app handles local features: the encrypted key vault, provider and agent switching, usage dashboards, and snapshots. Keys stay on your machine, no account required.

Install & run

npm install -g @cing-self/okit-cli
okit web

Browser extension, one-click key creation, CLI reference, and more live in the open-source manual: user-manual.en.md ↗.

02Account & sign-in

Click “Sign in” in the top-right corner to open the sign-in dialog: Google and GitHub are available; email sign-in is coming soon. The website and the desktop app share the same account.

Multiple devices

Every device that has signed in gets a device record, viewable and revocable from the account center. Revoking a device signs it out immediately; cloud data is kept.

Sign out

Website: account menu → “Sign out”. Desktop: settings page.

03Cloud Pro subscription

$7/month or $59/year (save 30%), billed through Stripe: international cards, Apple Pay, Google Pay.

• Entitlement activates automatically after payment — you'll see your avatar in the top-right corner. Open the desktop app and sign in with the same account to start syncing usage.
• Cancel anytime; access runs to the end of the period.
• When it lapses, only cloud features stop (usage history, alerts, multiple devices). Local features are unaffected.

04What Cloud receives

Cloud receives usage numbers, not keys: each usage event carries the provider, usage percentage / remaining amount, window type, and collection time.

• Provider whitelist of 37 (17 subscription + 20 prepaid); anything outside is rejected;
• Field whitelist: unknown fields reject the whole batch; single events ≤ 4KB, batches ≤ 256KB;
• API keys and cookies are never uploaded.

05Usage history

Usage events from the desktop app are aggregated into daily snapshots (provider account × window type × date), so you can view trends and historical curves across devices.

06Alerts (webhook)

Set threshold rules on your usage; when a threshold is crossed, OKIT pushes to your webhook. Any service that accepts webhooks works.

Creating a rule

• Metric: usage percentage (e.g. 8% left in a 5-hour window), remaining money, remaining quantity;
• Threshold and comparator: ≥ / ≤; scoped to one provider or all;
• The webhook URL must be publicly reachable over HTTPS.

Delivery behavior

Firing and recovery each deliver once (alert.firing / alert.recovered); retries reuse the same idempotency key so receivers can deduplicate.

{
  "type": "alert.firing",
  "rule_id": "6f1e2c…",
  "rule_metric": "used_percent",
  "comparator": ">=",
  "threshold": 90,
  "value": 92.5,
  "provider_id": "anthropic",
  "window_type": "5h",
  "transition_id": "8d3a…",
  "occurred_at": "2026-08-20T04:15:00.000Z"
}

07Privacy

These rights don't require a subscription. Every operation is recorded in an audit log.

• Export: all cloud data, downloadable as a gzipped JSON bundle;
• Delete usage data: clears cloud usage history;
• Delete account: confirm with an email code → wait out the 30-day cooling-off window → permanent deletion; cancellation is possible during the window.

08FAQ

I didn't get an alert

Check, in order: the rule is enabled; the webhook is publicly reachable; each crossing delivers once (firing / recovery) — nothing was missed; usage events are still syncing.

Payments and refunds

Billed through Stripe: international cards, Apple Pay, Google Pay. After canceling, access runs to the end of the period; account deletion can be undone within 30 days.

Are keys ever sent to the cloud?

No. A whitelist plus size limits, guarded by automated tests for sensitive fields; API keys and cookies are never uploaded.