Built API-first, not API-added

One API, powering everything

There’s no separate “reporting API” bolted on after the fact. The Metrics Explorer, Logs Explorer, trace waterfall, and Query Performance Insights you see in the dashboard are all built on the same REST endpoints exposed to you — search spans, fetch a trace by ID, run a metric query, pull query performance rollups, stream logs and traces live. If the dashboard can show it, the API can return it.

A real, browsable spec — not just a promise

PeachTrace publishes a full OpenAPI specification with an interactive API reference, always available, so you can see exactly what’s callable before you write a line of code.

Built for AI-driven investigations

An API-first platform is what makes it possible to bring your own AI tooling into an investigation instead of waiting on someone to open a dashboard. Point an LLM-backed tool at the same metrics, logs, traces, and query performance data the dashboard uses, and let it do the digging: correlate a spike with the traces around it, pull the logs from a failing span, or check whether a slow query is a new regression — all through the same API, in whatever tool you already work in.

What you can query

• Traces — search spans, fetch a full trace by ID, live-tail incoming traces, browse services and resources
• Logs — search and filter log records, jump straight to the logs correlated with a trace, live-tail incoming logs
• Metrics — browse the metric catalog, run aggregation queries, pull histogram distributions
• Query Performance Insights — search rolled-up query stats, drill into a single query by hash