OpenTelemetry endpoints
Use the Aient SDKs when possible. If you are using a standard OpenTelemetry SDK directly, send OTLP HTTP traffic to the public ingest endpoints with a publishable key.Public endpoints
| Signal | Endpoint | Protocol |
|---|---|---|
| Traces | https://ingest.aient.ai/v1/traces | OTLP HTTP/JSON for Aient JS SDKs; standard OTLP HTTP clients may use their supported encoding |
| Logs | https://ingest.aient.ai/v1/logs | OTLP HTTP/JSON for Aient JS SDKs; standard OTLP HTTP clients may use their supported encoding |
Authentication
Set this header on every request:organisationId from application code.
Resource attributes
Set these resource attributes so Aient can group services and resolve source maps:| Attribute | Meaning |
|---|---|
service.name | Stable service name shown in Aient |
deployment.commit_sha | Exact commit for the deployed build |
deployment.commit_ref | Branch or ref name |
deployment.environment | Environment slug such as prod, qa, or dev |
Local development
For local collectors, usehttp://localhost:4318 as the base endpoint and let the SDK derive /v1/traces and /v1/logs.
The Aient JavaScript SDKs send OTLP HTTP JSON payloads and set Content-Type: application/json. They do not bundle protobuf runtime packages.