Relace Search
openrouter/relace-searchمن openrouter · أُصدِر 2025-12-08
Prices in USD per 1M tokens. Unknown means the provider does not publish per-token pricing.
القدرات
Model fit scores
0–100 · higher is betterThese scores reward declared capabilities, context size, price and provider availability — they are not benchmark results. Use them as a directional signal alongside your own evaluation.
Coding49
- Tool calling40/40
- Structured output0/20
- Reasoning0/10
- Context window (100K → 1M)8/20
- Provider availability1/10
Agents51
- Tool calling35/35
- Structured output0/25
- Reasoning0/15
- Output token limit15/15
- Provider availability1/10
JSON / structured output42
- Structured output / JSON mode0/50
- Tool calling20/20
- Temperature control10/10
- Price-friendly for high-volume12/20
Cost efficiency47
- Headline price (log-scaled)47/95
- Has prompt-cache pricing0/5
Long context60
- Context window (100K → 2M)50/90
- Has published price for full window10/10
Production-readiness65
- Number of independent providers5/40
- Has published per-token price20/20
- Context window ≥ 8K15/15
- No data inconsistencies across providers10/10
- Official model (not derivative)15/15
Cost Efficiency Index
Open full calculator →Estimated cost using the recommended provider's headline rate. Each scenario fixes average input/output tokens — the assumptions are shown in the third column.
| Scenario | Cost | Assumption |
|---|---|---|
RAG answer per 1,000 RAG answers | $6.50 < $0.01 per request | 5K input tokens (query + 4 retrieved chunks of ~1K each) and a 500-token answer. Typical SaaS knowledge-base bot. |
Support ticket triage per 10,000 tickets | $13.00 < $0.01 per request | 1K input tokens (ticket body + system prompt) and a 100-token JSON classification reply. High-volume customer support. |
Data extraction per 1,000 documents | $3.50 < $0.01 per request | 2K input tokens (a single document page) and a 500-token JSON extraction. ETL / invoice / form pipelines. |
Code review per 1,000 PRs | $11.00 $0.01 per request | 8K input tokens (diff + surrounding files) and a 1K-token review comment. PR-bot workloads. |
Agent step per 1,000 steps | $13.80 $0.01 per request | 12K input tokens (long-running tool history) and a 600-token tool-call decision. Cost per agent step. |
تفاصيل التسعير
السعر المُوصى به من openrouter · relace/relace-search
متاح لدى 1 مزود
| المزود | معرف نموذج المزود | إدخال / 1M | إخراج / 1M | السياق | تاريخ الإصدار |
|---|---|---|---|---|---|
| OpenRouter openrouter | relace/relace-search | $1.00 | $3.00 | 256K | 2025-12-08 |
Frequently asked questions
How much does Relace Search cost?
Relace Search costs $1.00 per 1M input tokens and $3.00 per 1M output tokens, sourced from openrouter. Cache reads, audio tokens and >200K-context tiers (where applicable) are listed in the Pricing detail block above.
What is the context window of Relace Search?
Relace Search has a context window of 256K tokens, with a max output of 128K tokens per reply. This is the total combined size of prompt + completion.
Does Relace Search support tool calling?
Yes. Relace Search supports tool calling (function calling). This makes it suitable for production agent and automation workloads where the model has to invoke external functions reliably.
Does Relace Search support structured output / JSON mode?
No. Relace Search does not support structured output / JSON-schema-constrained decoding. If your workflow requires it, look at the /capabilities/structured-output list for alternatives.
Can Relace Search accept image input?
No. Relace Search only accepts text as input. If you need image input, see our /capabilities/vision list for current vision-capable models.
Is Relace Search open-weight?
No. Relace Search is a proprietary model — only openrouter (and any approved hosting partners) can serve it. The pricing above reflects the cheapest API access.
What are the best alternatives to Relace Search?
If Relace Search doesn't fit, consider INTELLECT-3, LFM2-24B-A2B, LFM2.5-1.2B-Thinking (free). Each one targets the same use case — see the Related links below for direct head-to-head pages.
Where does this data come from?
All numbers are normalised into a single canonical model record and reconciled with each provider's official documentation. We re-pull daily and write any changes (price, context, capability) to the /changelog page.
Explore more
More openrouter models
- INTELLECT-3$0.20 in / $1.10 out
- LFM2-24B-A2B$0.03 in / $0.12 out
- LFM2.5-1.2B-Thinking (free)Unknown pricing
- LFM2.5-1.2B-Instruct (free)Unknown pricing
- ReMM SLERP 13B$0.45 in / $0.65 out
Capability lists this model is in
آخر تحديث:
Pricing and capabilities are refreshed daily and reconciled against each provider's official documentation. Always verify critical production decisions with the provider directly.