Choose how to connect
Pick the connection method that reaches the AI usage you have, and know what each one cannot see.
Decision tree
Oabo has six ways in because customers arrive with different evidence, not because the same job was built six times. Start from what you already have.
The six doors
Five are on Settings, Connections (/settings/connections), in the order a new administrator should consider them. The sixth, Connect AI, is the first page of the Scorecard and is available when Scorecard mode is enabled for your organization.
| Door | You need | Use it for |
|---|---|---|
| Vendor account | An admin usage key you create at the vendor | Web chat and credits read nightly from the vendor’s own organization report. Web chat needs an eligible Enterprise account. |
| Managed fleet | One policy file deployed by your fleet manager (MDM, Intune, Jamf) | Every managed seat on any plan. Users cannot turn it off. |
| API gateway | A base URL pointed at your Cloudflare AI Gateway | Every API-metered call routed through the gateway, attributed per request. |
| Developer machines | One pasted command per machine | Claude Code and Hermes sessions on individual machines, subscription seats included. This is the collector. |
| Another system | A key pasted into that system’s settings | A system of yours that pushes usage or spend to Oabo over MCP. Nothing is installed or exported. |
| Connect AI | Your Oabo address and a sign-in | The AI you chat with (Claude, ChatGPT, Claude Code, Codex) sets up your Scorecard with you and records its own work. |
What each door sees
Each door states its blind spot as prominently as its reach, on the Connections page and here. A feed that is silent is a gap, never a zero.
- Vendor account misses personal accounts on personal devices, which never appear in an organization report. Conversation content is deliberately not collected.
- Managed fleet misses web chat, tools with no managed-settings mechanism, and devices the fleet manager does not manage.
- API gateway misses subscription seats. Claude Code on a Max plan, Cursor, Copilot and web chat cannot be routed through a gateway.
- Developer machines misses any machine it was not installed on. It is a manual install, not a fleet deployment.
- Another system misses everything that system does not send. Its reach is the one Oabo cannot state for you.
- Connect AI sees what the connected AI records through Oabo. It is a setup assistant and a record of its own work, not a usage meter for other tools.
Note
Two feeds watching the same traffic do not double count: a usage record is keyed on organization, system, day, harness, model and provider, and a second delivery replaces the first. See Usage batches.
Next
- Developer machines: Install and run the collector.
- Connect AI: Connect Claude, ChatGPT, Claude Code or Codex.
- Another system or the API gateway: Connections reference and Ingestion API reference.