models · subscription runtime

Run on the subscription
you already pay for.

You already pay for Claude Pro or Max. DISPATCH lets that subscription drive the canvas directly — over MCP and a sub‑authed CLI — instead of metering every node against pay‑as‑you‑go API credits. No API key. No second bill.

Testing via MCP Sub-authed CLI No API key

what it is

Your subscription is the runtime.

DISPATCH publishes the graph over MCP. Your subscription‑authed CLI attaches as the client, executes each node under your existing Claude Pro/Max entitlement, and writes results back. The canvas never sees a key, because there isn't one.

Since it's just another transport, funding is per node. An Investigate node can run on your Max seat while Create hits a local model and Evaluate stays on a metered API — same graph, three sources, one Run.

no key

Zero API credits

The run is driven by your seat's entitlement, not a pay‑per‑token key you have to top up.

transport

Canvas over MCP

Nodes, prompts, tools and context are published as an MCP surface the CLI can drive.

client

Sub-authed CLI

You sign in once with the CLI you already use; DISPATCH hands it nodes to execute.

mixed

Per-node funding

Subscription, local, or metered API — choose per node. One graph, mixed sources.

interactive · funding source

Flip the source. Press Run.

Switch the canvas between a metered API key and your Claude Max subscription, then run the chain. Watch the meter: same nodes, different bill.

canvas runtime idle

driving the graph

claude (sub-authed CLI)

Connected over MCP · executes nodes on your Claude Max seat.

auth: subscription session · no key

subscription · included $0.00

The subscription runtime drives the run end‑to‑end. No metered credits are drawn.

MCP

executing on canvas

Initialisertrigger

Investigateweb_search

Planreason

Createdraft

Reviewgate

dispatch · subscription session

sub-auth

how it works

Publish the canvas. Let the seat drive.

No key vault, no proxy reselling tokens. Three steps, once per session.

Expose over MCP

DISPATCH publishes the graph as an MCP server: each node's prompt, allowed tools (web_search, read_file, write_file) and the shared Context bus.

Connect the sub-authed CLI

Your Claude CLI signs in once with its own subscription session and attaches as the MCP client. No API key is generated, stored, or passed to the canvas.

The seat executes nodes

On Run, the canvas hands each node to the CLI, which executes it under your entitlement and writes the output back downstream — exactly like a metered node would.

related features

Activeper node