Chains

MAIN CHAINS

BNB Smart Chain

Fast. Affordable. EVM-Compatible

BNB Beacon Chain

Sunset Complete

BNB ecosystem’s staking & governance layer

SHAPE THE CHAIN

Staking

Earn rewards by securing the network

DocumentationFaucetBscScanBSCTraceDocumentationFaucetBridgeopBNBScanDocumentationFaucetBridgeGreenfieldScanDCellarLearn more about FusionToken Recovery ToolBeacon Chain ExplorerNative StakingLiquid Staking

Build

GET STARTED

Submit dApps

Explore

Accelerate

See All Programs

Connect

Join us

Careers🔥

Explore Opportunities on BNB Chain

BNB Chain CareersEcosystem Jobs

Azure Credits for Agents Built in BNB Agent Studio

2026.8.20  •  2 min read
Blog post image.

TL;DR

  • Microsoft is providing a $1,000 pool of Azure credits for developers deploying agents through BNB Agent Studio.
  • Azure sits alongside AWS as a cloud option in Studio.
  • Nothing changes in how you build the agent, only where it can run.

Microsoft is putting up a $1,000 pool of Azure credits for developers deploying agents through BNB Agent Studio. The pool is shared across everyone who takes part, so credits go on a first come, first served basis and the offer closes once it runs out.

The Smart Money Era runs on agents that do real work: watching a lending position, moving capital to where it earns more, charging for the job. All of that has to run somewhere, and paying to find out whether a new cloud suits you is the kind of cost that arrives before a developer has seen Studio do anything useful. The credits remove that step.

Azure sits alongside AWS as a cloud option in Studio, and which one you pick comes down to what already fits your setup and your distribution. The agent itself is unaffected either way. Identity, wallet, and payments work the same wherever the agent runs, so picking a cloud is a deployment decision rather than a change to how you build.

Get Started

Build your agent as usual with bag init, set up a testnet wallet with bag wallet new, and test locally with bag dev, which consumes no cloud resources. When you run bag deploy, choose Azure, sign in with GitHub, and confirm the 48-hour terms. Your window opens on the first deploy that succeeds, not at login.

From there, bag erc8004 register puts the agent's identity on BSC, and the agent serves requests over A2A or MCP without any further command.

Eligibility & Timing

Dimension

Rule

GitHub account

At least 30 days old

Participation

Once per GitHub account, no re-enrollment

Network

bsc-testnet only, mainnet not supported

Timer start

First successful bag deploy, not at login

Trial duration

48 hours

Reminders

CLI warnings at 12 hours and 1 hour before expiry

Logging in without deploying

Does not count against the 48 hours

Campaign end

Closes automatically once roughly 80% of the pool is spent

Anyone already inside their 48 hours when the pool closes keeps running to their own expiry.

Usage Limits

Limit

Value

Invocation rate

60 requests per minute

Concurrent invocations

2

Single session duration

5 minutes, terminated on timeout

Idle reclaim

After 1 minute of inactivity

Agents per user

10

Deployments per hour

10

Concurrent in-flight deployments

3

Zip package size

250 MB

Container image size

2 GB

Single request size

10 MB

What happens after 48 hours

The cloud deployment is deleted permanently and cannot be recovered. Your local code and wallet files stay on your machine, and the agent's ERC-8004 identity and transaction history stay on BSC.

Use a wallet dedicated to testnet and never one holding real assets, because stored secrets are deleted with no recovery window. Back your local code up when the 12-hour reminder arrives.

To keep an agent running past the window, point Studio at your own Azure account and redeploy.

For everything shipped in the latest release, read BNB Agent Studio v2: Your Agents, Your Rules.

Share