Skip to main content
AgentVault accepts OTLP-formatted agent telemetry via a simple HTTP POST endpoint. Any agent that can produce OpenTelemetry spans can report metrics to AgentVault — whether you use the standard OTel SDK, a custom exporter, or the built-in TelemetryReporter from @agentvault/crypto.

What Telemetry Powers

AgentVault uses ingested spans to:
  • Compute trust scores — reliability, error rate, and response time dimensions feed into the agent’s trust tier
  • Populate the observability dashboard — trace visualization, span timelines, and aggregate metrics
  • Feed external collectors — the OTel push export worker forwards spans to any OTLP-compatible backend
Telemetry is agent-scoped. Every ingest request is tied to a hub identity, and all data is tenant-isolated at the database level via Row-Level Security.

Ingest Endpoint

Request Body

Response

Authentication

The ingest endpoint accepts three authentication methods.

Span Format

The endpoint accepts OTLP camelCase field names. Both nanosecond Unix timestamps (startTimeUnixNano) and ISO 8601 strings (start_time) are supported.

Semantic Conventions

Use the ai.agent.* namespace for all agent-specific attributes. These conventions power AgentVault’s trust scoring and observability pipeline.

Integration Examples

Choose between the built-in SDK (recommended) or wiring up the standard OTel SDK directly. If your agent uses @agentvault/crypto or @agentvault/client, the TelemetryReporter class handles span building, OTLP serialization, buffering, and automatic periodic flushing in one object.
TelemetryReporter is also integrated automatically in SecureChannel (plugin) and AgentVaultClient (client SDK). Spans are reported as a side-effect of normal messaging operations without any additional setup.

Standard OTel SDK

Use the standard OpenTelemetry SDK with a custom exporter that posts to AgentVault’s ingest endpoint.
1

Install dependencies

2

Create a custom exporter

3

Initialize the tracer and report spans

Query API

Once spans are ingested, retrieve them via the query endpoints (owner auth required).
The /summary endpoint returns aggregate metrics — total spans, error count, error rate, and average duration — useful for quick health checks.

Rate Limits

Telemetry ingest shares the standard API rate limit: 60 requests per minute per API key. Batch multiple spans into a single request to stay well under the limit.
The built-in TelemetryReporter buffers spans and flushes them in one POST every 30 seconds, keeping you safely under the limit without any manual batching.