Your agent can say the right thing and do the wrong thing.

Mibo tests both, on every real conversation. One real trace in, a regression test drafted for you.

Tests for your agent, next to the tools you already use. Keep Langfuse, Datadog or LangSmith. Send traces from n8n or any OTLP/HTTP exporter.

Start testing free Explore test cases

Support example

Scenario: refund above the limit

FAILED

1
Customer
“Can I get a refund for order #4812?”
Agent looked up the order
Order found · $640
Agent issued the refund
Refunded $640 — no manager approval
Rule broken
“Never refund more than $500 without a manager’s approval.”
Agent replied to the customer
Tone and wording check passed

Correct wording. Broken refund rule.

Turn a recorded execution into a test.

Explore OTLP integration

Send your first trace
Configure an OTLP exporter and capture an execution from your system.
Generate a test with AI
Select a completed trace and ask AI to draft checks from its evidence. Review the draft before saving it.
Evaluate future traces
Send later executions and inspect which checks failed, together with the recorded response or action.

Exporter example

Instrument your application, replace the API key placeholder, and match the service name configured in Mibo. OTLP/HTTP JSON is also supported.

Mibo only Multiple destinations

Send traces directly from your instrumented application to Mibo.

export OTEL_EXPORTER_OTLP_TRACES_PROTOCOL=http/protobuf
export OTEL_EXPORTER_OTLP_TRACES_ENDPOINT=https://api.mibo-ai.com/public/traces
export OTEL_EXPORTER_OTLP_TRACES_HEADERS='x-api-key=<YOUR_API_KEY>'
export OTEL_SERVICE_NAME='your-service-name'

Send traces to an OpenTelemetry Collector and configure it to forward them to Mibo and your existing destination.

Application exporter

export OTEL_EXPORTER_OTLP_TRACES_PROTOCOL=http/protobuf
export OTEL_EXPORTER_OTLP_TRACES_ENDPOINT=http://127.0.0.1:4318/v1/traces
export OTEL_SERVICE_NAME='your-service-name'

Collector configuration

receivers:
  otlp:
    protocols:
      http:
        endpoint: 127.0.0.1:4318
exporters:
  otlp_http/mibo:
    traces_endpoint: https://api.mibo-ai.com/public/traces
    headers:
      x-api-key: ${env:MIBO_API_KEY}
  otlp_http/other:
    traces_endpoint: '<YOUR_OTHER_OTLP_HTTP_TRACES_ENDPOINT>'
service:
  pipelines:
    traces:
      receivers: [otlp]
      exporters: [otlp_http/mibo, otlp_http/other]

Set MIBO_API_KEY in the Collector environment. The other destination may need its own credentials. 127.0.0.1 requires the app and Collector to share a network namespace. Adjust existing exporter headers for the Collector; endpoint variables accept one URL, not a comma-separated list.

You can also configure multiple exporters in your SDK.

See both setup options →

Start testing for free. Scale when your suite grows.

Start with 3 agents and 500 traces per month. Upgrade for more capacity and history.

Starter

Recommended

$20/mo

Billed annually ($240)

For growing teams building production agents.

Plan limits include:

1,000 test runs / month
10 agents
100,000 traces / month
10 projects
5,000,000 tokens / month
90-day history
Semantic metrics

Get started

Free

$0/mo

Free forever

For individual developers and small prototypes.

Plan limits include:

100 test runs / month
3 agents
500 traces / month
1 project
300,000 tokens / month
7-day history

Get started free

Full

$50/mo

Billed annually ($600)

For teams that need the full platform.

Plan limits include:

3,000 test runs / month
100 agents
5,000,000 traces / month
100 projects
15,000,000 tokens / month
365-day history
Semantic metrics
Priority support

Get started

Questions about Mibo

What does Mibo evaluate?

Mibo checks recorded answers, tool calls, and values against the rules you configure, using the data in each trace.

Which systems can send traces?

Any system that exports OTLP/HTTP traces, including apps built with AI SDK 7 and @ai-sdk/otel, or with current OpenLLMetry versions for LangChain and LLM SDKs. n8n workflows send traces through the verified Mibo node.

What if a check needs missing data?

A missing field does not prove that a check passed. Add the required data to your instrumentation; the result depends on the check.

Does Mibo intervene in the interaction?

No. Mibo evaluates received traces; it does not block or undo the actions they record.

Turn a recorded execution into a test.

Send your first trace

Generate a test with AI

Evaluate future traces

Exporter example

Start testing for free. Scale when your suite grows.

Starter

Free

Full

Questions about Mibo