Build a plan and point to the repo generator
onchain_agent_scaffold_planUSE WHEN a plan has been agreed and the next question is which repository to start from. Builds the plan (same brain as onchain_agent_build_plan) and returns it with a create pointer to onchain_agent_create_agent, which generates the runnable repo from a nightly-checked template. This tool no longer writes repository files: every door (this server, POST /api/create, the CLI and the Agent Architect) downloads the same repo from the same engine.
WHAT COMES BACK: the plan summary (goal, intent, chain, plan_url, checked_at, stack slugs), the environment names the stack's own deploy specs ask for, any documented install that pipes a remote script into a shell (quarantined_installs, to read before running it), and create: the tool name, the CLI command and the template the goal maps to, or null when no template answers it.
KEPT FOR COMPATIBILITY: files is an empty list and bytes is 0; include_zip is accepted and ignored. mode is "plan_only".
RULE ENFORCED: nothing is generated. Every value is a field of the plan. An install line we were not told is never invented.
NON-CUSTODIAL: nothing here holds keys, signs, deploys or moves anything.
Returns (json): { mode: "plan_only", name, files: [], env_names, quarantined_installs, bytes: 0, plan: { goal, intent, chain, plan_url, checked_at, stack_slugs }, caveat, create: { tool, command, template, note } }.
Example: { goal: "a Base trading agent that swaps USDC to ETH on a signal", chain: "Base" }
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| goal | Yes | What the user wants to build, in plain words. The plan is built and the matching create_agent template is named. | |
| chain | No | Chain the agent runs on, e.g. 'Base'. When omitted it is read from the goal. | |
| budget_usd | No | Rough monthly budget in USD. Restated in the plan; it does not filter the stack. | |
| constraints | No | Hard constraints to restate back, e.g. 'self-custody only'. | |
| include_zip | No | Accepted for compatibility and ignored: this tool is plan-only. The repo comes from onchain_agent_create_agent. | |
| response_format | No | Text format; structuredContent is JSON either way. | markdown |