OpenUI ObservabilityUser analytics
for AI agents

See what users saw and did, where your agent fell short, and what to build next.

You’re on the waitlist.

OpenUI ObservabilityUser analytics
for AI agents

See what users saw and did, where your agent fell short, and what to build next.

You’re on the waitlist.

OpenUI Observability insights preview
OpenUI Observability insights preview

A successful trace
can still fail the user.

Tracing was built for services, where requests either succeed or fail. It shows what your agent did, not whether the user’s goal was met.

  1. Compare revenue by region.

  2. OpenUI

    Revenue is up 17% this month.

  3. But which region is driving it?

Execution

Tracing says everything worked

All checks passed
  1. Tool calls succeeded

    Every call completed

    Passed
  2. The model responded

    No generation errors

    Passed
  3. The request completed

    Response returned 200

    Passed
User outcome

But tracing can’t tell you…

Not captured
  • Did the user get what they needed?

    The trace looks successful even when the answer is useless

    Not captured
  • What did the user actually experience?

    It records the response, not the UI they saw or how they used it

    Not captured
  • What should we build next?

    Errors and latency don’t show what users tried to do but couldn’t

    Not captured

Product analytics for AI agents

not just traces

Connect each response to what users saw,
what they did, and whether it met their needs.

Session replay in OpenUI Observability

Session replay

See every
user session

Replay the exact interface, responses, and interactions each user experienced.

Triage

Find sessions
worth opening

Surface failed journeys, unmet needs, and high-impact issues to understand where users struggle.

Triage in OpenUI Observability
Annotations in OpenUI Observability

Annotations

Turn bad responses
into feedback

Mark the broken response, add context, and share the session with your team.

Evals

Prevent the same
issue twice

Turn production failures into evals that catch regressions before release.

Evals in OpenUI Observability

Set up in two lines

Keep your agent framework and backend. The SDK captures events OpenUI already emits as it renders.

  1. 1
    Generate a frontend API key

    Create a publishable key in the OpenUI console. It’s safe to use in browser code.

  2. 2
    Initialize the SDK

    Add it once at your app entry point. No tracking code needed in your components.

// src/main.tsximport { createRoot } from "react-dom/client";import { App } from "./App";import * as Observability from "@openuidev/observability-cloud";
Observability.init({ apiKey: "pk-th-…" });
const root = document.getElementById("root");createRoot(root!).render(<App />);

Secure, compliant, and under your control

View trust centre

Frequently asked questions

Have another question? Join our Discord.

How is OpenUI Observability different from tracing tools?

Tracing tools show how your agent ran. OpenUI Observability shows what users experienced, including generated UI, interactions, errors, corrections, and fallbacks.

They work together. Export flagged responses as eval cases to tools such as Braintrust or LangSmith.

What does the SDK capture?

The SDK captures events from OpenUI when rendering settles, including timestamps, update counts, error counts, and error details such as code, source, and component.

Full capture includes the generated response and is enabled by default. Minimal capture excludes response content and error messages.

Can I control what data is sent?

Yes. Choose minimal capture to send metadata without generated responses. Use the beforeSend hook to edit or drop events before they’re sent to OpenUI Observability.

Is the frontend API key safe to expose?

Yes. Frontend API keys are publishable and designed for use in browser code, like an analytics key.

What does OpenUI Observability cost?

OpenUI Observability is free during early access. Pricing will be published before paid access begins.

Do I need OpenUI Gateway?

No. OpenUI Observability and OpenUI Gateway work independently.

We recommend using both. Gateway makes generated UI more reliable. Observability shows what users experienced and whether it worked.

See your agent through your users’ eyes

See what works, what’s missing, and what to build next.

Join waitlist

You’re on the waitlist.

Free during early access. View pricing