Connections reference
The connection kinds, what each reaches and misses, the receiver each key opens, and the MCP tools.
A connection is a source: one named feed with one key, one kind and one receiver. Sources are created on Settings, Connections (/settings/connections) by an Administrator or Governance lead, or over the API with POST /api/v1/usage/gateway/sources. The sixth door, Connect AI, is a Scorecard screen and is covered in Connect Claude, ChatGPT, Claude Code or Codex.
Kinds
| kind | Door | Shown as | Key |
|---|---|---|---|
| managed_policy | Managed fleet | Managed policy | Source ingest key, shown once |
| cloudflare_ai_gateway | API gateway | AI gateway | Source ingest key, shown once |
| local_collector | Developer machines | Local collector | Source ingest key, shown once |
| mcp_client | Another system | Connected system | Source ingest key, shown once |
| vendor_analytics | Vendor account | Vendor analytics | No ingest key; a vendor admin key is stored sealed |
Reach and blind spots
Read from the same table the Connections page shows, so the two cannot disagree.
| Door | Reaches | Cannot see |
|---|---|---|
| Managed fleet | Every seat your fleet manager reaches, on any plan. Users cannot turn it off. | Web chat, tools with no managed-settings mechanism, and devices your fleet manager does not manage. |
| API gateway | Every API-metered call routed through your gateway, attributed per request. | Subscription seats, Claude Code on a Max plan, Cursor, Copilot, web chat, cannot be routed through a gateway at all. |
| Developer machines | Claude Code and Hermes logs on machines where it is installed, including subscription seats. | Any machine it was not installed on. It is a manual install, not a fleet deployment. |
| Another system | Whatever the system on the other end sends, usage or spend, pushed straight into your record. Nothing is installed and nothing is exported. | Everything that system does not send, and every system nobody connected. This is the one feed whose reach Oabo cannot state for you: the other end decides what it reports. |
| Vendor account | Web chat, read nightly from the vendor's own report, claude.ai and chatgpt.com, plus Claude Code, Cowork and Codex credits, priced at what the vendor actually billed. | Personal accounts on personal devices, which never appear in an organization report. Conversation content is deliberately not collected. |
Receivers
A key opens one door. Using it at another kind's receiver returns 403 and names the right one.
| kind | Receiver |
|---|---|
| managed_policy | POST /api/v1/usage/gateway/managed-policy/otlp |
| cloudflare_ai_gateway | POST /api/v1/usage/gateway/cloudflare/otlp |
| local_collector | POST /api/v1/usage/gateway/collector/events |
| mcp_client | POST /api/v1/mcp |
| vendor_analytics | none: Oabo pulls from the vendor with the stored key |
Note
No key, a malformed key, a revoked key or a key for a deleted source all answer 404, so an unauthenticated caller learns nothing about what exists. Keys do not expire; revoke or re-issue instead, and both take effect at once.
Health per source: GET /api/v1/usage/gateway/sources reports events_received, last_event_at, unattributed_events and last_error.
MCP tools
POST /api/v1/mcp: Streamable HTTP, stateless, JSON responses. GET returns 405; no session id is issued. Configure the client with the URL and key the Another system door returns:
{
"transport": "streamable-http",
"url": "https://<your-workspace>/api/v1/mcp",
"headers": { "Authorization": "Bearer <ingest-key>" }
}| Tool | Does |
|---|---|
| submit_usage_events | Record measured token usage as day-level totals. Safe to retry. |
| submit_spend | Record one month’s cost for one system. Send idempotency_key. |
| list_sources | The organization’s connected feeds and their health. |
| get_scorecard_summary | Read back recorded cost and token totals for a month. Carries is_demo while seeded figures are still served. |
| submit_evidence_records | ModelDeck runtime evidence, one metadata-only record per request or decision. Schema modeldeck.evidence.v1. |
Arguments mirror the HTTP schemas in Ingestion API reference, with fingerprint as an argument rather than a header. Full JSON Schemas come back from tools/list. A tool that refuses the work returns a normal result with isError: true and a sentence saying why; a JSON-RPC error means the protocol failed, not the request.
Note
There is no OAuth, no dynamic client registration and no discovery on the MCP endpoint. Connecting a system is a deliberate act by an administrator.