Engineering
Check the models in your code every month
Every month, Merlin checks each model id in your code against OpenRouter. You get expiring models and price changes in Slack, and a pull request that moves off anything expiring.
@Merlin on the 1st of every month at 10:00, list every OpenRouter model id in acme/app and look each one up in OpenRouter's public models list. Post here the ones that have an expiration date or are no longer listed, and any whose price changed since last month (keep each month's prices in the model-prices project on your machine). For each expiring model, open a pull request in acme/app that moves it to the closest current model from the same author and runs the tests. Don't merge it: a person reviews it. If you can't reach OpenRouter, say so.
Starts whenOn the
1stof every month at10:00, a monthly Merlin schedule posts to#engMerlin worksClaude Code or Codex lists every model id in acme/app and checks each in OpenRouter's public models list for an expiration date and a price change since last month
- You getThe models expiring or changing price in
#eng, with a pull request that replaces each expiring one
Tools
- Slack
- OpenRouter
- GitHub
Capabilities
- Automations
- Integrations
How it works
From the model ids in your code to a pull request off the expiring ones.
On the 1st of every month at 10:00, the automation you created from
#engstarts a run.Claude Code or Codex finds every model id in
acme/appand looks each one up in OpenRouter. It flags models with an expiration date (the date after which OpenRouter may remove them) or no longer listed, and prices that changed since last month.A post in
#englists what it found and links a pull request that moves each expiring model to the closest current one from the same author. A person reviews and merges it.
On the 1st of every month at 10:00, the automation you created from #eng starts a run.
Claude Code or Codex finds every model id in acme/app and looks each one up in OpenRouter. It flags models with an expiration date (the date after which OpenRouter may remove them) or no longer listed, and prices that changed since last month.
A post in #eng lists what it found and links a pull request that moves each expiring model to the closest current one from the same author. A person reviews and merges it.
Overview
Agents
Skills
Memory
Automations
Integrations
Settings
Check the models in our code
PauseDetailsRun history
Trigger
When Merlin runs it.
Run
What Merlin does each time, where it runs, and where the result goes.
on the 1st of every month at 10:00, list every OpenRouter model id in acme/app and look each one up in OpenRouter's public models list. Post here the ones that have an expiration date or are no longer listed, and any whose price changed since last month (keep each month's prices in the model-prices project on your machine). For each expiring model, open a pull request in acme/app that moves it to the closest current model from the same author and runs the tests. Don't merge it: a person reviews it. If you can't reach OpenRouter, say so.
Before and after
Expiring models get replaced before they go, not after calls start failing.
Without Merlin
Someone remembers to audit the model ids now and then, looks each one up and makes the swap by hand.
- 01Search the code for model ids
- 02Look up each model
- 03Check for an expiration date
- 04Compare prices with last month
- 05Pick a replacement
- 06Change the model id
- 07Run the tests
- 08Open a pull request
- 09Post the findings in #eng
With Merlin
A monthly schedule catches expiring models early, and a person reviews the move.
- Day 1 of every month at
10:00Monthly Merlin schedule in #eng Checks each model id on Omar's MacBookOpenRouter and the code
- Pull request for expiring modelsLinked in #eng with any price changes
Setup
Give your agent OpenRouter and the code, then schedule the check from #eng.
Set these up once and the check runs on the 1st of every month. Merlin never merges, so a person reviews every model change.
- 01Connect a machineRuntimeInstall the Merlin desktop app or CLI on a computer running Claude Code or Codex. You can also use a machine a teammate shares with your workspace.
- 02Add Merlin to SlackIntegrationsInstall the Slack app and add Merlin to the channel you work in. A private channel needs
/invite @Merlin. - 03Keep OpenRouter on your agentOptionalYour agent's MCPIf your machine's agent already uses the OpenRouter MCP server, Merlin can use it here too. You don't need to set up anything in Merlin.
- 04Install the GitHub appIntegrationsPick the repositories Merlin can access, so it can read and link the pull requests there. Pushes use the machine owner's own Git access.
- 05Keep your code on the machineRuntimeMerlin reads the code in a local project on the runtime, so keep the repository checked out there.
- 06Send the prompt from the machine with the codeRuntime
Runs prefer the machine recorded when the automation is created (choose a runtime), so send it from the one with
acme/appchecked out. Merlin keeps each month's prices in a local project there, and the first run posts the current prices as the starting point. - 07No OpenRouter key neededYour agent's MCP
The run reads OpenRouter's public models list, which has every model's price and expiration date, so it doesn't depend on the 7-day key OpenRouter's MCP server mints.
- 08Paste the setup promptAutomationsSend the prompt below to @Merlin in Slack, in the channel it should post to. Merlin creates the automation and tells you what it set up.
Prompt
Schedule the monthly model check with one message in #eng.
@Merlin on the 1st of every month at 10:00, list every OpenRouter model id in acme/app and look each one up in OpenRouter's public models list. Post here the ones that have an expiration date or are no longer listed, and any whose price changed since last month (keep each month's prices in the model-prices project on your machine). For each expiring model, open a pull request in acme/app that moves it to the closest current model from the same author and runs the tests. Don't merge it: a person reviews it. If you can't reach OpenRouter, say so.
Once, when you send it
- PromptYou send the prompt to @Merlin
- AutomationMerlin creates the automation
Every scheduled run
- ScheduleThe schedule starts a run
- RuntimeMerlin picks the creator's machine first
- ContextThe run gathers context
- WorkClaude Code or Codex checks each model in OpenRouter
- ResultMerlin posts what changed and links the pull request
- SteeringReplies in its thread follow up
Related use cases
More engineering tasks you can hand to Merlin.
- IntegrationsYour agent's MCP
Engineering
Try a cheaper model before switching
Delegate a model change to Merlin in Linear. It runs the feature's eval cases on cheaper models through OpenRouter and opens a pull request with the comparison, or says none held up.
Model issue delegated to MerlinA pull request with the comparison, on the issue - Integrations
Engineering
Upgrade a dependency and fix what breaks
Delegate a dependency upgrade to Merlin in Linear. It bumps the version, fixes the breaking changes and opens one pull request linked on the issue.
Upgrade issue delegated to MerlinOne pull request, linked on the issue - IntegrationsYour agent's MCP
Engineering
Find out why an LLM call failed
Mention Merlin in Slack with an OpenRouter generation id from your logs. You get why the call failed and the fix it would make, from the generation, its providers and your code.
@Merlinin#engwith a generation idThe cause and a fix, in the thread
Bring your coding agents into the tools your team already uses.
Let your whole team hand work to Claude Code and Codex today. Connect one machine and add Merlin to Slack, Linear or GitHub. 14-day free trial, no API keys, no card.