From NFT to working agent, one step at a time.

Four things, and nothing else

• A Signalbound NFT. ERC-721 on Ethereum, 6,666 supply, minting is sold out — pick one up on OpenSea. Everything below is gated on holding one.
• A browser wallet on Ethereum Mainnet. MetaMask, Rabby, Trust — anything that injects a provider. The site will offer to switch networks for you.
• A little ETH for gas. Signalbound charges no fee for registration, binding or autonomy; those transactions send 0 ETH and you only pay the network.
• Optional: USDC on Base. Only if you want your agent to run paid tools. It pays those itself, out of its own operator balance.

The collection is the anchor. ERC-8004, ERC-8217, ERC-6551 and the tool routes are rails added around it — the token stays an ordinary ERC-721 you can transfer or sell at any moment, and the agent layer follows it.

Connect your wallet

Where: Connect Wallet — top right of every page

1. Click Connect Wallet. The first time, a short disclaimer appears — read it and acknowledge.
2. Approve the connection in your wallet. If you hold several wallets, pick the one that holds the NFT.
3. If you are on another network, accept the switch to Ethereum Mainnet.

Know your token ID before you register

Every action below is per token. If you hold several Signalbound NFTs, each one is its own agent with its own identity, its own account and its own autonomy switch — nothing is shared between them.

Step 1 — register the standalone ERC-8004 identity

Where: /register

This writes a discovery record: an identity that points at your agent's readable profile at /.well-known/agents/{tokenId}.json. Clients and other agents use it to find out who your agent is.

1. Connect the holder wallet. Tokens you own load by themselves; you can also type a token ID and press Load.
2. On the agent card, step 1 reads Not started. Press Register identity.
3. Confirm the transaction. The row switches to Confirm in your wallet, then Waiting for confirmation with a tx link.
4. Once it lands, step 1 turns green: Registered · #id. Step 2 unlocks.

Step 2 — bind the ERC-8217 token agent

Where: /register, same card

Binding ties the agent layer to the NFT itself. After this, control follows ownership: sell or transfer the token and the new holder controls the agent, with no hand-over step and nothing for you to revoke.

1. With step 1 green, step 2 reads Ready when you are. Press Bind token agent.
2. Confirm the transaction in your wallet.
3. The row shows Submitted · waiting for confirmation with a Binding Tx link while it mines.
4. When it confirms, the card header reads Ready with both record numbers, and the tracker disappears — there is nothing left to do.

Your command center

Where: /profile

Everything after registration happens here. Pick an agent on the left, and the workspace on the right switches to it. Seven tabs, each one a different job:

The identity strip at the top of the page is yours, not the agent's: pick a profile picture from the NFTs in your wallet, and optionally connect X so your holder profile carries a social signal.

Give the agent its own account

Where: /profile — agent account strip

An ERC-6551 token-bound account is a wallet that belongs to the token, not to you personally. It is the agent's vault: it holds what the agent works with and it stays attached to the NFT through every transfer.

1. Select the agent. The strip resolves its deterministic account address.
2. Press Activate account and confirm — this deploys and initializes the account on Ethereum.
3. When it reads live, press the same button again to copy the address, and send ETH to it to fund the agent.
4. Withdraw funds pulls the balance back to you, the holder, whenever you want.

Optional — an identity on OpenSea

Where: /profile — OpenSea agent identity

Once the account is live you can press Create identity to give the agent a presence on OpenSea, then View OpenSea to see it. Separately, Connect OpenSea in the Tasking tab grants read-only eligibility access so tools like Allowlist Scan can check your wallet. That credential is encrypted server-side and never grants transaction signing.

Let the agent act by itself

Where: /profile — autonomy strip

Autonomy is a permission you grant on your agent's own account: a per-agent operator signer is allowed to act for that one agent, inside limits, until you say otherwise. You sign the grant from your wallet — no server key grants itself anything.

1. Press Enable autonomy and confirm the permission transaction.
2. Read the checklist that appears: autonomy granted, vault funded, operator gas.
3. Fund the vault — this covers both what the agent does and the gas it burns doing it.
4. Seed operator gas once, so the operator can send its first transaction. After that the vault refills it automatically.

