Skip to content
Model infoModelsSnapshot: 15 Oct 2026

Relace / Relace

Instant Apply · legacy

Earlier Relace Instant Apply model family documented before Apply 3.

deprecatedClosed weightsCoding
Official documentation (opens in a new tab)Reviewed 15 Oct 2026
2 of 15 specification fields collected
Context windowNot collectedAwaiting source review
Maximum outputNot collectedAwaiting source review
Input billingNot collectedRelace API
Output billingNot collectedNo inferred price

Specifications

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

Context / input limit
Not collected

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

Maximum input tokens
Not collected

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

Maximum output
Not collected

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

Parameters
Not collected

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

Release date
Not collected

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

Knowledge cutoff
Not collected

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

Reasoning
Not collected

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

Tool calling
Not collected

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

Structured output
Not collected

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

Streaming
Not collected

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

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.

Access & pricing

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

API model ID
Not collected

No confirmed raw API selector for this historical model or managed workflow.

Access
Earlier versions deprecated in current Apply documentation.
Regions
Serving-region inventory not established.

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

Data & enterprise terms

Retention, training use, regional processing and enterprise terms have not been summarized for this endpoint.

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.

Relace API

Not verified

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

How it works
Not collected

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

Minimum reusable input
Not collected

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

Lifetime & refresh
Not collected

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

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
Not collected

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

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

Caching reviewed 15 Oct 2026

What the measurements say

Apply throughput · historical provider report

Relace · provider-reported
4300tokens/s

May 2025 optimized speculative-decoding deployment; varies with edit complexity. Not a current API SLA.

Evaluation source (opens in a new tab)

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)

Lifecycle dates

Faster Instant Apply deployment announced25 May 2025Source (opens in a new tab)

Sources reviewed