Cardano Code Don Merge Enter Official x402 SDK for AI Agent Payments

The x402 Foundation merge pull request #2537 on September 9, add Cardano to the protocol official TypeScript SDK. The contribution wey Cardano Foundation Fabian Bormann submit include working code, tests and integration examples.

Cardano get support through the x402 exact payment scheme across mainnet,

preprod and preview. The merge move the network from protocol specification enter the main repository wey dem dey use build x402 applications.

x402 Dey Connect HTTP Requests With Payments

X402 na open payment standard wey Coinbase originally develop. E dey use the HTTP 402 Payment Required status to connect access to online resource with cryptographically authorized payment.

API, dataset or digital service fit return request wey contain the price, supported network and recipient address. The client go sign the required transaction, while facilitator go verify the payment and submit am to the selected blockchain.

The Cardano code cover every part of this process. The client dey prepare and sign transactions, the facilitator dey verify and broadcast them, and the server dey define the price and conditions for accessing protected resource. The structure fit support software and AI agents to purchase data, computing resources or specialized API access.

Cardano Support Include Mainnet and Test Networks

The SDK dey register separate identifiers for Cardano mainnet, preprod and preview. E still support Cardano native assets and wallet connections through CIP-30.

USDM don configure as the default dollar denominated asset for mainnet and preprod. Payments in ADA fit happen through lovelace when dem configure am explicitly, but the native asset no be the default for prices wey dem express in dollars.

The client dey sign the transaction without broadcasting am, leave verification and submission for the facilitator. Cardano transaction decoding and serialization dey handled through the TypeScript based Evolution SDK.

Masumi Add Payments Between AI Agents

The code still include payment method wey connect to Masumi, Cardano based infrastructure for registering and paying AI agents.

Server fit issue seller signed quote for specific service and direct the payment enter Masumi vested_pay escrow contract. The payment go then connect to the terms wey dem present for the original HTTP 402 response.

The documentation identify one compatibility limitation. The authorization wey x402 integration use different from the signature format for the existing masumi-payment-service, so these payments need x402 aware tooling for result submission, refunds and dispute handling.

As of September 9, the npm registry no list @x402/cardano, and im dedicated publishing workflow never run. Developers fit inspect and build the merged code from the repository, while direct package installation go dey available after im first public npm release.