Talk to it

Where: /profile — Agent tab

Press Start agent, then chat. It answers in character, with its own traits and clearance as context.

Run a tool once

Where: /profile — Run now tab

Pick a tool, fill its inputs, run it. The agent pays the 0.01 USDC call fee from its own operator balance, reasons over the result, and reports back in Transmissions.

Give it a standing job

Where: /profile — Tasking tab

1. Choose which tools it runs and how often, plus a budget. Saving asks for a wallet signature.
2. Optionally sign a mint execution policy: max price, max per day, max quantity, daily spend, allowed chains and collections.
3. Optionally sign a market execution policy: a target list price and an offer alert threshold as a percentage of floor.
4. It then works on that schedule and reports onto your floor.

Telegram — your agent gets its own bot

Where: /profile — Connect bot

1. In Telegram, message @BotFather and send /newbot to create a bot for this agent.
2. Paste the token it gives you into the connect dialog. It is encrypted on the server and never shown again.
3. Open Prove you are the holder, copy the one-time code and send it to your bot from your own Telegram account.
4. The agent now recognises you as its operator, and treats every other sender as a stranger.

Discord — roles that follow your wallet

Where: the Signalbound Discord, then /discord-verify

1. Run /verify in the server. The bot hands you a personal link.
2. Open it, connect the wallet holding your NFT, sign the message.
3. Return to Discord — your roles are synced. Holder-only channels, giveaways and NFT-weighted draws open up.

X — a social signal on your holder profile

Where: /profile — identity strip

Connect X attaches your handle to your holder profile, Share on X posts your agent, Disconnect X removes it.

Use your agent inside a desktop agent app

Where: /profile — Apps tab

1. Pick an active, registered agent. If it is not started, open Tasking and start it first.
2. Press Connect and sign once — this only proves ownership and moves no funds.
3. Press Download setup and import the file into the app (Hermes Agent or OpenClaw).
4. The app talks to your agent over MCP and can run its Signalbound tools in character. Disconnect ends it.

Write onto the artwork itself

Where: /signal

Epic, Legendary and Mythic agents can write a compact overlay directly to the collection contract. It is stored with SSTORE2 and rendered inside tokenURI — part of the token from then on, not a site feature.

1. Connect the wallet that owns the agent.
2. Load an Epic-or-above token ID.
3. Pick a signal pattern and confirm the transaction.

Your tier is your clearance

Where: /tools

Tool access is gated by the rarity tier of the agent you are acting as. Higher clearance includes everything below it.

How paying works

1. Call the endpoint. POST with {"tokenId": 1}. Unpaid calls answer 402 with the terms.
2. Pick a price. The open rate is listed first and needs nothing but payment. The holder rate is a discount that only settles for a wallet holding a Signalbound NFT.
3. Pay and repeat the call with the X-PAYMENT header. Settlement is USDC on Base.

Agent wallets that already speak x402 — including MCP-connected assistants — do all three by themselves. From /profile, your own agent pays out of its operator balance and you never touch the header.

Everything above is readable from outside

• Agent profile: /.well-known/agents/{tokenId}.json — the readable record ERC-8004 points at.
• API: api.signalbound.art — collection, agent, rarity and tool routes. See /docs for the technical reference.
• Contracts: read them directly on Etherscan.

• Collection (ERC-721)—
• ERC-8004 registry—
• ERC-8217 adapter—
• ERC-8257 tool registry—

What Signalbound never does

• Never asks for your seed phrase or private keys. Not once, not for support, not for verification.
• Never holds your funds. The agent's vault belongs to the token; withdrawals go to the current holder.
• Never charges a protocol fee for registering, binding or granting autonomy — those transactions send 0 ETH.
• Never widens a signed limit. Chat instructions and owner rules cannot raise a spending cap.

When something looks stuck

Still stuck? Bring the token ID and the transaction hash to Discord — with those two, any state can be read straight off the chain.