AI agent performance optimization

Cheaper and faster agents, with accuracy held to a baseline

Your agent reaches its cost and latency target without losing accuracy. One change at a time, each rerun against a baseline built from your own cases.

Why tuning goes in circles

Without a baseline, nobody knows what a fix broke.

Trimmed prompts can lose accuracy, bigger models slow runs, and only a rerun shows it.

  1. 01

    Where it stallsA bigger model for every step.

    What we do Each step gets the smallest model that passes.

  2. 02

    Where it stallsFive changes shipped in one go.

    What we do One change at a time, each one retested.

  3. 03

    Where it stallsGuessing where time and money go.

    What we do Every step priced from traces first.

How we tune an agent

Profile, tune, hand over

Every before-and-after is measured on the same set of your cases.

  1. 0103

    Profiled from real runs

    We trace real or recorded runs and price each step: model, tokens, tool calls, waits.

    • Cost and latency per step
    • Baseline eval on your cases
    • Costliest steps ranked first
  2. 0203

    Changed one thing at a time

    Cheapest changes go first; any change that lowers the baseline score is rolled back.

    • Prompts and context trimmed
    • Caching and per-step routing
    • Retrieval and tool calls tuned
    On the open 50-scenario benchmark, guideline-executing triage scored 98%, against 44% for a raw LLM.
  3. 0303

    Your team keeps tuning

    Everything lives in your repo with a runbook, so your team tests the next cheaper model.

    • Eval set and routing rules
    • Cost and latency dashboards
    • Runbook for testing models
Engineering in the open

We help build what agentic AI runs on

Open standards, open-source tooling and published research, all public, so you can check our engineering before you hire us.

Shaping agentic AI

The first agentic AI engineering company to join the Agentic AI Foundation

The Linux Foundation formed it around Anthropic's MCP, OpenAI's AGENTS.md and Block's goose. AWS, Google and Microsoft are platinum members. In its own words: “Together, we're shaping the future of agentic AI.”

Open source

We build open-source agent tooling that other engineering teams install

9M+ PyPI downloads
3,900+ GitHub stars
31 public repositories

Framework contributors

When the framework breaks, we fix it at the source

We maintain our own open-source agent framework and contribute fixes to the frameworks our agents run on, through official partnerships with their teams. Breaking changes reach us before they reach your codebase.

Research

Our engineers and PhDs publish peer-reviewed research

Peer-reviewed papers on agent architectures, evaluation and AI security, and an open benchmark anyone can rerun against our results.

Track record

Frontier AI teams now build on what we shipped first

Our client agents were in production before most of today's agent frameworks had a stable release. You get a team that already knows what breaks between a promising demo and a system people rely on every day.

Engagement models

Ways to start

Each path starts with a free call with a founder or senior AI engineer. Changes ship only once they meet the agreed target.

Technology

What we tune with

The model is chosen per step and stays replaceable.

  1. Model Compared on the same eval set
  2. Agent framework Where calls, retries and tools live
  3. Traces and evals Per-step cost, latency and the baseline
  4. Your environment Where the agent already runs

How we choose the stack

FAQ

Agent performance optimization, answered

What does AI agent performance optimization include? +
Profiling from traces, a baseline eval set built from your cases, and changes made one at a time: trimmed prompts and context, caching, model routing per step, batching and fewer tool round trips, plain code in place of steps that never needed a model, and retrieval tuning through chunking, hybrid search and reranking. Each change is rerun on the same eval set. The eval set, routing rules and cost dashboards stay in your repository.
When does an agent need optimization rather than a rebuild? +
When its answers are already useful and the problem is the bill, the wait or the share of answers that miss. If the answers are wrong because the process or the data behind them is wrong, tuning will not fix that, and the profile says so before any work starts.
Will cutting cost lower accuracy? +
It can, so every change runs against the baseline eval set; a change that lowers the score is rolled back. The exception is a trade-off you decide to keep, with the numbers on both sides in front of you.
Do we have to switch models or providers? +
No. Routing sends each step to the smallest model that passes its cases, and that may be the model you use today. The system stays model-agnostic, so hosted and open-weight models can be compared on the same eval set.
What do you need from us to start? +
Access to the agent's code, traces or logs from real runs, and a sample of cases with the answers you expect. If the agent has no tracing yet, we add it first and record a sample.
How do you measure latency and cost? +
From traces: duration, token counts and model for every step, plus the tool calls each step makes. Cost per run is computed from those token counts, split into cached, uncached and reasoning tokens, at your current provider prices, so before and after are priced the same way.
Does it work with any agent framework? +
Yes. Profiling, caching, routing and retrieval tuning apply to agents built with LangChain, LangGraph, LlamaIndex, Pydantic AI or plain code. We tune the framework you already run.
Can our team keep tuning after the engagement? +
Yes. The eval set, the routing rules and the dashboards live in your repository, with a runbook for testing a new model or prompt against the baseline.
Start with the traces

See where your agent's time and money go

Book a call, and we go through a sample of your runs together.