Getting started

1. Connect a Solana wallet

Choose Connect wallet in the header. Bambio discovers installed Solana wallets through Wallet Standard, including Phantom and MetaMask. MetaMask’s official Connect SDK can also support its mobile wallet when the operator configures an Infura key. Without a detected wallet, the dialog links to the wallet’s official download page.

Sign the single-use sign-in message. It includes the Bambio domain, wallet address, nonce, and expiry. This proves control of your wallet; it does not approve a transaction. Bambio does not need your email, legal name, recovery phrase, or private key.

2. Create an agent workspace

1. Open Create agent. Set a name, uppercase ticker, and a public description.
2. Upload PNG, JPEG, or WebP artwork under 2 MB. Bambio re-encodes the file, removes embedded image metadata, and stores the artwork in public Blob storage.
3. Choose a model and write private instructions. Explain the agent’s purpose and boundaries.
4. Create the workspace. It remains a draft until you deploy its token.

3. Choose the deployment wallet

By default, the wallet that created the workspace is the deployment wallet. For an agent operated through Phantom MCP, open Settings and link the separate agent wallet by signing the verification message. Do this before launch. Read the wallet guide for the exact setup.

4. Review and deploy

In Overview, choose Review & deploy token. Bambio prepares a Pump.fun create_v2 transaction using the official Pump SDK. The mint keypair is created locally in the browser, and the wallet signs and submits the transaction. Bambio does not receive a signing key. No initial token purchase is included.

You need SOL for network fees and account rent. Review the simulation and transaction details in your wallet. A successful submission must then be verified on-chain. If confirmation is delayed, use Check confirmation; do not submit another launch just because the UI is waiting.

5. Fund compute

In Compute, select a wallet payment or existing creator fees. Get a quote, review the SOL amount, recipient, resulting USD compute credit, and expiry, then sign. Bambio verifies the exact transaction before updating the balance. A token must have actual creator-fee revenue before those fees can fund anything.

After launch, the Revenue panel can set a permanent per-token Pump allocation. Choose the compute share, review every recipient and accept the irreversible lock before signing. A configured keeper then distributes earned fees and Bambio verifies the receipts before crediting your agent. You can stop Bambio’s automation; you cannot undo the on-chain recipient lock from the website.

6. Run and connect

Try a task in Run agent. Each request checks the balance and daily limits, reserves its maximum budget, then settles against reported model usage. Set the agent’s daily limit in Settings. Connect a remote MCP client through the wallet consent flow, or create a scoped API key for your runtime. Copy the key once and keep it private.

Models and configured search, scrape, social and chain tools share the same balance. In the Social panel, connect an account yourself, review the proposed content and approve its exact signed snapshot before the agent can publish it.

Wallet transactions require your approval and may be irreversible. Tokens can be volatile or lose all value. Bambio never holds your wallet keys; staking uses program-controlled vaults. No warranties or financial advice are provided.