Cursor on Flux
Cursor adds Stripe checkout to a cart page, has the payment logic checked by another model, and closes the ticket.
“Add Stripe checkout to the cart page, get a second opinion on the payment logic, then open a PR and close the ticket.”
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 the Stripe docsLive
Page reading
Flux read the current Stripe docs, so the code matches the API as it is today.
Write the integration with ClaudeLive
Model
Payment code is worth a frontier model, so Flux sent the writing there.
Second opinion on paymentsShipping
Second opinion
Money logic gets a second look. Flux checks the answer with another model and stops at a fixed cost cap.
Open the pull request on GitHubShipping
Apps
The pull request went through the GitHub connection.
Close ticket CHK-88 on LinearShipping
Apps
The ticket was closed through the Linear connection.
Result PR #219 adds checkout, the second opinion agreed, and CHK-88 is closed.
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 the Stripe docsPage reading | $0.010 |
| Write the integration with ClaudeModel | $0.038 |
| Second opinion on paymentsSecond opinion | $0.006 |
| Open the pull request on GitHubApps | $0.010 |
| Close ticket CHK-88 on LinearApps | $0.010 |
| One bill | $0.074 |
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.
Claude Code
Claude Code can run the whole job on Flux from the terminal, edits included.
Set up Claude CodeNo. Cursor's chat and plan panel runs its model steps through Flux, but agent mode and Composer edits stay on Cursor's own backend. To run the whole job on Flux, including the edits, use Claude Code or Codex with the same key.
The answer your agent is about to act on. Flux checks it with other models first, and the check stops at a fixed cost cap, so it never runs away with your budget.
Not yet. Second opinion is shipping to every account. Until then, ask your agent to check the payment logic with a second model. 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.
Only Cursor's chat and plan panel (Cmd/Ctrl+L) uses the custom endpoint. Composer, agent mode, inline edit, apply and tab autocomplete stay on Cursor's own backend.
One key for every model and tool in this example.