BNB SMART CHAIN · BEP-20 · THE PARADE HAS STARTED

The avenue is open. 7,777 shares.

SAMBARIO mints by share on BNB Smart Chain, paid in native BNB. Only a wallet holding a .ai Agent ID can mint. The first share for every agent is free — no approve, one transaction.

Price per share —BNB
1st share —
Total shares —FCFS
Minted —
The first share is free — the first one for every .ai Agent ID goes for 0 BNB. From the 2nd to the 10th, each share costs 0.0012 BNB.

Mint stub

empty
SAMBARIO mint—
NO.000000
Wallet—
Agent ID—
Shares left—
How many shares?
Price per share—
1st share—
You receive—
You pay—
To the treasury—
Transactions1
—
—
You need: a wallet holding a .ai Agent ID and some BNB. No approve — BNB and tokens swap inside the same transaction.

Two ways to mint · the full walkthrough

Way 1 · through an AI agent (no human in the loop)

  1. Point your agent at …/skill.md The agent reads the live guide: current price, your quota, and the exact call data. All plain HTTP, no API key.
  2. The agent checks your eligibility Call /api/verify?address= to learn: do you hold an Agent ID, how much quota is left, is the free share still available, and does your BNB cover it.
  3. The agent shows you the numbers How many shares, how much BNB, the maxCost ceiling, and how much SAMBA you get. Then it waits for your go-ahead.
  4. You approve → the agent sends one mint transaction BNB rides along as value. No approve step. Any overpayment is refunded in the same transaction.
  5. SAMBA lands in your wallet immediately It arrives in the same transaction. The contract never holds SAMBA, so there is no "claim" step.

Way 2 · mint by hand in the interface

  1. Connect a wallet Hit "Connect wallet" at the top, or open this page inside the Binance Agentic Wallet.
  2. The page reads your identity and quota Quota follows the identity, not the wallet — several wallets under one Agent ID share the same quota.
  3. Pick how many shares (1–10) The first is free; from the second on, 0.0012 BNB each. The stub shows the exact amount live.
  4. Hit mint, then confirm in your wallet One transaction, no prior approve. Leftover BNB is refunded automatically.
  5. Done SAMBA goes straight into your wallet. Add the token to see the balance.
Why pay in BNB and not USDT? With native BNB there is no approve — one click instead of two, less gas, and much easier for an agent to execute on its own. The trade-off is that BNB's price moves, so the owner adjusts the share price (see "Trust").

Board · read straight from the chain

Reading the chain…

Trust · how to verify it yourself

Fixed supply7,777 shares · capped
Extra issuanceimpossible
Who can mintonly the sale contract
Contract holds SAMBAalways zero
Where payments go100% to the treasury
Auditable codepublic on-chain
  1. The supply is capped in code. The token has a hard ceiling = 7,777 × 100,000. Once the shares run out, creating new SAMBA is impossible.
  2. The mint permission is locked for good. Only the sale contract mints, and that setting is written exactly once. Not even the deployer can mint after that.
  3. The contract never holds your SAMBA. Tokens land in your wallet inside the payment transaction itself. So the most common scam — draining the pool — has nothing to drain here.
  4. Every payment is on-chain. The treasury address is public and anyone can follow it live. The board is decoded from the chain's own events.
  5. The code is open. The verified source is published on BscScan — you don't have to take a single line of this page on faith.
This isn't a promise, it's structure. Read the contract on BscScan, or check the state at /api/stats — neither goes through us.

Status

…

For agents

The whole interface is plain HTTP endpoints:

Guide/skill.md
State/api/stats
Eligibility/api/verify?address=
History/api/activity

Point your agent at …/skill.md and it participates on its own.

Contract · BSC · BEP-20

…