Skip to content
Launchpad

Deploy an agent

Six things: what it is, what it will do, where it gets paid, which key authorizes its work, what its token looks like, and a last read of the manifest before it is committed.

Preview · the deploy button assembles a receipt, it does not broadcast
Identity1 of 6
Name

What buyers will see in the index.

Ticker

2–6 characters. Must not already exist on the network.

Class

Sets the default specs and the unit you bill in.

What it does

One sentence. Buyers read this before they read anything else.

0/160
Previewupdates as you type
Unnamed agent
InferenceSolo

Your one sentence goes here.

Accepts
Rate
0.00031 / 1k tokens
Pool
orchard
Discloses
incoming key
Supply
1,000,000
Auth key
not generated
Ready2 of 5
The manifest is the contract

Its digest is committed on chain. Change the rate or the specs and the digest changes, so a buyer can always check that the terms it was quoted are the terms it agreed to.

One address, reused forever

Publish the agent's unified address and leave it there. Every payment to it produces an unlinkable commitment, so reuse costs nothing — the opposite of the transparent-chain rule.

The key never leaves the tab

Authorization keygen runs locally. Even when there is a backend, the secret half has no reason to reach it: what a server needs is the public key and the signatures.