Command reference
There is no wizard. You post a sentence at @almeruagent and a typed launch request comes out the other side — or a question does.
The agent reads free text, so there is no syntax to memorise. There is, however, a grammar it resolves against, and knowing it is the difference between a launch that goes through on the first post and a thread of clarifying replies. Everything below describes what the parser looks for, not a format you are required to type.
The grammar
@almeruagent <verb> <object> called <Name> ($TICKER)
with <amount> <asset> [ options ]
verb launch | deploy | start | create → all resolve to the launch intent
object treasury protocol | miner
Name 1–32 characters, must be unique per deployer
TICKER 2–8 characters, letters and digits, leading $ optional
amount positive decimal, an asset the derived wallet actually holdsWord order is loose. "Launch a miner called Copper Field with 1,200 USDC, ticker CPFD" and "deploy CPFD — Copper Field, miner, 1200 USDC" resolve identically. What the parser will not do is guess a missing required field: a post with no bootstrap amount produces a question, never a default.
Required parameters
| Parameter | Accepted forms | Notes |
|---|---|---|
| Object | treasury protocol, miner | Ambiguous objects are asked about, not assumed. |
| Name | Quoted or unquoted after called / named | Trimmed, collapsed whitespace, case preserved. |
| Ticker | $CPFD, CPFD, ticker CPFD | Uppercased. Collisions are reported before any spend. |
| Bootstrap | 1200 USDC, 1,200 USDC | Must clear the balance check and both signed caps. |
Optional parameters
Optional fields decorate the launch. None of them touch economics — splits, fees, odds and schedules are fixed in the contract and are not addressable from a post.
| Option | How to express it | Effect |
|---|---|---|
| Token art | Attach an image to the post | Stored as the protocol image. Square, ≤4 MB, PNG/JPG/WebP. |
| Description | described as "…" or a trailing sentence | One line shown on the protocol page. |
| Opening delay | opening in 30 minutes | Delays the first round; the schedule length is unchanged. |
| Dry run | simulate only / do not execute | Runs parse → simulate and replies with the quote. No transaction. |
Worked examples
@almeruagent launch a treasury protocol called Harbor Reserve ($HRBR)
with 4,000 USDC
@almeruagent deploy a miner named Copper Field, ticker $CPFD,
bootstrap 1200 USDC [image attached → token art]
@almeruagent start a miner called Tin Line with 500 USDC, simulate only
@almeruagent launch a miner
↳ reply: "I need a name, a ticker and a bootstrap amount before I can
quote this. Reply with all three and I'll pick up from here."From post to transaction
Seven steps run between a post landing and a receipt going out. Steps one and two are pure identity, step three is the only place the language model touches anything, and steps four through seven are mechanical.
| Step | Stage | What it does |
|---|---|---|
| 1 | Ingest | A signed webhook delivers the post. The immutable numeric account id is extracted; the handle is ignored. |
| 2 | Bind | The account id resolves to its derived wallet. The EIP-712 grant is read and must be live. |
| 3 | Parse | The model turns free text into a typed launch request. It emits structure, never authority. |
| 4 | Validate | Name, ticker, amount and asset are checked. Per-launch and rolling 24-hour caps are applied. |
| 5 | Quote | Balance and fees are computed and replied back — what will happen, in full, before it happens. |
| 6 | Simulate | A dry run one block ahead against the pinned implementation set. Any revert stops here. |
| 7 | Execute | A single atomic-or-revert call to executeLaunch. The receipt is posted as a reply. |
A launch that fails at step four, five or six costs nothing but a reply. Only step seven spends, and only through the one method the agent is permitted to call — see Wallets and authority.
Reply classes
| Reply | Means | Your move |
|---|---|---|
| Question | A required field was missing or genuinely ambiguous. | Reply in the same thread with the missing piece. |
| Quote | Everything parsed; here is the exact cost and split. | Confirm, or ignore it — quotes expire quietly. |
| Refusal | A cap, a balance, or a name collision blocked it. | Lower the amount, fund the wallet, or rename. |
| Receipt | Executed. Transaction hash, block, and protocol route. | Open the protocol page and verify on chain. |