Skip to main content
Telara

Integrations / Factory

Factory logo

Factory

Factory (Droids) — Enterprise Analytics API for Factory Standard Credits, per-user token spend, tool invocations, and productivity signals. Spend-only connector for AI Platform Spend Governance.

API key
Spend
AI estate

What Telara does

Capability matrix

Indexes NoTracks spend YesDiscovers shadow AI YesRuns actions NoReal-time events No

Before you connect

Prerequisites

A Factory workspace you can administer.
Admin who can open Settings and issue API keys.

Vendor setup

Get the credential

1
Open API keys
Sign in to Factory. Open Settings → API Keys (organization settings).
2
Create a key
Click Create. Name it for Telara. Copy the key immediately.
3
Paste in Telara
Settings → Integrations → Factory. Paste the key into the field Telara shows.

In Telara

Connect in Telara

API key

Factory API key (prefix `fk-...`) from Settings → API keys. Analytics API requires Manager or Owner role — User role returns 403.

In Telara, open Settings → Integrations, choose this connector, and paste the key into the fields Telara shows.

Fields Telara asks for
  • API key

Spend

What gets measured

Resolution: Per user per day.

Attribution: Matched to people by email.

How far back vendor history goes is not published uniformly for this connector.

  • input_tokens
    tokens
  • tool_calls
    count
  • sessions
    count
  • output_tokens
    tokens
  • billable_tokens
    tokens

AI estate

What gets discovered

Config paths
  • ~/.factory/mcp.json
Resource kinds

mcp_client_configuration, mcp_server_deployment

Config paths
  • .factory/mcp.json
Resource kinds

mcp_client_configuration, mcp_server_deployment

Sync

Freshness & sync

Spend connectors refresh on the vendor pull cadence declared in the catalog. Indexing lag is not published for this connector.

Data handling

Permissions & data handling

Telara has not published a permission list for this connector yet. Treat the vendor consent screen as the source of truth until this page lists scopes.

This catalog entry does not declare extra semantic-search exclusions.

After connect

Verify it worked

After you save, Telara runs a read-only check against the account. The integration shows as connected when that check succeeds.

Honesty

Known limitations

A personal key is the wrong class when Telara asks for an organization key.
This connector reads Factory usage. It is not an OTLP exporter from droids.