Supported providers
Nine connectors ship today. Each one carries its own honest labels describing where its credentials come from, how official its data interface is, and how likely it is to break.
The nine connectors
| id | connect | reads |
|---|---|---|
claude | 設定は不要です。OpenLimiterはClaude Codeがすでに表示している情報を読み取ります。 | The Claude Code status line, automatically. An opt in poll of Anthropic's own usage endpoint, with your own token, covers the gap when Claude Code is closed. Off unless you turn it on. |
openrouter | ハブから開始する正式なOAuthです。すでに持っているキーも引き続き使えます。 | OpenRouter's documented key and usage report. |
codex | 既存のログインを使うか、OpenLimiter内からログインします。 | The login the Codex CLI stored. May break when OpenAI changes it. |
antigravity | 既存の認証情報を使った読み取り専用の接続です。 | The credential the Antigravity CLI stored. May break when Google changes it. |
gemini_cli | 既存のログインを使った読み取り専用の接続です。 | The login the Gemini CLI stored. May break when Google changes it. |
grok | 既存のログインを使います。OpenLimiterからGrok自身のログインを開始することはまだできません。 | The login the Grok CLI stored, without the client marker xAI's own tool sends. |
kimi | 既存のログインを使います。OpenLimiterからKimi自身のログインを開始することはまだできません。 | The usage response the Kimi CLI defines. May break when Moonshot changes it. |
opencode | インポート専用です。ドキュメントは自分で用意します。 | A usage view behind a session you already signed in to. May break without notice. |
manual | 数値は自分で入力します。 | Never breaks, never guesses. |
How data actually arrives
Most connectors read for themselves now. Two still do not, and this is the part worth stating plainly.
claudeis fed by the Claude Code status line the moment it renders, and by an opt in poll of Anthropic's own usage endpoint when Claude Code is closed.codex、gemini_cli、antigravity、grok、kimi、openrouterは、それぞれのツールが保存したログインを最大15分に1回読み取ります。デスクトップアプリの更新処理、またはターミナルのopenlimiter refreshが実行します。manualis fed by a document you place in the state directory.opencodeis the one connector left with no reader of its own: it only accepts data throughopenlimiter ingest --provider opencode, because it reads an authenticated page rather than a login file.
The ingestion page documents the manual and OpenCode shapes in full.
Reading the labels
Every snapshot carries four labels, so a surface can always tell a reader how much to trust a number.
| label | values you will see |
|---|---|
credentialOrigin | official-local-tool, user-key, browser-session, user-entered |
dataInterfaceStatus | native-statusline-payload, documented-api, internal-endpoint, authenticated-scrape, manual |
automationRisk | low or high |
verification | UNVERIFIED |
What drift looks like
Unofficial interfaces change without notice. When a shape moves, parsing fails closed: the affected provider returns to unknown, the other providers are unaffected, and nothing invents a number to fill the gap.
The OpenRouter credential
OpenRouter is the one connector with a real sign in of its own: OAuth, started from the hub, and the key it hands back is what gets read from then on. A key you already hold still works, fed the same way any other connector is.
openlimiter ingest --provider openrouter --payload '{"data":{"total_credits":15,"total_usage":14.2}}'API支出用のキー
API支出の計測キーは、サブスクリプションのログインとは別のものです。通常はこのデバイスのOSのキーリングに保存されます。任意のPro機能であるクラウド計測では、代わりにサーバーへ暗号化して保存します。これにより、デバイスが起動していなくてもハブやスマートフォンで支出を表示できます。
Connectors that do not exist yet
Only the nine above are real. Anything else you might hope for is not built, is not scheduled, and should not be assumed. If a subscription has no connector, the manual path covers it today with numbers you enter yourself.