Skip to content
Recued
Menu
← Back to recipes

OpenRouter key usage brief

by recued-core v1

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 7 steps

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 4 configurable

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.

Where it runs

Device + server Runs on your device (browser) or your server.

Permissions it requires

Read your Openrouter connection
Declared by the recipe — Recued grants these at install, where you review them before approving.

About

Tags

openrouter openrouteraiusagecost-reviewapi-keymodelspack:openrouter

Details

7 steps 4 configurable settings recipe_id: openrouter-key-usage-brief