Skip to main content
The local dreamtune research command calls a selected tool and model through MCP. It needs a key and public documentation, not private backend knowledge.

Prerequisites and discovery

Install the CLI, configure its environment, enable tool/model read and run scopes, and add wallet credit.
Choose a real endpoint and exact model ID from the live catalog. Replace the input below with the envelope required by that endpoint’s inspected schema.

Save research.json

maxTotalMinor uses USD millionths: 100000 is USD 0.10. It guards between steps; an individual operation can exceed the remaining allowance. Select inexpensive operations, bound output tokens and use suitable per-key limits.

Execute and review

The workflow checks model limits, inspects the tool, submits the search and reads its result. Pending search work returns saved state rather than a fabricated answer. Completed source material is passed to the model as untrusted content for a cited summary, subject to the workflow’s budget guard. Read the returned stage and IDs. A later failure does not undo earlier billable work. Review cited pages yourself; the output is not a guarantee of correctness.

Recover safely

Keep the file and both keys unchanged. Read saved IDs with tools get and models get. Reusing a key with changed input conflicts; using a new key creates new work. For ongoing work, set session context and use observability. To allow multiple model/tool rounds, follow the agent tutorial.