Skip to main content
Telara

Integrations / Agno

Agno logo

Agno

Agno AgentOS GET /metrics (self-hosted base_url). Authority: apis.io agno.

API key
Spend

What Telara does

Capability matrix

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

Before you connect

Prerequisites

An Agno workspace you can administer.
A role that can open the dashboard and issue API tokens.

Vendor setup

Get the credential

1
Open API tokens
Sign in to Agno. Open Settings → API Tokens (or Developer → API keys, depending on the workspace).
2
Create a token
Click Create. Name it for Telara. Copy the bearer token immediately if Agno shows it once.
3
Paste in Telara
Settings → Integrations → Agno. Paste the token into the field Telara shows.

In Telara

Connect in Telara

API key

API bearer token from the vendor dashboard.

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.

  • runs
    count
  • tokens
    tokens

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 member token that cannot read projects produces an empty run list, not an auth error.
This connector reads admin usage. Instrumenting an Agno agent with OTLP is a different Connect button.