Integrations / Ideogram (direct)

Ideogram (direct)

Ideogram image-generation API (api.ideogram.ai, Api-Key header) called directly from customer code. TENG-2205: no telara-observability SDK wrapper exists for Ideogram, and there is no OpenAI-compatible fallback a generic wrapper could use instead — image generation is a different call shape (prompt in, image binary/URL out) than a chat completion. This connector only receives data if the customer's own code emits an OTel span or log record per generate call carrying the attributes below; an uninstrumented integration reports nothing, not zero. Ideogram meters usage in CREDITS, and per its docs "credit usage scales with the number of output images and selected model/render speed" — it is not token-based, so gen_ai.usage.* attributes do not apply and are intentionally absent. Credit balance and spend are visible only on the Ideogram account dashboard (ideogram.ai/manage-api); there is no admin/ billing API to pull them, which is why this is otlp_push rather than a pull connector. Cost is NOT derived to USD: Ideogram publishes no public credit-to-dollar rate that holds across plans, so no model_price_table is set. This connector reports credit and image counts only; $ appears only if the customer's own code emits a cost_usd attribute.

OTLP

Spend

What Telara does

Capability matrix

Indexes No Tracks spend Yes Discovers shadow AI No Runs actions No Real-time events No

Before you connect

Prerequisites

A process that uses Ideogram (direct) and can export OpenTelemetry.

Ability to run the Telara CLI where that process runs.

Vendor setup

Get the credential

Print the OTLP endpoint

Run `telara otlp`. It prints the endpoint and headers Telara expects. Do not paste a vendor API key on this connector.

Point Ideogram (direct) at it

Enable OpenTelemetry in Ideogram (direct) (or in your collector) and send traces to the endpoint that command prints.

In Telara

Connect in Telara

OTLP

This connector does not take a vendor key in Settings → Integrations. Run `telara otlp` (or point the vendor’s OpenTelemetry exporter at the endpoint that command prints) so usage arrives as telemetry.

Telara has not published the exact form fields for this method yet. Complete whatever the Connect dialog shows.

Spend

What gets measured

Resolution: Per request.

Attribution: Matched to people by email.

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

credits
count — Credits consumed by this generate call. Ideogram's own billable unit — scales with output image count and render speed/model choice. Not exposed on the response body per Ideogram's public docs, so the customer's instrumentation must compute/track it (e.g. from the dashboard-reported rate for the model used) and set it explicitly; absent that, this metric reads zero for that span rather than a real value.
images
count — Number of images returned by the call (the num_images request parameter, or the actual count returned).
generations
count — Count of generate calls (one span/log per request).

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

This connector does not declare a credential probe yet. A saved connection means Telara stored the credential, not that the vendor accepted it.

Honesty

Known limitations

Nothing appears in Telara until that process actually emits telemetry.

This is not an admin-key connector. Org-level spend, if Telara offers it for this vendor, is a separate page.