Fulcrum: Root-cause debugging for failing AI systems

Fulcrum is building tools to find and explain failures in AI systems. It fits teams deploying agents or reinforcement-learning environments that need more than traces and pass rates: they need an adversarial investigation into why the system failed and what to change.

What it does

Fulcrum’s YC profile ↗ calls the product an agentic debugger. Its launch describes red-teaming agents that plug into an environment, agent traces and source code, then investigate fake solutions, reward hacking and catastrophic failures. The output is an explorable report that a developer can discuss rather than a dashboard that only says a run failed.

The current public site is broader than the YC one-liner. Fulcrum’s research site ↗ says the company works on measuring and optimizing model performance in fuzzy domains such as communication and truthfulness. It highlights research on Fable at the CIFAR Speedrun and links to writing on multi-agent systems, agent software and evaluation. That looks like a widening thesis around model behavior and human intent, not a contradiction of the debugger product, but a buyer should confirm which surface is available today.

The useful distinction is between observability and diagnosis. A team can already collect spans, screenshots and tool calls. Fulcrum’s stated bet is that an investigation agent can construct experiments, identify a hidden failure mode and produce a report that points to an environment bug or a model behavior problem. That is valuable when a small number of failures can block deployment, but it is not automatically worth adding to every routine evaluation suite.

Founder context and tradeoffs

The YC page identifies Kaivalya Hariharan as CEO, with MIT computer-science and mathematics training and research experience at Redwood Research and Truthful AI. It identifies Uzay Girit as CTO, with MIT math and computer-science training and research on in-context learning and scaling laws. Those backgrounds are relevant to the company’s evaluation and oversight focus, not proof that its agents diagnose a buyer’s system correctly.

Pricing is not public, and the current site reads more like a research and product thesis than a self-serve documentation hub. A buyer should ask what access the system needs, how much an investigation costs, which failure classes are covered and how humans review the suggested fix.

Editorial take

I would shortlist Fulcrum for a team shipping high-consequence agents or training environments where the bottleneck is root-cause understanding. I would not buy it just to add another eval score. The product earns its place when a failed run triggers a useful experiment and a concrete engineering decision.

Quick facts

Sources checked

Cohort context

Fulcrum is listed in Summer 2025. In our 2026-09-18 directory snapshot, 112 of 166 listed companies in that cohort have YC’s primary industry label B2B (67.5%). This is a current-directory comparison, not an original intake count or a performance ranking. Nine-cohort dataset.

Public website snapshot

Observed 2026-09-19 16:18 UTC in raw homepage HTML. This records visible metadata and advertised links, not agent execution or product quality.

Public observations · Collection method. Missing links here do not establish that a capability or file is absent elsewhere.