BNB Chain · Partner discussion draft28 Oct 2026

Agentic services marketplace / Proposed AWS collaboration

Try a service.
Connect your agent.

A marketplace where people and their agents discover and pay for useful services on BNB Chain. BNB proposes to build its shared application and managed seller infrastructure on AWS, while keeping access open to clients on other runtimes.

Proposed productTwo buyer entry pathsAWS scope to agree
01 / PRODUCT EXPERIENCE

One marketplace. Two ways in.

Newcomers can try the product immediately. Existing-agent users can bring the workflow they already use. Both reach the same services and commerce system.

Newcomers / Official web assistant

“Help me find and use a service.”

A focused BNB-operated assistant explains options, presents a quote, requests wallet approval and returns the result. Guest and account allowances control BNB-funded inference.

Agent users / MCP, API and SDK

“Connect my existing agent.”

Portable tools provide discovery and authorized purchases. Clients keep their model, wallet and hosting. Their own AgentCore deployment is an optional integration.

The official assistant is proposed and still to be built. BNB operates this shared application. Clients operate the personal agents they bring; no individual buyer deployment is required to try the marketplace.
02 / SHARED ARCHITECTURE

AWS hosts BNB’s foundation.
Clients retain their choices.

BNB owns the product, merchant relationships and application operations. AWS can support compute, models, security, search and observability. Public service contracts connect all participants.

Two entry paths share discovery, commerce and quality evidence.

Conceptual architecture · responsibilities shown below · expand for larger labels

BNB marketplace on AWS with optional client-owned runtimesBNB's official assistant and independently operated agents use shared marketplace tools. Services can run in BNB's AWS pool or on merchant infrastructure, and use compatible facilitators to settle on BSC. BNB OPERATES / AWS-HOSTEDOfficial marketplace assistantShared web app · wallet approvalBNB funds bounded inference and hosting CLIENT OPERATES / ANY COMPATIBLE HOSTClient’s existing agent + model + walletLocal device · another cloud · own AgentCoreClient authorizes its purchase adapter BNB MARKETPLACE / AWS PREFERREDRanked discovery · quotes · access rights · receiptsMerchant console · feedback & evidence · assistant usage controls Published service interfaces Merchant service / API / agentBNB-managed AWS deployment, merchant’s own AWSor independently hosted compatible service Compatible facilitator / adapterMerchant selects supported payment optionsProvider verifies and settles payment BNB Smart Chain · settlement Output returns to the originating client.Feedback informs future discovery.Sensitive inputs and results remain offchain.
Discovery and commerce share a contract; purchases can call sellers directly where supported. Payment execution requires wallet authorization. Native AWS payment support for the required BSC combinations remains a separate validation gate.

No required buyer AWS account

Visitors use BNB’s web app. External clients use portable interfaces. AWS charges apply to clients only when they explicitly choose AWS products.

Clear operating costs

BNB pays for its shared assistant, marketplace and managed seller infrastructure. Clients pay for their own agents and approved service purchases.

Independent components

Runtime, model, wallet and payment adapter are separate choices. AWS can remain BNB’s preferred infrastructure without becoming a buyer requirement.

03 / END-TO-END JOURNEYS

Make the first exchange work for both sides.

The first purchase must deliver a useful result and a reconciled merchant record. Self-service registration can coexist with a curated launch catalog.

  1. 01

    Try or connect

    Open the official assistant or connect an existing agent.

  2. 02

    Discover

    See eligible services, relevant evidence and a clear quote.

  3. 03

    Approve

    Authorize the specific purchase through a supported wallet.

  4. 04

    Receive

    Get the result and a receipt in the originating experience.

  5. 05

    Reflect

    Submit attributable feedback; retrieve records when needed.

No AWS account is required for this buyer path. The official assistant’s allowance and the user’s service-payment budget remain separate.

Facilitator partnership ask: give eligible merchants a self-service activation path, clear provider requirements and predictable settlement operations. Automatic production activation depends on the provider; marketplace listing and payment approval are separate.
04 / PROPOSED CO-BUILD PACKAGES

Concrete AWS contributions.
BNB accountability stays clear.

Start with the shared application, service supply and open client access. Treat native payments and commissioned jobs as separately gated extensions.

A / Launch foundation

Official assistant & marketplace

BNB owns
Product, catalog/commerce, wallet consent, usage budgets and application operations.
AWS ask
Runtime/model architecture, identity and edge protection, observability and cost controls.

Valid without AWS: yes. Application interfaces remain portable; AWS is the preferred host.

B / Service supply

