@bnbagent/studio-cli 0.0.13-alpha.2 → 0.0.13-alpha.3

package/README.md

@@ -10,9 +10,9 @@ The bundled `/bnbagent-studio` skill is the primary interface. It turns your int
 
 ## What Studio builds
 
-- **One valuable agent, one wallet, one signer.** The same runtime can serve A2A, MCP, and X402 faces without splitting custody across services.
+- **One valuable agent, one wallet, one signer.** The same runtime can serve A2A, MCP, and one B402 payment face (X402 or MPP) without splitting custody across services.
 - **On-chain identity.** ERC-8004 makes the deployed agent discoverable and records its live service endpoint.
-- **Two ways to earn.** ERC-8183 handles negotiated, escrowed jobs; x402 handles instant HTTP requests, with B402 settlement in paid mode.
+- **Two ways to earn.** ERC-8183 handles negotiated, escrowed jobs; x402 or MPP handles instant HTTP requests, with B402 settlement in paid mode.
 - **Bounded signing.** Quotes and payment checks run in fixed code. Raw signing is never exposed to the LLM, whose chain tools are read-only.
 - **A project you own.** Studio generates ordinary TypeScript under `app/agent/`; edit, fork, or move that code whenever you want.
 - **A guided path to production.** Run locally, diagnose readiness, deploy to the managed BSC testnet trial or your own AWS AgentCore account, then register the public endpoint.
@@ -90,10 +90,10 @@ Studio does not force every agent through one fixed path. The skill guides these
 | Network | `bsc-testnet`, `bsc-mainnet` | Start on testnet. The managed BNB trial always uses BSC testnet. |
 | Wallet | `evm-local`, `twak`, `altana` | Local encrypted keystore, Trust Wallet Agent Kit custody, or a bounded Altana runtime session. |
 | LLM | Pieverse, OpenRouter, OpenAI, Anthropic, Bedrock | Pieverse is the default; `auto/free` starts at $0/token. Other providers use your own credentials. |
-| Commerce rails | ERC-8183, B402, or both | ERC-8183 is job escrow. B402 settles x402 requests. Rails and public faces are separate choices. |
-| Public faces | A2A, MCP, X402, or a combination | One seller core and one wallet serve every selected face. |
+| Commerce rails | ERC-8183, B402, or both | ERC-8183 is job escrow. B402 settles request payments. Rails and public faces are separate choices. |
+| Public faces | A2A, MCP, and either X402 or MPP | X402 and MPP are alternative adapters for the same B402 seller and cannot be selected together. |
 | Deployment | BNB managed trial or AWS AgentCore | Every deploy asks for `bnb` or `aws`; a previous deployment is never a silent default. |
-| Deliverable storage | local or IPFS | Local storage is for offline development and fails deployment readiness. IPFS is durable, public, and deploy-ready. |
+| Deliverable storage | local, IPFS, S3, Azure Blob | Self-hosted deploys are BYOS: use IPFS, S3, or Azure Blob with a stable public read URL. Platform deploys ignore the project's local/BYOS choice; the API injects an agent-scoped token and uses managed S3 on AWS or Azure Blob on Azure. Public deliverable URLs stay on `bnbagent-api` and return 404 after the Agent is deleted. |
 
 ### Wallet choices
 
@@ -114,7 +114,7 @@ The skill normally takes a new seller through six stages:
 3. **Implement the value.** You edit the generated `runWork` hook in `app/agent/src/sellerCore.ts`. Pricing and signing stay in deterministic code.
 4. **Run and diagnose.** `bag doctor` checks the project, wallet, balances, LLM, network, and local runtime; `bag dev` starts the selected faces. Before deployment, `bag deploy prepare` adds storage, provider, and deploy-tooling gates.
 5. **Deploy and publish identity.** `bag deploy prepare` gates readiness, `bag deploy --provider ...` ships the runtime, and `bag deploy verify --provider ...` reconciles its ERC-8004 identity with the live endpoint.
-6. **Earn and settle.** Buyers fund ERC-8183 jobs or pay an x402 request. The agent verifies payment before work, submits the result, and records an audit trail.
+6. **Earn and settle.** Buyers fund ERC-8183 jobs or pay an x402/MPP request. The agent verifies payment before work, submits the result, and records an audit trail.
 
 ## What gets generated
 
@@ -167,6 +167,21 @@ The X402 face exposes `/x402`. Its seller rail has two intentional modes:
 
 Paid mode requires a complete per-agent B402 merchant setup; any supported wallet kind can be the payout wallet (for altana the payout lands at the admin address). Payment settles before work; if later work fails, there is no automatic refund. On self-hosted AWS AgentCore the rail runs in-process, but a buyer-facing x402 URL requires your own gateway that authenticates its relay call to AgentCore and, for paid mode, a fixed-egress path to B402.
 
+### MPP+B402: the alternative request-payment protocol
+
+Use `bag init <name> --rails b402 --payment-protocol mpp`. The generated project selects the `MPP` face, mounts `/mpp`, and uses the canonical `[payments.b402_seller]` policy. It emits only MPP—not x402—deployment publication metadata. Paid MPP additionally requires a 32-byte-or-longer `MPP_SECRET_KEY`, a stable `MPP_REALM`, and a durable atomic replay store shared by all production instances. See [the MPP+B402 guide](../../docs/guides/mpp-b402-selling.md).
+
+MPP buyer commands mirror the x402 workflow while remaining protocol-explicit:
+
+```bash
+bag mpp trust https://seller.example/mpp --yes
+bag mpp quote https://seller.example/mpp
+bag mpp buy https://seller.example/mpp --max-usd 0.10
+bag recipe code mpp-buyer
+```
+
+The buyer requires `evm-local` EIP-712 signing in P0, accepts B402 EIP-3009 only, pins realm plus recipient before signing, and never falls back to x402. Unknown post-dispatch outcomes are audited and never retried automatically. The emitted recipe is shared by AgentCore and Azure Foundry runtimes; managed Azure seller publication additionally depends on the platform's `mpp` capability.
+
 ## Service faces
 
 | Face | Local surface | Commerce behavior |
@@ -175,6 +190,7 @@ Paid mode requires a complete per-agent B402 merchant setup; any supported walle
 | MCP | Streamable HTTP at `http://localhost:8000/mcp` | The same seller operations, with funded delivery completed synchronously. |
 | A2A + MCP | A2A-native process on port `9000`, with `/mcp` tunneled | Both faces share one seller core, wallet, and busy-state lifecycle. |
 | X402 | `/x402` on the selected runtime entrypoint | One paid or explicitly FREE request; independent of ERC-8183 escrow. |
+| MPP | `/mpp` on the selected runtime entrypoint | Alternative to X402; standard MPP challenge/credential/receipt headers with B402 settlement. |
 
 For an A2A project, inspect the local agent card at <http://localhost:9000/.well-known/agent-card.json>. A seller expects structured A2A data parts, so a plain-text chat box is not a complete commerce test.
 
@@ -186,6 +202,18 @@ Run the readiness sweep before either target:
 bag deploy prepare
 ```
 
+To validate the exact managed backend explicitly (including Azure projects
+whose scaffold intent remains self-hosted), select the same provider/backend
+you will deploy:
+
+```bash
+bag deploy prepare --provider bnb --backend aws
+bag deploy prepare --provider bnb --backend azure
+```
+
+These Platform targets use managed deliverable storage, so a project-local
+`[storage].kind = "local"` does not trigger a BYOS storage blocker.
+
 ### BNB Chain managed trial
 
 ```bash