Supported providers
Eight connectors ship today, plus manual entry, and the desktop app also reads Cursor as an experimental connector. 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.
On this page
The eight connectors, and manual entry
| id | connect | reads |
|---|---|---|
claude | Nothing to do: OpenLimiter reads what Claude Code already renders. | The Claude Code status line, automatically. A direct usage request is off until you turn it on; when on, it sends your own Claude Code login only to Anthropic, about every five minutes, and every Claude bar comes from it. Anthropic's policy for tools like this is unresolved. |
openrouter | Real OAuth, started from the hub. A key you already hold still works. | OpenRouter's documented key and usage report. |
codex | Use the login already there, or sign in from inside OpenLimiter. | The login the Codex CLI stored. May break when OpenAI changes it. |
antigravity | Set up the documented Antigravity CLI status line. | Quota from the documented status line. Use /usage in Antigravity CLI to refresh it. |
gemini_cli | Read only, from the login already there. | The login the Gemini CLI stored. May break when Google changes it. |
grok | Use the login already there. OpenLimiter cannot start Grok's own sign in yet. | The login the Grok CLI stored, without the client marker xAI's own tool sends. |
kimi | Use the login already there. OpenLimiter cannot start Kimi's own sign in yet. | The usage response the Kimi CLI defines. May break when Moonshot changes it. |
opencode | Use the sign in the opencode CLI already saved, or paste an OpenCode API key. | OpenCode Go's rolling, weekly and monthly usage, from an undocumented endpoint. May break without notice. |
manual | You write the numbers yourself. | Never breaks, never guesses. |
How data actually arrives
Most connectors read for themselves now. Only manual entry still does not, and that is worth stating plainly.
claudeis fed by the Claude Code status line the moment it renders. A direct usage request is off until you turn it on; when on, it is the source of every Claude bar instead.codex,gemini_cli,grok,kimiandopenrouterread the login their own tool already stored, at most once every fifteen minutes, behind the desktop app's own refresher or the terminal'sopenlimiter refresh.antigravityarrives through the documented Antigravity CLI status line. Use/usagein Antigravity CLI to refresh quota.manualis fed by a document you place in the state directory.opencodeis read by the desktop app with the sign in the opencode CLI saved on this computer, read only and never refreshed, or with an OpenCode API key you paste. It reads OpenCode Go's rolling, weekly and monthly usage from one undocumented endpoint, so it carries high automation risk.
The ingestion page documents the manual shape 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 spend keys
A key for an API spend meter is a separate thing from a subscription login. It lives in this device's operating system keyring by default. Cloud metering, an opt in Pro feature, stores that key encrypted on the server instead, so the hub and the phone can show spend with no device running.
Connectors that do not exist yet
Only the eight connectors and manual entry above are real, plus Cursor, which the desktop app reads as an experimental connector. 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.