CursorCursor on Flux

Add checkout, get a second opinion and close the ticket

Cursor adds Stripe checkout to a cart page, has the payment logic checked by another model, and closes the ticket.

Cursor was asked
“Add Stripe checkout to the cart page, get a second opinion on the payment logic, then open a PR and close the ticket.”
  • Page readingLive
  • ModelLive
  • Second opinionShipping
  • AppsShipping
Now playing: Cursor · Add checkout
Your agent
MurageMurage
Wayland
Claude CodeClaude Code
>_Codex
CursorCursor
Hermes AgentHermes
OpenClawOpenClaw
ClineCline
Your app
CursorCursor asks
Add Stripe checkout to the cart page, get a second opinion on the payment logic, then open a PR and close the ticket.
Flux5 jobs done · $0.074
  1. Read the Stripe docs$0.010
  2. ClaudeWrite the integration with Claude$0.038
  3. DeepSeekSecond opinion on paymentsShipping$0.006
  4. Open the pull request on GitHubShipping$0.010
  5. Close ticket CHK-88 on LinearShipping$0.010
PR #219 adds checkout, the second opinion agreed, and CHK-88 is closed.
The best model or tool for each job
Models90+ from 12 AI labs
ClaudeGPTGeminiGrokDeepSeekKimiQwenZhipuMinimaxMistral
Live websearch and read pages
Shipping
Voices61 voices, speak and listen
Shipping
Imagesmake and edit
AppsShippingact with permission
GmailSlackGitHubNotionGoogle CalendarGoogle SheetsLinearShopifyHubSpot
MemoryShippingfollows each user

Examples. Names, prices and costs are illustrative.

What Flux did, step by step

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.

  1. Read the Stripe docsLive

    Page reading

    Flux read the current Stripe docs, so the code matches the API as it is today.

  2. Claude

    Write the integration with ClaudeLive

    Model

    Payment code is worth a frontier model, so Flux sent the writing there.

  3. DeepSeek

    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.

  4. Open the pull request on GitHubShipping

    Apps

    The pull request went through the GitHub connection.

  5. 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.

The receipt

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

Illustrative cost of each step
StepCost
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

Run it with your own agent

  1. Get your key.
  2. Connect Cursor to Flux with flux-auto as the model. Cursor setup
  3. Cursor sends only its chat and plan panel (Cmd/Ctrl+L) through Flux. Agent mode and Composer edits stay on Cursor's own backend, so to run every step of this job on Flux, use Claude Code or Codex.
  4. For page reading and images, add the Flux tools server to Cursor’s MCP settings as a remote HTTP server at 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.
  5. Ask it for the job in your own words, like the ask at the top.

What works today

  • Page readingLivePage reading works today on a paid key. It covers public pages only.
  • ModelLiveModel steps work today, as soon as your agent points at Flux with flux-auto.
  • Second opinionShippingSecond opinion is shipping to every account. Until then, ask your agent to check the payment logic with a second model.
  • AppsShippingApps 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.

Try it with another agent

One key, any agent. If it can talk to OpenAI or Anthropic, it can connect to Flux.

  • Claude Code

    Claude Code

    Claude Code can run the whole job on Flux from the terminal, edits included.

    Set up Claude Code
  • >_

    Codex

    Codex can do the same, on the same key.

    Set up Codex

Questions

Does Cursor run every step here through Flux?

No. 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.

What does the second opinion check?

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.

Does every step work on my key today?

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.

What will it cost me?

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.

Anything to know about Cursor?

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.

Give your agent everything else.

One key for every model and tool in this example.