Merchant & seller launch

BNB owns
Merchant recruitment, offerings, facilitator activation, console and managed hosting operations.
AWS ask
Seller/public gateway templates, isolation, scaling, secure networking and API onboarding guidance.

Valid without AWS: yes. Compatible merchants can operate their own infrastructure.

C / Open client access

Agent toolset & optional hosting

BNB owns
Remote MCP, purchase companion/SDK, wallet adapters and tested client integrations.
AWS ask
Integration patterns and optional client-owned AgentCore deployment templates.

Valid without AWS: yes. Local and other-cloud clients retain a complete purchase path.

D / Discovery and trust

Ranked services & outcome evidence

BNB owns
Ranking policy, attributable feedback, evidence quality, merchant responses and appeals.
AWS ask
Search/evidence infrastructure, monitoring and optional discovery/evaluation connectors.

Valid without AWS: yes. Discovery and evaluation contracts remain provider-neutral.

E / Conditional extension

Native managed payment controls

BNB owns
Required BSC combinations, provider coordination, compatibility tests and portable fallback.
AWS ask
Assess approved BSC support in managed payments; co-build integration if supported.

Core product valid without AWS: yes. This native extension is AWS-specific and requires validation.

F / Later expansion

Commissioned jobs & evaluation

BNB owns
Deliverable/acceptance rules, evaluator authority, contracts, recovery and disputes.
AWS ask
Job orchestration, secure deliverable storage, tracing and approved evaluation adapters.

Valid without AWS: yes. Portable job APIs and evaluator choices preserve access.

All packages are proposed asks. Engineering support, credits, commercial terms and co-marketing require agreement; no AWS commitment is asserted.

05 / QUALITY IN DISCOVERY

Let outcomes improve the next query.

Ranked results combine task relevance with attributable quality evidence, confidence and warnings. Merchants can respond and demonstrate improvements.

DiscoverEligible, ranked services
Purchase & deliverKeep interaction references
Evaluate & reflectChecks and optional review
Improve discoveryValidate and weight evidence
Payment proves an interaction. Outcome evidence describes delivery quality. Reviews influence discovery after processing; refunds and optional escrow follow separate agreed rules.
06 / LAUNCH AND EXPANSION

Prove one useful purchase, then expand choice.

First / Working exchange

Assistant + external client

Curated paid APIs, one tested payment path, per-call approval, result/receipt recovery, merchant sales visibility and basic quality evidence. Enforce assistant usage budgets.

Next / More coverage

Clients and merchant activation

Add client integrations, facilitator options and optional client-owned AgentCore templates where they improve activation and repeat use.

Conditional / New capabilities

Managed payments and jobs

Enable native AWS payments after compatibility validation. Add subscriptions, commissioned escrow and advanced evaluation when demand and rules justify them.

Launch proof: a newcomer and a supported external agent can each complete a real service purchase; the result is usable, the merchant sees the reconciled sale, and costs and authorization stay controlled. No buyer AWS subscription is required.
07 / AWS DISCUSSION

Agree the first joint work package.

  1. Choose the initial workloads. Which assistant, marketplace and managed-seller components should form the reference architecture?
  2. Confirm the public access boundary. How will external clients reach services while BNB keeps tenant isolation, wallet consent and cost controls?
  3. Separate hosting from native payments. Which BSC network/token/scheme combinations can AWS support natively, and which need BNB’s middleware?
  4. Define the joint launch. Agree engineering owners, pilot services, acceptance gates and any credits or distribution support.
EVIDENCE / CAPABILITIES AND OPEN GATES

The architecture and responsibilities above are proposals. Published payment capabilities do not establish native support for every BSC configuration or readiness of the combined product.

Primary references and validation limits
  • AgentCore payment processing
    Documents payment instruments/sessions and returned signed results. Required BSC combinations still need validation.
  • WAF payment settlement
    Documents Coinbase facilitator settlement. Custom BNB middleware on AWS is a separate implementation.
  • B402 merchant onboarding
    Applications and separate sandbox/production credentials; instant production activation cannot be assumed.
  • API Gateway usage plans
    Best-effort quotas support the need for application-level inference budget enforcement.
  • MCP architecture
    Tool connectivity supports client integration. Wallet authorization is additional application design.
  • ERC-8004 · ERC-8183
    Draft identity/reputation and job/evaluator interfaces; ranking policy and implementation validation remain BNB work.

Public baseline: 26 Oct 2026. Core AWS payment, WAF settlement, quota and B402 onboarding references rechecked 27 Oct 2026.