Skip to Content
V1Using Lore SaaSAI Usage ConnectorsOverview

AI Usage Connectors

AI usage connectors let an organization see what it spends on AI tools, in one place, with numbers that match each vendor’s invoice. An org Owner connects each vendor’s admin API once in the Lore panel. From then on, Lore pulls the org’s usage and cost every hour and shows it under AI Usage.

Connectors require an active Pro plan. On self-hosted Registries with LORE_PRICING_ENABLED=false, the plan check is skipped.

What Lore uses, and what it never uses

Connectors only accept admin or analytics credentials that your org creates for this purpose, such as an Anthropic Admin API key or a Cursor admin API key. Lore never reads, copies or reuses anyone’s personal login, OAuth token or session for any AI tool. Most vendors prohibit that, and a governance product can’t be built on a mechanism the vendor itself prohibits.

Credentials are validated with a live, read-only call when you save them, stored encrypted, and never shown again, not even to you.

Billed, estimated and credits

Some vendors report the same usage in more than one place. For example, Claude Code usage through the API appears both in Anthropic’s cost report and in Claude Code Analytics. To avoid counting it twice, Lore labels every amount:

LabelMeaningCounted in totals?
BilledWhat the vendor bills your orgYes
EstimatedA vendor-computed estimate (e.g. Claude Code Analytics)No, shown separately
CreditsUsage credits on seat-based plansNo, shown separately

Totals only ever add up billed amounts.

Who sees what

OwnerBilling adminMember
Configure connectors✅——
Org totals and breakdowns (vendor, product, model)✅✅—
Breakdown by person✅——
Their own usage✅✅✅

Every member can see their own usage under AI Usage → My AI usage. That view shows exactly what org owners can see about them.

Coverage

SourceCoveredNotes
Anthropic Claude API (Console)✅ anthropic-adminBilled cost by workspace; no per-person cost
Claude Code (API and subscription users on Console orgs)✅ anthropic-adminPer person, estimated cost
Claude Enterprise (chat, Claude Code, other surfaces)✅ anthropic-enterprisePer person; billed only on usage-based Enterprise
Claude Code on Team, Pro and Max plans✅ Claude Code telemetryPer person and per repository, API-equivalent (estimated) cost; compared with seat cost
Claude Cowork on Team and Enterprise✅ Cowork telemetryPer person, API-equivalent (estimated) cost; usage only, content never stored
claude.ai chat on Team❌Anthropic provides no programmatic analytics API for Team plans
Office Agents (Claude in Excel, PowerPoint…)❌ not yetExports traces with content and no cost; not received
OpenAI Platform (API)✅ openai-platformBilled cost by project; tokens by Platform user
ChatGPT / Codex workspaces❌ not yetPlanned once the workspace analytics API contract is verified
GitHub Copilot✅ github-copilotBilled cost org-level; activity per user
Cursor (Teams)✅ cursorBilled usage-based cost per person
Seat fees on seat-based plans❌Not reported by the analytics APIs
Usage per repository or project❌ hereRequires Lore Desktop (planned)

Freshness

Lore syncs each connector at most every hour (every 6 hours for Claude Enterprise and GitHub Copilot, whose data is daily). Vendors can revise recent data, so Lore re-reads a trailing window on every sync: 30 days for Claude Enterprise, 3 days for the others. The dashboard shows the last successful sync for each vendor.

Set up a connector

  1. Open the org in the Lore panel and go to Usage Connectors.
  2. Follow the guide for your vendor to create the right credential:
  3. Paste the credential and click Connect. Lore checks it with the vendor before saving.
  4. The first sync runs within an hour and backfills up to 90 days where the vendor allows it.

To disconnect, click Disconnect on the vendor’s card. By default the usage history already collected is kept. Check Also delete the usage history to remove it too.

© 2025 Lore · Built by M1 Cloud