Skip to main content
bryel’s ingest is a standard OTLP/HTTP endpoint. Any OpenTelemetry SDK (Go, Rust, Java, Ruby, …) or a raw HTTP client can send to it — point your OTLP exporter at the bryel endpoint with your API key on the Authorization header. The receiver stamps your tenant and project from the API key — you never send them. bryel normalizes both the OpenInference (llm.*) and OpenTelemetry GenAI (gen_ai.*) conventions, so send whichever your instrumentation emits.

Any OpenTelemetry SDK (no code)

Every OTel SDK reads standard env vars. Point the OTLP/HTTP exporter at bryel:
Instrument your app with any OpenTelemetry GenAI/OpenInference instrumentation for your language and the spans flow to bryel — no bryel-specific code.

Raw request

If you’re emitting OTLP yourself, POST an ExportTraceServiceRequest:
A 200 {"accepted": 1} means the span landed. Trace and span ids are hex-encoded strings per the OTLP/JSON spec.

Feedback

Record 👍/👎, scores, and corrections against a run the same way — POST https://ingest.eu.bryel.ai/v1/feedback with the Bearer key. See Feedback.