Skip to main content
These twelve tools turn agents running in your sandbox into a marketplace listing other people install in one click. See Create a template for the same workflow in the app.
Expert accounts only. Every tool on this page requires the key to belong to the sandbox of an expert account. The gate says so on the first call. All 45 tools are advertised to every key, so a client will offer these even when your account cannot use them. See the Expert Program.
Two rules every tool here shares. Publication is never the caller’s decision: you write a draft and hand it over. And a template can only be built from sandbox agents, because capturing from a working workspace would publish a client’s memory files.

​
The usual sequence

1

create_template

Create a draft from a title.
2

update_template

Write the copy and set the pricing.
3

plan_template_capture

Dry run the capture and read what it would ship.
4

capture_template_agents

Archive the agents into the template.
5

add_template_image

Add the cover.
6

get_template

Read submitChecklist and fix what is missing.
7

submit_template

Hand it to the Rerun team.

​
list_templates

Lists the templates this account authors, with templateId, slug, title, status, pricing, how many agents are captured, and why a template is no longer editable when it is. Takes no arguments. Call it first: every other template tool takes the templateId it returns. Statuses are draft (yours, editable), in_review (handed over, frozen), published and unlisted (live, maintained by Rerun from then on), and archived.

​
get_template

One template in full: the editorial document, the agents already captured with their key, and submitChecklist, the exact list submit_template enforces with met true or false per item, plus readyToSubmit and missing.
​
string
required
Read it before every update. update_template only touches the fields you pass, so this is how you know what is already written.

​
create_template

Creates an empty draft.
​
string
required
The product name of the template, for example Inbound lead qualifier.
The slug, which is the public URL of the page, is derived from that title and is not editable afterwards. Treat the title as the product name. Nothing becomes public here. A draft stays private until submit_template hands it over and the team approves it.

​
update_template

Writes the editorial page of a draft. Only the fields you pass change.
​
string
required
​
string
​
string
One line, up to about 160 characters. The card subtitle.
​
string
The body of the page, in markdown. This is the page.
​
string
The audience the template is for, not the team that built it. One of agencies, ecommerce, saas, sales, recruiting, real-estate, legal, creators, productivity, other.
​
string[]
Replaces the whole list.
​
number
Honest minutes to install it and connect the accounts. Shown on the page.
​
object[]
Replaces the whole gallery, cover first. Each entry needs url and may carry alt.
​
string
​
object[]
Replaces the whole FAQ. Each entry needs question and answer. Four to six entries reads best, written the way someone types them into a search box.
​
string
Search title, about 60 characters.
​
string
Search snippet, about 200 characters.
​
string
free, one_time (charged once) or recurring (monthly).
​
number
Cents. 0 when free, at least 500 ($5) when paid, up to 200000 ($2,000). Any other combination is refused rather than silently stored.
Three traps. tags, gallery and faq replace the whole list, so passing gallery here drops the images already on the template. A template in review or published is read-only, and withdraw_template is the way back. Status, slug, creator, featured and the visibility flags are not writable.

​
submit_template

Hands a draft to the Rerun team for review.
​
string
required
It enforces the list get_template returns: a title, a tagline, a description, at least one image, at least one captured agent, and for a paid template a Stripe account that can actually receive payouts. It names what is missing instead of half-submitting. It also refuses on a credential found anywhere in the copy. Once it succeeds the template is frozen: still private, no longer editable. withdraw_template is the only way back to a draft.
Payout onboarding cannot happen from here. It needs a browser: in the Rerun app, board toolbar, My templates, Payouts.

​
withdraw_template

Takes a template back from review into draft so it can be edited again.
​
string
required
Only works while it is in_review. Once published, the page is maintained by Rerun and this is refused.

​
delete_template

Permanently deletes a draft. Refused on a template in review or already published.
​
string
required
​
boolean
required
Must be true.

​
list_capture_sources

Lists the Boxes and agents that can be captured: the sandbox only, and only agents the engine actually knows about. Takes no arguments. The agent ids it returns are what plan_template_capture and capture_template_agents take.

​
plan_template_capture

Dry run. Inspects what capturing these agents would ship, without writing anything.
​
string
required
​
string
required
From list_capture_sources.
​
string[]
required
Agent ids from list_capture_sources, in that Box.
Returns, per agent: its skills, scheduled tasks and declared connectors, the .env key names a copy will have to be given again (names only, never values), the MCP servers whose sign-in stays behind, how many memory files it holds, what the engine will redact on the way out, and excludedByDefault, the paths considered too personal to publish.
Read this before capturing. It is the security review, and the archive ends up behind a public install button.

​
capture_template_agents

Captures agents from the sandbox into the template: prompt, skills, scheduled tasks, connector declarations and workspace files are archived, and the template page is rewritten from what the folder actually contains.
​
string
required
​
string
required
​
object[]
required
One entry per agent. Each entry needs agentId and may carry exclude, keep and setup.
​
string[]
Extra paths from plan_template_capture to leave out.
​
string[]
Paths from excludedByDefault to ship anyway. A deliberate act: these are memories and credentials.
​
object
The answer to “does this agent need to be configured after install?”, which a template cannot be submitted without. required is mandatory. prompt is required when required is true, and is addressed to the agent, not to the user.
Paths marked excluded by default (memory, credential folders, the agent database) are left out unless you name them in keep. Do not keep a memory folder without the account owner asking for it. Re-capturing an agent already in the template updates its entry in place, and the editorial copy written about it survives. Read the warnings that come back: they name literal credentials the engine had to strip.

​
remove_template_agent

Removes a captured agent from a template and deletes its archive.
​
string
required
​
string
required
The key get_template returns for each agent, not the sandbox agent id.
​
boolean
required
Must be true.
Connectors no remaining agent uses leave the page with it.

​
add_template_image

Adds one image to the gallery from a URL that is already hosted somewhere public.
​
string
required
​
string
required
Public https URL of a png, jpg or webp.
​
string
What the image shows, one sentence. Read by search engines and screen readers.
​
boolean
Put it first, making it the cover and the social preview.
The bytes are downloaded and re-encoded into Rerun storage, so the gallery never points at a host that can expire or swap the picture after the review. Unlike update_template(gallery) this appends: the images already there are kept. There is no upload and no image generation here. Produce or host the image elsewhere, then pass its https URL.