Relace: Relace Search

relace/relace-search

The relace-search model uses 4-12 view_file and grep tools in parallel to explore a codebase and return relevant files to the user request.

In contrast to RAG, relace-search performs agentic multi-step reasoning to produce highly precise results 4x faster than any frontier model. It's designed to serve as a subagent that passes its findings to an "oracle" coding agent, who orchestrates/performs the rest of the coding task.

To use relace-search you need to build an appropriate agent harness, and parse the response for relevant information to hand off to the oracle. Read more about it in the Relace documentation(opens in new tab).

Modalities

In / Out Price

Avg

$1 / $3per 1M

Context

High

256K

Released

Dec 8, 2025

Providers

This model is hosted by one provider. OpenRouter forwards every request to it directly — no routing decisions to make.

Performance

Throughput is how fast the model writes (tokens per second — higher is better). Latency is total round-trip time (lower is better). TTFT is time-to-first-token — how long before you see anything appear (lower is better).

Pricing

List price is the headline rate per million tokens. Effective price is what you actually pay after prompt caching is applied — for repeated context, this can be 60–80% cheaper. The chart below shows the rolling effective price over the past 30 days.

Apps

Public apps that send the most traffic to this model. Good signal for what real production workloads look like — and a hint at which use cases this model is best suited for.

Activity

Token volume and request traffic to this model over time.

Uptime

Percent of requests that succeeded over the last 30 days. OpenRouter monitors every provider continuously and automatically retries on the next-best provider when one returns an error.

Quick Start

Drop-in code to call this model. OpenRouter's API is OpenAI-compatible — most SDKs work by just swapping the base URL. The only thing that changes between models is the model slug below.