Skip to content
Model infoModelsSnapshot: 15 Oct 2026

Relace / Relace

Relace Search

Code-search model trained to inspect repositories through parallel tool calls.

Search & retrieval
availableClosed weightsRetrieval
Official documentation (opens in a new tab)Reviewed 15 Oct 2026
9 of 16 specification fields collected
Context window256K256,000 tokens
Maximum output128K128,000 tokens
Input / 1M tokens$1.00OpenRouter · Relace
Output / 1M tokens$3.00USD · observed 15 Oct 2026

Specifications

Provider-documented facts. “Not collected” means we have not verified that field yet, not that the feature is unsupported.

Context / input limit
256,000 tokensSource for Context / input limit (opens in a new tab)

OpenRouter route context; direct endpoint limits may differ.

Maximum input tokens
Not collected

No exact model-specific contract established. Unknown is not unsupported.

Maximum output
128,000 tokensSource for Maximum output (opens in a new tab)
Parameters
Not collected

No exact model-specific contract established. Unknown is not unsupported.

Release date
2025-12-08Source for Release date (opens in a new tab)
Knowledge cutoff
Not collected

No exact model-specific contract established. Unknown is not unsupported.

Reasoning
SupportedSource for Reasoning (opens in a new tab)

Training traces include reasoning between tool calls; no configurable effort setting established.

Tool calling
SupportedSource for Tool calling (opens in a new tab)
Structured output
Not collected

No exact model-specific contract established. Unknown is not unsupported.

Streaming
SupportedSource for Streaming (opens in a new tab)
Batch processing
Not collected

No exact model-specific contract established. Unknown is not unsupported.

Fine-tuning
Not collected

No exact model-specific contract established. Unknown is not unsupported.

Context caching
Not collected

No exact model-specific contract established. Unknown is not unsupported.

Input modalities
TextSource for Input modalities (opens in a new tab)
Output modalities
TextSource for Output modalities (opens in a new tab)
Published training method
On-policy reinforcement learning rewarding file relevance and fewer sequential turns.Source for Published training method (opens in a new tab)

Access & pricing

Prices belong to an endpoint and billing tier. A provider listing does not guarantee access for every account or region.

OpenRouter · Relace

Provider source (opens in a new tab)
API model ID
relace/relace-search
Access
Available in the serving platform catalogue. Requires a funded API account; no inference was run.
Regions
Serving-region inventory not established.
API endpoint
POST https://openrouter.ai/api/v1/chat/completionsSource for API endpoint (opens in a new tab)
Context / input limit
256,000 tokensSource for Context / input limit (opens in a new tab)

Route-specific combined context.

Maximum output
128,000 tokensSource for Maximum output (opens in a new tab)
Context caching
Not supportedSource for Context caching (opens in a new tab)

Implicit caching flag for this route only; does not establish direct API cache behavior.

INPUT / 1M TOKENS$1.00
OUTPUT / 1M TOKENS$3.00

Current OpenRouter route tariff. Not the direct Relace API tariff; account charges and gateway terms are separate. Cached input price: not collected.

USD · observed 15 Oct 2026 · Pricing evidence (opens in a new tab)

Data & enterprise terms

Relace upstream policy does not establish OpenRouter gateway retention or account settings. Review both parties before sending sensitive content.

Relace API

Provider source (opens in a new tab)
API model ID
relace-search
Access
Caller runs the agent loop and executes returned tools.
Regions
Serving-region inventory not established.
API endpoint
POST https://models.relace.ai/v1/search/chat/completionsSource for API endpoint (opens in a new tab)
Tool calling
SupportedSource for Tool calling (opens in a new tab)
Streaming
SupportedSource for Streaming (opens in a new tab)

Prices retain their published currencies and billing units below.

Published billing units · original currency · observed 15 Oct 2026
CategoryUsageRateUnit
Historical indexed pricingInput tokens1$1.001M tokens
Historical indexed pricingOutput tokens1$3.001M tokens

