Agents & bound wallets

Your Agent ID lives in Binance's Agentic Wallet, which only works by chatting with your Agent; it can't click buttons on a web page like a regular wallet. Zebra offers two ways:

Way	Good for	Each action
Bind a regular wallet	joining often, using the web page, trading the tokens you get freely	click buttons on the page like any dApp
Let your Agent do it	joining now and then without another wallet	page makes a code → send it to your Agent → Agent previews, you confirm → it runs

Both need two things first:

1. Turn on Developer Mode in the Agentic Wallet settings of the Binance app. It lasts 7 days, then must be turned on again, and has its own daily limit. Without it your Agent can't call contracts or sign authorizations.
2. Give your Agent the Zebra skill: hand it zebra.pub/skill/SKILL.md. The skill is public, so read it first if you like; it holds API addresses, how to check contracts and the steps, and no keys.

Bind a regular wallet

Once bound, the regular wallet can act for your Agent ID: subscribe, top up, exit and claim; tokens and refunds go to that wallet.

1. Open zebra.pub/bind with the regular wallet (e.g. a regular wallet in Binance Wallet, or MetaMask) and connect.
2. Enter your Agent ID name and click "Make code".
3. Click "Copy the line for your Agent" and send it. Your Agent first asks you for the last 6 characters of the wallet you are binding (look them up in your regular wallet); only if they match does it show what it will sign: your ID, name, the wallet to bind, the expiry and a fixed sentence, Bind this wallet to my Agent ID. It can join launches for this ID. Check the wallet address and confirm.
4. Paste the signature your Agent returns into the page and click "Check signature and bind". The page first checks locally that the signature comes from your Agent ID, then the regular wallet submits it (a little gas).

The code is valid for 30 minutes; signing is only an authorization: no cost, nothing on-chain, void after 3 hours. The binding takes effect with the transaction in step 4.

Rules

• Only sign codes you made yourself on the bind page. Signing a bind code someone else sends you hands your ID to their wallet.
• One wallet per Agent ID, one ID per wallet; a wallet that has its own Agent ID can't be bound.
• 3-day cooldown: after every bind, rebind or unbind, the ID waits 3 days to bind again (the first binding needs no wait); an unbound or replaced wallet also waits 3 days before it can be bound to any ID.
• Rebinding: when the ID binds a new wallet, the old one is unbound automatically.
• Bindings are public on-chain: anyone can see which wallet acts for which ID.
• If the Agent ID no longer holds its name, the binding stops working.

Unbinding

How	Who	When
"Unbind" on the bind page	the bound wallet	you're done with it
The ID signs an unbind that anyone submits	Agent ID (signs) + any wallet (submits)	the wallet is lost or stolen: cut it off at once
The ID calls the contract directly	Agentic Wallet (Developer Mode)	fallback

Unbinding takes effect at once. Rounds already joined are unaffected: money and tokens stay with the address that subscribed.

Let your Agent do it

1. On a round page, open "Do it with your Agent", enter your Agent ID name and amount, and click "Subscribe" (or "Exit", "Claim tokens", "Claim refund").
2. The backend checks first: the round is at the right stage, your ID hasn't already joined this round from another address, the amount is within the per-person limits, and then it simulates the call. If anything fails you see why and no code is made.
3. You get a 6-character code; click "Copy the line for your Agent" and send it.
4. Your Agent fetches the transaction, shows you the summary and amount, runs it only after you confirm, and gives you the transaction hash.

Codes are valid for 30 minutes and work once; make a new one on the page if it expires or was used.

You can also skip the page and tell your Agent "subscribe 0.05 BNB to this Zebra round": with the skill installed it makes the code itself, with the same checks and confirmation.

What your Agent will never do

The Zebra skill lets your Agent run only transactions made by the Zebra backend and sent to Zebra round contracts, and sign only authorizations for Zebra's binding contract. It never approves tokens (approve / permit) or transfers anything, the amount must come from you, and it always previews and waits for your confirmation.

Your record

Enter your name at zebra.pub/me to see your rounds, amounts and tokens received, no wallet needed. Rounds joined through your bound wallet count under your ID.

Error messages

The page and your Agent translate contract errors. If all you have is a 0x… string, open https://api.zebra.pub/api/decode?data=0x…; the full table is in the API reference.