Templates, workflows and other starting points

Studio offers several ways to start an agent. This page explains the difference between template agents and workflows, how to duplicate the workflow template, and what the assistant, package import and Record & replay produce. It is for creators deciding where to begin.

Choose a starting point#

Template agents or workflows#

Template agents are the fixed first-party kinds. Their graph, tools, input form and report format are set by the platform; you choose the name, the description, the analysis networks, the read limits and, for some kinds, optional reads and an AI-assisted summary. Each kind has its own platform-selected test cases, so a template agent can complete operator review and earn the "Tested on listed cases" badge.

Workflows are your own graphs built from approved read-only tools, conditions, transforms and report sections. They can cover far more ground (about fifty approved tools on Solana, Ethereum, Base and Robinhood Chain), but today they are published as "Creator test only" because their platform checks cannot pass yet (see Review and the badge).

Use a template agent when one of the fixed kinds already answers the question you sell. Use a workflow when you need your own combination of reads, checks and sections.

Template agents#

Open Templates (/studio/build). The left column lists Start from a template and Your drafts. Choose a template, fill in the form and choose Save draft or Save & test.

Every template form has:

• Agent name (up to 100 characters) and What this agent does (up to 2,000 characters).
• Maximum blockchain calls (1 up to the template's maximum above). "Lower limits can leave a report incomplete."
• Time limit · seconds (1 to 60). "The worker stops when this limit is reached."
• Current template coverage: a plain statement of what the kind reads and what it does not.
• Advanced package definition: the full package JSON. While it is open, the JSON takes priority over the form. Only supported, declared tools can run.

Watchtower versions are not sold as listings from Studio. Save & test on a Watchtower draft opens monitor creation instead, and Studio notes that "Operator review, listings and purchase do not accept Watchtower versions."

Duplicate the workflow template#

The builder offers one first-party workflow template, Token metadata snapshot (Apache-2.0, by AGENTEX). It reads an ERC-20 token's name, symbol, decimals and total supply on Ethereum or Base, formats the supply exactly and reports it.

1. In the workflow builder, choose Start from a permitted template. (The same list is under Duplicate a permitted template at the bottom of Versions.)
2. Edit Name for Token metadata snapshot copy if you want another name.
3. Tick "I accept the Apache-2.0 licence and attribution terms for Token metadata snapshot." The terms read: "Duplicating copies the workflow into your private draft with attribution to its source. Per-run fees pay for platform execution of hosted agents; AGENTEX does not collect, enforce or promise royalties on copied workflows used outside the platform."
4. Choose Duplicate Token metadata snapshot. The copy opens in the builder as your private draft.

The copy records an attribution line (shown under Attribution in Settings) and starts with private rights: only you run it, its source is private and forking is not permitted. You can change the rights in Settings. You become the owner of the copy; duplicating never transfers ownership or royalties.

The assistant#

The assistant (/studio/assistant) drafts a workflow proposal from a plain-language description. It uses only the approved read-only tools, cannot invent tools or data sources, and never saves or publishes anything.

1. Describe the workflow under Describe the workflow you want (8 to 4,000 characters), or choose one of the examples under Try an example.
2. Choose Propose workflow. The result is one of: "Valid proposal, ready for your review", "Proposal needs edits before it validates", "Nothing in this request is supported by the approved tools", "The model declined this request" or "No proposal was produced". Parts it cannot serve are listed under Not supported, left out.
3. Choose Open in editor to review (or Open in editor to fix). The proposal opens as an editable copy in the same builder, with its permissions and estimated cost.
4. Edit it, give it an Agent name, tick "I reviewed the tools, chains, permissions and estimated cost of this workflow." and choose Save reviewed draft.
5. Choose Continue in the workflow builder to carry on.

Each request is metered against a daily per-account limit, and the proposal shows what it cost. When the limit is reached you see "You reached the daily workflow assistant request limit. Edit the workflow directly or try again later."

Import an SDK package#

The published agentex-creator-sdk npm package can scaffold, validate, test and pack a Token Researcher package on your own machine. Import accepts Token Researcher packages only; workflows are built in Studio.

npm install agentex-creator-sdk
npx agentex scaffold --id my-agent --name "My agent" --chains base --out manifest.json
npx agentex validate --file manifest.json
npx agentex test --file manifest.json
npx agentex pack --file manifest.json --out package.json

1. Open Import package (/studio/import).
2. Choose Choose a package JSON file (up to 64 KiB) or paste the JSON under Or paste package JSON.
3. Choose Inspect package and check the networks, blockchain call limit and time limit it shows.
4. Choose Import private version. You become the owner of a private draft and its first test version. Importing does not grant first-party status or approve a listing.
5. Follow Run a private test, then review and publish as for any template agent.

A package holds data only: it cannot install code or bring wallet sessions, provider keys or network endpoints. You can import up to 20 packages per day. See the SDK for the full toolkit.

Record & replay#

Record & replay (/studio/record) turns a demonstration you run in Studio into an agent. It records only the actions you explicitly run on the page: "The recorder never watches your desktop, other tabs, clicks, keystrokes, logins, cookies or wallet, and never replays your session for buyers."

There are two recording modes.

Record tool steps and public pages#

This mode compiles into a workflow.

1. Enter a Recording name and tick the Chains (Ethereum, Base or Robinhood Chain).
2. Optionally list Declared public sites: "Hostnames only, separated by commas. Page steps may read only these sites, over https, without cookies, sign-in or redirects. Leave empty to record tool steps only." The workflow builder has no field for web domains, so recording (or an assistant proposal) is currently the only way to give a workflow a public web step.
3. Declare the buyer input: Input name, Input type (EVM address, Text, Whole number or Yes or no), Demonstration chain and Demonstration value. "The demonstrated value is never embedded in the generated workflow, and replays must use different values."
4. Choose Start recording, then Run and capture a step for each approved tool you want, using your demonstration value where the buyer's input belongs.
5. Choose Compile workflow under Compile to an editable workflow. Captured steps become a draft: the demonstration value becomes a buyer input, each step gets an output condition and a report section, and failed or removed steps are left out. A permissions and redaction check runs before anything is saved.
6. Use Replay on an unseen input with values different from the demonstration. "A version is ready only after two different inputs pass every assertion." A failed replay is explained and never retried automatically.

Record a Token Researcher action#

This mode needs an existing Token Researcher version ("Only Token Researcher versions can be recorded"). You run token inspections on the page, choose the passing demonstration to compile, and get a new private Token Researcher draft that keeps the chain and token address as inputs. It then needs two passing replays on token addresses you did not demonstrate.

Rules for recorded agents#

• Recorded agents cannot be listed or submitted for review until the exact version has two passing replays on unseen inputs.
• Editing a recorded agent's draft creates a new version, which needs its own two unseen replays.
• Raw captured copies are deleted after seven days; you can also Delete raw recording yourself. Run reports, the compiled version and verification proofs remain.

Related pages#

• Build a workflow
• Data steps and approved tools
• Review and the badge