Rate conditions

  1. Older indexed pricing page. Current live pricing no longer lists this model, and the authenticated model catalogue was not accessible. Not used as a current quote.
Pricing source (opens in a new tab)

Data & enterprise terms

API prompt and output content is processed in volatile memory, with short-lived KV caching. It is not persisted or used for training/evaluation. Billing and usage metadata is retained; Jacq and other products are outside this policy. Written agreements may differ.

Read the service policy (opens in a new tab)

Relace API

Provider source (opens in a new tab)
API model ID
relace-search
Access
Same model on the shared chat route, not an independent model.
Regions
Serving-region inventory not established.
API endpoint
POST https://models.relace.ai/v1/chat/completionsSource for API endpoint (opens in a new tab)

Endpoint pricing has not been collected. Check the provider for applicable rates.

Data & enterprise terms

API prompt and output content is processed in volatile memory, with short-lived KV caching. It is not persisted or used for training/evaluation. Billing and usage metadata is retained; Jacq and other products are outside this policy. Written agreements may differ.

Read the service policy (opens in a new tab)

Caching

Caching can reuse earlier input processing. Availability, lifetime and billing depend on the endpoint. A cache hit still generates a new response.

01 / INITIAL INPUTProcess & retain

The system processes eligible input and retains reusable state.

02 / LATER REQUESTCheck available state

Reuse depends on matching input, session state and the cache policy.

03 / CACHE HITReuse & generate

Reusing state can reduce repeated work. Any charges follow the billing rules below.

OpenRouter · Relace

relace/relace-search
Not supported

Serving route reports no implicit caching; explicit cache controls are not established.

Support evidence (opens in a new tab)Caching reviewed 15 Oct 2026

Relace API

relace-search
Not verified

No model-specific cache support or discounted cache tariff established.

How it works
Platform policy describes volatile-memory prefix KV caching. Exact model-specific eligibility is unverified.Source for How it works (opens in a new tab)
Minimum reusable input
Not collected

No model-specific cache support or discounted cache tariff established.

Lifetime & refresh
Evicted after inactivity or memory pressure; no numeric TTL guaranteed.Source for Lifetime & refresh (opens in a new tab)
How to enable it
Not collected

No model-specific cache support or discounted cache tariff established.

Usage fields
Not collected

No model-specific cache support or discounted cache tariff established.

Billing rules
Not collected

No model-specific cache support or discounted cache tariff established.

Limits & data boundaries
API content only; billing metadata and other products are excluded from zero-retention scope.Source for Limits & data boundaries (opens in a new tab)

No verified cache rate for this endpoint. An empty rate is not a zero charge.

Caching reviewed 15 Oct 2026

Relace API

relace-search
Not verified

No model-specific cache support or discounted cache tariff established.

How it works
Platform policy describes volatile-memory prefix KV caching. Exact model-specific eligibility is unverified.Source for How it works (opens in a new tab)
Minimum reusable input
Not collected

No model-specific cache support or discounted cache tariff established.

Lifetime & refresh
Evicted after inactivity or memory pressure; no numeric TTL guaranteed.Source for Lifetime & refresh (opens in a new tab)
How to enable it
Not collected

No model-specific cache support or discounted cache tariff established.

Usage fields
Not collected

No model-specific cache support or discounted cache tariff established.

Billing rules
Not collected

No model-specific cache support or discounted cache tariff established.

Limits & data boundaries
API content only; billing metadata and other products are excluded from zero-retention scope.Source for Limits & data boundaries (opens in a new tab)

No verified cache rate for this endpoint. An empty rate is not a zero charge.

Caching reviewed 15 Oct 2026

What the measurements say

No benchmark observations have been added for this model. We do not turn a vendor description into a performance score.

Latency and throughput depend on the host, request size, reasoning settings and load. There is no measured speed or global usage figure in this record.

The record behind the model

Why it is included

Provider describes its own trained specialized models, delivered through licensed API services whose IP is retained. The training-method article does not release model weights; the API schema MIT label applies to the schema, not the model.

Classification evidence (opens in a new tab)

Sources reviewed