>_Codex on Flux
Codex turns a week of merged pull requests into release notes with a cover image, then publishes and announces them.
“Write release notes for everything merged this week, make a cover image, publish them and tell the team.”
Examples. Names, prices and costs are illustrative.
Flux split the ask into jobs and sent each one to the model or tool that fits it. It picks among vetted models for each kind of task, cost-aware.
Read 14 merged pull requestsShipping
Apps
Codex needed the week’s merged work, so Flux read the pull requests from GitHub.
Summarise them with DeepSeekLive
Model
Summarising is a light job, so Flux picked a fast, low-cost model.
Make a cover imageLive
Images
The cover image went to an image model, on the same key.
Publish the notes to NotionShipping
Apps
The notes were published through the Notion connection.
Announce them in #generalShipping
Apps
The announcement went to #general through the Slack connection.
Result Release notes for v2.4 are live on Notion and announced in #general.
Every call comes back with the model or tool that ran it and what it cost, all on one bill.
These costs are illustrative, not a quote. flux-auto bills each model step at the Standard rate, or the Fast rate when it sends the step to the Fast lane and a Fast model answers. Never more than Standard. Pin a model and you pay its own rate. See pricing
Example receiptIllustrative
| Step | Cost |
|---|---|
| Read 14 merged pull requestsApps | $0.010 |
| Summarise them with DeepSeekModel | $0.006 |
| Make a cover imageImages | $0.030 |
| Publish the notes to NotionApps | $0.010 |
| Announce them in #generalApps | $0.010 |
| One bill | $0.066 |
https://api.fluxrouter.ai/mcp-tools/, with your Flux key as the bearer token (Authorization: Bearer sk-flux-…). It offers web_fetch to read a page and image_generate to make an image.One key, any agent. If it can talk to OpenAI or Anthropic, it can connect to Flux.
Yes. Put it in the ask, for example “short, plain and for customers”. The model that writes the summary follows it like any other instruction.
Not yet. Apps on your own key are shipping. Until then, your agent can use its own tools for these steps, and Murage runs them today with apps built in. The steps marked Live work today.
The costs on this page are illustrative, not a quote. flux-auto bills each model step at the Standard rate, or the Fast rate when it sends the step to the Fast lane and a Fast model answers. Never more than Standard. Pin a model and you pay that model’s own rate instead. Web, image, voice and app steps have their own prices.
Codex only speaks the Responses API, so wire_api must be "responses". Flux serves it at the same base URL. The provider IDs openai, ollama and lmstudio are reserved. Use a custom ID such as flux.
One key for every model and tool in this example.