Your first agent.
The whole journey.

Enter the workshop

1. Click Connect wallet in the header, then choose Local creator.
2. If you are already signed in as another identity, open Settings, click Switch test identity, then choose Local creator.

Signing in identifies your workspace. It does not authorize a payment. My Workspace brings your agents, access passes, and run history together. Use Settings to change the connected wallet.

Create your first agent

1. Choose Create an Agent from the home page, or open the creation screen below.
2. Enter the example name and job, choose a category, then click Prepare my draft. Or choose Generate agent, describe the agent in a short prompt, and review the generated fields first.
3. Review the editable instructions in Instructions. Manual drafts start from a template; generated drafts use the suggested instructions you approved.

Add source material

1. In your agent, select Knowledge → Add source.
2. Set Source title to First handbook and paste the text below into Source text.
3. Click Add source and wait for the source to appear.

You can also upload a UTF-8 .txt or .md document up to 100 KB, review the populated fields, then click Add source. PDF and Word ingestion are not available in this edition.

To update a handbook, click Edit beside its name, change the title or text, then choose Save changes. Cancel discards your edits. Published versions keep their original handbook; publish a new release to make the updated content available to holders.

Connect a tool

A knowledge-only agent works without a connection. Use this optional step to try a tool and the controlled failure example later.

1. Open Connections → Add a connection. Choose Remote MCP, then click Use the local test fixture and Save connection.
2. Click Inspect tools, select reference_lookup, read and check the observe-only acknowledgement, then click Approve selected tools.
3. Click Test and inspect the result.
4. Return to My agents, open your agent, select its Tools tab, and check the tested connection. Wait for Saved.

Run inputs are shared with selected tool operators. Use the provided local fixture for this example. For current public information, open your agent’s Tools tab and enable Web research. Live answers can then search the public web and show clickable links to the pages used. The source check mode does not call the live model.

Test your draft

1. Find the Playground beside the editor and paste the question below into Test input.
2. Click Run a test or press Ctrl / ⌘ + Enter. Read the returned source excerpts and answer. Open Run details for status, timing, and tool activity. Enter on its own adds a new line.
3. Earlier questions and answers stay above the newest test in the Playground. Scroll inside the conversation to revisit them; each test is an independent run.
4. Open Test history to inspect a saved result. Use Copy output to copy it or Clear answer to clear the screen; saved history is kept. Use this question again puts a previous question back in the prompt without running it.
5. Choose Revise expected answer to enter a correction. Review the change to Instructions or Knowledge before saving. Save & retest runs the saved question again; Save without retesting keeps it in Test history for later. Published versions are unchanged until you publish a new release.
6. If the answer is missing, check that the source was added and saved in step 3, then test again.

Source check uses a local fixture and does not call a paid model. Choose Live AI in the Playground to test the real model and any enabled Web research tool before publishing. Draft tests do not use NFT credits. Test history keeps each question and result for later inspection.

Publish a version

1. Select Review & publish → Pricing & access. Review access price, price per completed run, pass supply, transferability, and holder usage quota.
2. For this walkthrough you can keep the defaults: 0.001 ETH for access and 0.00002 ETH per completed run. Your form is the source of truth if you changed them. Choose a daily, monthly, or lifetime quota; resets use UTC. Each completed run is charged separately.
3. Open the final Review & publish step, check the creator allocation, then click Publish local version and wait for confirmation.

Publishing creates a fixed version of the draft. Editing the draft later does not update an existing release. A new release has its own access pass.

Switch identity & get access

1. Open Settings, click Switch test identity, and choose Local holder.
2. Open Explore and select your published agent. If several releases share a name, use the URL saved in step 6. Reload any agent tab left open before switching identities.
3. Connect a wallet and use Try before minting to ask up to two live questions. No ETH transaction or NFT credit is needed. Trial history stays in that agent’s chat; failed runs return the trial slot. The two-run limit follows the wallet and agent across new versions.
4. Review the access terms and click Mint access pass. Wait for the confirmed access state.

New releases include floor(mint price ÷ run price) runs with every primary mint. At 0.001 ETH and 0.00002 ETH per run, that is 50 runs with no extra usage charge. These credits are shared by website and API and stay with the original minter; transfers do not grant credits. Earlier releases keep their original terms.

Only using an existing agent? Start here with Local holder and choose an available release. You do not need to build your own.

Optional paid run balance

Skip this deposit while you have included runs. Check the remaining credits on your agent or in My Agents → Collected. Deposits are for paid usage after included credits run out. For earlier releases, use their separate balance card in Wallet.

1. As Local holder, open Wallet and check your wallet balance.
2. Click Deposit ETH, enter 0.01 for this example, and click Confirm transaction.
3. Wait for the confirmed balance. If your chosen run costs more than 0.01 ETH, deposit enough for its displayed price.

A deposit makes funds available for runs. It does not buy an access pass or start an agent. All ETH labels in this local workshop refer to local test ETH.

Authorize a run

1. Open the same published agent as the holder with its pass.
2. Enter What is the refund period? in the message box at the bottom of the conversation, then click Send message.
3. Your earlier website conversations with this agent appear above the new message. Each question is a separate run; the agent does not remember earlier messages.
4. The first included-credit run may ask for a one-time wallet signature. Later included-credit runs use that permission without another prompt. Paid runs still require wallet approval.

The price beside Send message shows whether the run uses an included credit or ETH. The local identity flow handles test signatures for you.

Read your result & receipt

1. Select your run to open Run receipt. Read the output, source references when present, execution status, and funding status.
2. Compare the authorized maximum with the confirmed charge. A reservation holds funds temporarily; it is not a final charge.
3. Optional: with the local reference tool attached before publishing, run a question containing [fail]. Inspect the failed execution and eventual released reservation.

For a queued or running job, Request cancellation submits a request. Wait for the final execution and funding states; clicking it does not itself confirm a refund. A pending payment state should be checked before submitting another paid run.

Reservation released confirms that the held amount returned to your available balance, with a zero application charge. Release awaiting confirmation means that recovery is still in progress. A timeout appears as timed_out; an interrupted worker preserves the question and does not automatically repeat the request.

Claim creator earnings

1. Use Settings → Switch test identity → Local creator.
2. Open Creator earnings and review the claimable amount from pass sales and completed holder runs after the displayed fees.
3. If the amount is positive, click Claim earnings, review the dialog, and click Confirm transaction.

Check the actual balance rather than expecting a fixed amount: earlier transactions may exist, and prices are configurable.

Withdraw unused funds

1. Use Settings → Switch test identity → Local holder, then open Wallet.
2. Check AVAILABLE TO RUN. Only available funds can be withdrawn; wait for any reserved run funds to settle or release.
3. Click Withdraw, enter an amount no greater than your available balance, and click Confirm transaction.

Withdrawing unused funds does not refund a purchased pass or a completed run. Your pass and receipts remain associated with the holder wallet.