OpenRouter Models API
Fields: identity, description, modalities, context window, maximum output, pricing, supported parameters
The relace-search model uses 4-12 view_file and grep tools in parallel to explore a codebase and return relevant files to the user request. In contrast to RAG, relace-search performs agentic…
- Context
- 256K
- Max output
- 128K
- Input
- $1
- Output
- $3
Recommended use cases
Strengths in this dataset
- 256,000-token context window
- text input
- 8 supported API parameters listed
Limits and caveats
- Provider behavior and pricing can change; verify the linked sources before production use.
Capability
Model-native facts
Model- Reasoning
- Unknown
- Open weights
- Unknown
Provider endpoint facts
Provider endpoint- Tool calling
- Supported
- Structured output
- Supported
- Streaming
- Unknown
- Prompt cache
- Unknown
- Batch
- Unknown
- Fine-tuning
- Unknown
Relace Search Provider pricing
Provider endpoint: relace/relace-search
- Input
- $1 per 1M tokens
- Output
- $3 per 1M tokens
- Cached input
- Unknown per 1M tokens
- Image output
- Unknown per 1M tokens
Sources and verification
Frequently asked questions
Answers are generated from the same sourced model and provider facts shown above.
The relace-search model uses 4-12 view_file and grep tools in parallel to explore a codebase and return relevant files to the user request. In contrast to RAG, relace-search performs agentic…
Model specifications and prices may vary by provider and change over time. AIToolly displays sources and verification dates so users can confirm critical details before production use.