B402 (BNB 402)

BNB Chain first fair launch token based on the 402 protocol

x402 Request Flow diagram

About B402

BNB 402 Technical Story

On BNB Chain, B402 is a fair‑launch protocol token that backs micro‑payments. We elevate payment to a first‑class HTTP concept with fast, low‑cost settlement for APIs, pages, and AI agents.

Fair Launch Micro‑Payments Fast Finality Agent‑Native
Design Goals

Plug‑and‑play 402 flow, auditable on‑chain settlement, wallet/agent‑friendly client experience.

  • Clients or agents request a resource; server responds with 402 and PaymentRequirements.
  • Client chooses a scheme and constructs X-PAYMENT, then resubmits the request.
  • Server verifies locally or via facilitator; on success it fulfills and settles on‑chain.
  • Server returns X-PAYMENT-RESPONSE with transaction summary and auditability.

Mint B402 Tokens

0/500 BNB 0%
Fair Mint 50%
LP Pool 50%
BNB
Enter amount to see token conversion

Tokenomics

50%
Fair Mint
50%
LP Pool

Features

🔥Fair Launch
🔒Safe & Secure
💳402 Protocol
🤖AI-Driven

X402 Technical Story

What is x402?

x402 turns HTTP 402 (Payment Required) into an internet‑native payment primitive: metered access for pages, APIs, and agent actions with minimal integration.

HTTP‑Native Open Standard Chain‑Agnostic Trust‑Minimizing
Headers & Schema

X-PAYMENT (client) and X-PAYMENT-RESPONSE (server); PaymentRequirements are returned with 402, declaring accepted schemes and parameters.

  • Standard client/server flow with tiny integration.
  • Local or facilitator verification to reduce trust.
  • Chain‑agnostic, adaptable to different settlement layers.

Reference: coinbase/x402

BNB 402 Architecture

Resource Server

  • x402 middleware
  • Return 402 + PaymentRequirements
  • Local verify / facilitator verify
  • Fulfill response on success

Facilitator Server

  • Endpoints: /verify, /settle
  • Chain-aware validation
  • Policy/config for fees

BNB Chain

  • Low fees, fast finality
  • Settlement for micro-payments
  • Denomination in BNB or B402

Clients / Wallets

  • Construct X-PAYMENT from requirements
  • Agent or user-driven
  • Retry on 402 with chosen scheme

Technical Specifications

Headers

X-PAYMENT (client), X-PAYMENT-RESPONSE (server)

Requirements Schema

PaymentRequirements JSON describes accepted schemes and parameters

Verification

Local logic or facilitator server; signature and transaction checks

Settlement

BNB Chain finality; fees configurable per endpoint

Implementation Notes

Headers

X-PAYMENT (client) and X-PAYMENT-RESPONSE (server)

Schema

PaymentRequirements JSON accompanies 402 to describe accepted schemes

Verification

Local or facilitator validation; signature and transaction checks

Settlement

Finality on BNB Chain; endpoint policy configures fees