OpenRouter key usage brief
Read-only OpenRouter workflow for reviewing the current API key label, spending limit, remaining budget, usage counters, and current text-model inventory. It does not require the management-only credits endpoint and does not create completions, manage keys, mutate workspaces, or call arbitrary OpenRouter routes.
How it works
Inspect the data fetches, transforms, gates, and output this recipe runs.
Process (7 steps)
key
?
model_count
?
models
?
model_rows
slice
Take a subset of
model_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.
focus
setting
=
Summarize current OpenRouter key usage, remaining limit, BYOK usage, and the available model count. Highlight budget risk without inventing data outside the API response.
max length
setting
=
700
openrouter
setting
=
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.