Models / Relace/ Relace Apply 3

Relace Apply 3

Relace · released Sep 26, 2025

Input: text. Output: text.InputOutput
Type
Closed
Input
$0.85
Output
$1.25
Cached
None held

List price · per 1M tokens · Relace at 256K context · source ↗

Our take

Written Sep 30, 2026

Relace Apply 3 is a hosted-only model for applying edits to existing code, reached through an API rather than downloaded. Nothing here measures how well it does that job, so the sensible move is a trial on work you can check yourself.

Who should pick it

Use it for applying edits to existing code through a hosted API, where the bill is predictable because both listed hosts charge the same rate. Long documents go in whole rather than being split up first. Skip it if you need to run the model yourself, or if you need measured evidence of coding quality before committing.

The case for it

  • Both listed hosts charge the same rate, so picking between OpenRouter and Relace is not a price decision.
  • The request capacity takes long documents whole, though reliable recall across all of it is unverified in our data.

The case against it

  • No benchmark scores are supplied, so the only way to judge it is a trial on work you can check yourself.
  • Neither host carries a measured speed, so price alone will not tell you which one to pick.
00

How good is it?

We hold no score for this model.

So there is no figure here for everyday use, coding, agent work or writing. That is a gap in our data, not a low score.

Where these scores come from →

01

Where to rent it

Prices checked 2 hours ago — each listing carries its own date.

Cheapest published offer

Why this differs from the header. The strip above quotes Relace's own list price; this is the cheapest live offer, whoever is serving it — a reseller undercutting a lab is ordinary commerce, not an error.

per 1M tokens
$0.85 in / $1.25 out
Context served
256K
Throughput
Not measured
Current provider offers with price, context and prompt-privacy answers
ProviderIn / out per 1M tokensContextThroughputTrains on promptsLogs promptsZero retention
OpenRouterOpenRouter's own listing$0.85 / $1.25checked 2 hours ago256Knot measuredUnknownUnknownUnknown
Relacefp8Through OpenRouter$0.85 / $1.25checked 2 hours ago256K128K max reply7175 tok/sNoNoConfirmed

Across the 2 listings we hold: 1 says it does not train on prompts, 0 say they do and 1 does not say. 1 appears in the zero-retention registry we check; the rest are unknown to us.

What each host's API supports

From the parameter list each endpoint publishes. Streaming is omitted: nothing we hold reports it, for any model.

API features per host
ProviderTool callingJSON outputStrict schema
OpenRouterOpenRouter's own listing✗✗✗
Relacefp8Through OpenRouter✗✗✗

Tool calling: 0 of 2 listings say yes, 2 say no. JSON output: 0 of 2 listings say yes, 2 say no. Strict schema: 0 of 2 listings say yes, 2 say no.

02

When we formed this view

Recent changes

Jul 26, 2026ListedListed on LLMap
What movedfirst indexed by our pipeline
Sep 26, 2025AnnouncedRelace Apply 3 announced by Relace

Each date is the day we first saw the change, or the day the maker announced it.

What we do not know about this model yet

  • No independent board has scored it, so we hold no quality figures at all.
  • Nothing we hold says whether an endpoint streams, so we do not show it either way.
  • 1 of 2 listings does not say whether it trains on prompts.
  • We hold no cached-input rate for any of its listings.
  • We hold no batch or off-peak rate for any of its listings.
03

Licence and identifiers

What the licence allowsWe hold no licence record for this model. Inside are the identifiers you need to pull it — its Hugging Face repo where we have one, our slug and a machine-readable card.

Licence

We hold no licence record for this model, and no record of published weights either — so we can neither summarise its terms nor point you at the weights.

Identifiers

Takes in, gives back
Text in, text out
Catalogue slug
relace-relace-apply-3

Machine-readable model card (omc.json) →

Something wrong on this page? Tell us