All models/ Relace / Instant Apply · legacy Relace / Relace
Instant Apply · legacy Earlier Relace Instant Apply model family documented before Apply 3.
deprecated Closed weights Coding
Context window Not collected Awaiting source review
Maximum output Not collected Awaiting source review
Input billing Not collected Relace API
Output billing Not collected No inferred price
Specifications Access & pricing Caching Evaluation Sources & lifecycle
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 collectedNo 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 INPUT Process & retain The system processes eligible input and retains reusable state.
02 / LATER REQUEST Check available state Reuse depends on matching input, session state and the cache policy.
03 / CACHE HIT Reuse & generate Reusing state can reduce repeated work. Any charges follow the billing rules below.
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 Sources reviewed Model notes Seven current, historical and managed records reviewed. Current routing prices are separated from older direct tariffs. Exact legacy identities and account-specific availability remain open.
The May 25, 2025 announcement reports a faster deployment, but supplies no exact revision selector or parameter count. This family record does not invent separate v1/v2 checkpoints.
The Apply 3 article dates the first public release to a year before October 29, 2025. Exact original API identity still requires evidence.
Check against your workload Try representative inputs, measure task success and total cost, then check the exact endpoint’s data policy.
Read our methodology
Also from Relace Relace Apply 3 Relace Search Relace Compact Relace Embed v1 Relace Rank Fast Agentic Search · hosted