Answers from the documentation; checking which model is on duty
Hi - I answer from the OpenSmartRoute documentation: routing, the API, plans and quotas, self-hosting. Ask away, or open a support ticket if you need a person.
Grounded in the docs - follow a source before acting on it.
Claude 3 Haiku - Model - OpenSmartRoute
Modelv1.0.0
Claude 3 Haiku
Claude 3 Haiku is Anthropic's fastest and most compact model for near-instant responsiveness. Quick and accurate targeted performance. See the launch announcement and benchmark results [here](https://
Reference model card from the OpenRouter listing - model anthropic/claude-3-haiku. Prices are per million tokens as listed; ratings and installs below are from this marketplace.
Claude 3 Haiku
Claude 3 Haiku is Anthropic's fastest and most compact model for near-instant responsiveness. Quick and accurate targeted performance. See the launch announcement and benchmark results here #multimodal
Facts
Vendor
Anthropic
Context window
200,000 tokens
Max output
4,096 tokens
Input price
$0.25 / 1M tokens
Output price
$1.25 / 1M tokens
Input
text, image
Output
text
Tool calling
yes
Structured outputs
no
Reasoning
no
Open weights
no
Endpoint: https://openrouter.ai/api/v1 (OpenAI-compatible), model anthropic/claude-3-haiku
Use it
Copy one of these into your project. Installing also returns the manifest and these snippets.
# after Install: the listing is in your workspace's routing pool - nothing else to configurecurl-s-X POST https://api.opensmartroute.ai/api/v1/route -H 'Authorization: Bearer $OSR_API_KEY' -H 'Content-Type: application/json' -d '{"text": "...", "plan": true}'# or pin it on the OpenAI-compatible endpoint: {"model": "model-anthropic-claude-3-haiku", ...}
Installed into a catalogue, chosen by a router
Install Claude 3 Haiku and it becomes one more candidate the router can pick - when it fits.
A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.