Relace Search API256K context

Pricing & specs mirror our live pricing as of July 2026 (pay-as-you-go).

What is 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...

Relace Search pricing

Pay-as-you-go on DataLLM Lab — these are our live list prices (identical to the pricing page):

On output price, Relace Search is cheaper than 34% of the 309 models in the catalog.

What Relace Search costs per month

Cost = input price × input volume + output price × output volume. The same five workloads run on every model page, so any two compare directly.

Relace Search vs alternatives

When not to use Relace Search

• It is served by a single provider, so there is less failover headroom during an outage.

Specs

How to call Relace Search

Copyfrom openai import OpenAI
client = OpenAI(base_url="https://api.datallmlab.com/v1", api_key="YOUR_DATALLM_LAB_KEY")
resp = client.chat.completions.create(
    model="relace/relace-search",
    messages=[{"role": "user", "content": "Hello"}],
    # supports tools=[...] and tool_choice
)
print(resp.choices[0].message.content)

Copycurl https://api.datallmlab.com/v1/chat/completions \
  -H "Authorization: Bearer YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{"model":"relace/relace-search","messages":[{"role":"user","content":"Hello"}]}'

Copyimport OpenAI from "openai";
const client = new OpenAI({ baseURL: "https://api.datallmlab.com/v1", apiKey: process.env.DATALLM_KEY });
const r = await client.chat.completions.create({
  model: "relace/relace-search",
  messages: [{ role: "user", content: "Hello" }],
});
console.log(r.choices[0].message.content);

The same key routes Relace Search and 300+ other models — switch models by changing one string. How OpenAI-compatible APIs work.

Prompting tips for Relace Search

• Be explicit and show the shape of the answer. Spell out format, tone and constraints up front, and include one short example of the output you want — Relace Search follows concrete instructions better than abstract ones.
• Huge 256K context — but anchor the ask. You can paste whole documents or codebases; models attend most to the start and end, so put the key instruction at the top and restate it after long inputs.
• Give it real tools. Pass a tools=[...] schema instead of asking it to "pretend" — let Relace Search emit tool calls, execute them, and feed results back for the next turn.
• Constrain JSON with a schema. Use response_format / structured outputs rather than "reply in JSON" to get valid, parseable objects every time.

Tips are derived from Relace Search's actual capabilities — context window, tool & JSON support, modality and price tier — not generic advice.

Open-source tools for Relace Search

Popular open-source frameworks and agents to build with Relace Search over the API — star counts pulled from GitHub (July 2026).

Listed by GitHub stars; inclusion is by ecosystem relevance (agent frameworks, SDKs and gateways), not affiliation. Stars change — see each repo for current numbers.

Migrating to Relace Search

Coming from OpenAI or another gateway? On an OpenAI-compatible setup the only changes are base_url → https://api.datallmlab.com/v1 and model → relace/relace-search. Messages, streaming, tool calls and the rest of your code stay the same. Routing & failover guide.

Rate limits & reliability

Rate limits here are the DataLLM Lab gateway's, not the upstream vendor's. On 429 (rate limited) or 503 (provider busy), retry with exponential backoff. See the error-code guide and failover setup.

Related reading

Frequently asked questions