Prompt in.
Agent out.

BNB Agent Studio is a developer tool from BNB Chain that brings a wallet, an LLM, on-chain agent identity (ERC-8004), a task interface (ERC-8183), and a cloud runtime together in one toolkit. You install it from the command line; the CLI then auto-registers Studio's MCP server into your vibe coding tools (Cursor, Claude Code, or any MCP-compatible client), so you can create and deploy an on-chain agent using natural language right inside the editor. Describe what you want, and BNB Agent Studio scaffolds, deploys, and registers the agent on BSC. Every agent gets its own on-chain identity and its own wallet, and can pay for its own LLM calls so it runs by itself.

Getting started takes four steps, you install via the CLI with pip, then build in your vibe coding tools:

1. Install: Run pip install bnbagent-studio. The CLI and the agent runtime land together in one command.
2. Install Skills: Run bag install. This auto-detects Cursor and Claude Code and installs the BNB Agent Studio skills; reload your vibe coding tools and it knows how to drive BNB Agent Studio.
3. Build in your vibe coding tools: Describe what you want in plain English, for example (Create a BNB seller agent that sells weather forecasts on BSC testnet). The skills scaffold a production-shape agent, the seller logic, wallet, LLM, signing, and pricing, instead of boilerplate.
4. Deploy & Earn: One ask, for example (Deploy my agent and verify it's live). The agent deploys to cloud platform, its ERC-8004 identity is registered, its ERC-8183 task interface goes live, and x402 funds the LLM, so the agent gets paid in $U on its own.

You choose the wallet provider when you create the agent, BNB Agent Studio integrates wallet tooling such as TWAK (Trust Wallet Agent Kit) as a default option, and more wallet providers are welcome to integrate. Whichever you pick, the agent gets its own wallet bound to its on-chain identity.

Spending stays under your control through spend rules you confirm yourself: a balance threshold, a refill amount, and a daily spend cap act as guardrails, so an agent can only auto-top-up within the limits you set. The exact custody model depends on the wallet provider you choose.

Yes. BNB Agent Studio is an integration layer, not a locked-in stack. It bundles a wallet, an LLM, on-chain agent identity (ERC-8004), a task interface (ERC-8183), and a cloud runtime, and when you create an agent you pick the providers that fit you. The defaults today are TWAK for the wallet, Pieverse for the LLM, and AWS AgentCore for the runtime, but each is one option among several, and BNB Agent Studio actively welcomes new wallet, LLM, and cloud providers to integrate.

You pay only for the LLM calls the agent makes. As a real-world example: an agent watching BSC overnight made dozens of LLM calls and spent roughly $0.31 in a night, topping itself up automatically when it hit its $2 floor. Costs depend on the model and provider you choose. On the default Pieverse path, gpt-4o runs about $0.002 per call, and every call logs its exact cost and remaining balance for full transparency. On-chain, $U transfers are gasless via EIP-3009, so you never pay for BNB gas.