OpenRouter model routing brief
Read-only OpenRouter workflow for comparing candidate models, provider metadata, model counts, and zero-data-retention endpoint availability. It does not create completions, manage API keys, mutate guardrails or workspaces, use files, enable tools/plugins, or call arbitrary OpenRouter routes.
How it works
Inspect the data fetches, transforms, gates, and output this recipe runs.
Process (12 steps)
models
?
model_count
?
providers_raw
?
zdr_endpoints_raw
?
model_rows
slice
Take a subset of
provider_rows
slice
Take a subset of
zdr_rows
slice
Take a subset of
model_table
to_table
Format results as a data table
provider_table
to_table
Format results as a data table
zdr_table
to_table
Format results as a data table
summarize
?
card
to_summary
Format results as a summary card
Settings
Configurable at install. Defaults shown — change them anytime in Recued.
sort
setting
=
most-popular
focus
setting
=
Compare model choices for the requested use case, including context window, pricing, provider diversity, zero-data-retention availability, and practical routing caveats. Do not invent model capabilities not present in the OpenRouter payload.
query
setting
=
max price
setting
=
10
max length
setting
=
900
openrouter
setting
=
provider filter
setting
=
input modalities
setting
=
text
output modalities
setting
=
text
Trust & control
What installing this recipe would let it do. Recued grants these permissions at install — review them there before approving.