Skip to main content
Early pricing is live. Start free for up to 3 AI systems — no card, no time limit.Early pricing is live. Free for up to 3 AI systems.
All docs
Reference

Connections reference

The connection kinds, what each reaches and misses, the receiver each key opens, and the MCP tools.

5 minFor: Engineer

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

kindDoorShown asKey
managed_policyManaged fleetManaged policySource ingest key, shown once
cloudflare_ai_gatewayAPI gatewayAI gatewaySource ingest key, shown once
local_collectorDeveloper machinesLocal collectorSource ingest key, shown once
mcp_clientAnother systemConnected systemSource ingest key, shown once
vendor_analyticsVendor accountVendor analyticsNo 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.

DoorReachesCannot see
Managed fleetEvery 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 gatewayEvery 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 machinesClaude 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 systemWhatever 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 accountWeb 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.

kindReceiver
managed_policyPOST /api/v1/usage/gateway/managed-policy/otlp
cloudflare_ai_gatewayPOST /api/v1/usage/gateway/cloudflare/otlp
local_collectorPOST /api/v1/usage/gateway/collector/events
mcp_clientPOST /api/v1/mcp
vendor_analyticsnone: 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:

client configuration
{
  "transport": "streamable-http",
  "url": "https://<your-workspace>/api/v1/mcp",
  "headers": { "Authorization": "Bearer <ingest-key>" }
}
ToolDoes
submit_usage_eventsRecord measured token usage as day-level totals. Safe to retry.
submit_spendRecord one month’s cost for one system. Send idempotency_key.
list_sourcesThe organization’s connected feeds and their health.
get_scorecard_summaryRead back recorded cost and token totals for a month. Carries is_demo while seeded figures are still served.
submit_evidence_recordsModelDeck 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.

Previous

oabo-collector command reference

Last documented 2026-11-18 against master fb17e1c5. Live release 0.3.1.