# Special Developers Office Hours #81: Build, Pay, Automate with x402 (06 October)

**URL:** <https://forum.cardano.org/t/special-developers-office-hours-81-build-pay-automate-with-x402-06-october/157138>\
**Category:** Misc Dev Talk\
**Tags:** dev-office-hours\
**Created:** [2 October 2026 11:04 UTC](https://forum.cardano.org/t/special-developers-office-hours-81-build-pay-automate-with-x402-06-october/157138 "2026-10-02T11:04:27Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![lodl\_de](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.cardano.org/lodl_de/32/82473_2.png) [@lodl\_de](https://forum.cardano.org/u/lodl_de)\
**Post date:** [2 October 2026 11:04 UTC](https://forum.cardano.org/t/special-developers-office-hours-81-build-pay-automate-with-x402-06-october/157138/1 "2026-10-02T11:04:27Z")

</div>

![dev](https://us1.discourse-cdn.com/flex023/uploads/cardano/original/3X/4/7/475a7f7c8fc0d3b50158310a3262d25331c78311.jpeg)

**Special Dev Office Hours - Build, Pay, Automate with x402**

Joining the TOKEN2049 Hackathon? Curious how agent payments can work on Cardano?

Join Thomas Kammerlocher, Head of Solutions Engineering at the Cardano Foundation, for a practical session on building with x402 on Cardano.

In this special edition, Thomas will cover:

• What x402 is  
• How the official Cardano specification works Live demos and practical implementation insights  
• Q&A

And we may have some familiar faces from the Masumi team joining the conversation.

If you’re taking part in the hackathon, exploring agent payments, or want to see x402 in action, come join us and bring your questions.

📅 Tuesday, 06 October 2026  
🕑 08:00 UTC  
🔗 [Developers Office Hours #81 | AddEvent](https://www.addevent.com/event/4cgh95dcjx4p)

**Missed a session? View the recordings [here](https://www.youtube.com/playlist?list=PLCuyQuWCJVQ3IZiQQvHtczEM-cFAqoHBr).**

You can subscribe directly to the calendar here: [Cardano Developers | AddEvent](https://www.addevent.com/calendar/TG807216)  
Join the discussion below! We’ll update this thread with the recording link as soon as it’s live.

---

<div class="post-metadata">

**Author:** ![lodl\_de](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.cardano.org/lodl_de/32/82473_2.png) [@lodl\_de](https://forum.cardano.org/u/lodl_de)\
**Post date:** [21 October 2026 12:31 UTC](https://forum.cardano.org/t/special-developers-office-hours-81-build-pay-automate-with-x402-06-october/157138/2 "2026-10-21T12:31:13Z")

</div>

[![](https://us1.discourse-cdn.com/flex023/uploads/cardano/original/3X/2/1/218bb5cf8aac53d395727fbbaea8d37c5588b7d4.jpeg "x402: Build, Pay, Automate with Thomas Kammerlocher") ](https://www.youtube.com/watch?v=HM4Hp3SxI7s)

### **Summary: x402 on Cardano – Version 2 Standard & Integration**

In this edition of the Developers Office Hour, the host and representatives from the Cardano Foundation present the x402 standard and its integration into the Cardano ecosystem. The session details how x402 brings automated, decentralized pay-per-use monetization to HTTP requests for API data and AI agent computations.

**What is x402? Standardizing HTTP Payment Required**  
HTTP status code 402 (“Payment Required”) has existed in web standards since the early days of the internet but remained largely unused due to a lack of standardized native payment protocols. The x402 standard extends HTTP 402 to establish a universal mechanism for web servers to request direct cryptocurrency payments. Under this workflow, a client requests a resource, the server responds with a 402 status code containing a structured payment offer (specifying price and accepted cryptocurrencies), the client signs and submits the required payment, and the server validates the payment to immediately deliver the requested resource.

**Eliminating Friction for APIs and AI Agents**  
Traditional Web2 and Web3 API models force users through cumbersome onboarding steps, such as setting up user accounts, entering credit card details, managing subscriptions, or manually generating API access tokens. x402 completely eliminates these friction points by enabling true pay-per-use microtransactions. This is particularly transformative for autonomous AI agents, which cannot navigate traditional human sign-up flows or credit card forms, allowing them to pay per API call, data query, or compute task seamlessly.

**Version 2 Standard and Cardano Integration**  
Originally initiated under Coinbase, the x402 standard is now governed under the x402 Foundation within the Linux Foundation. The Version 2 update introduces flexible asset transfer methods, standardized extension schemas, and enhanced multi-chain interoperability. To bring x402 to Cardano developers, the Cardano Foundation’s Ecosystem Engineering team implemented client and server SDK packages across major programming languages, including Go, Java, Python, and TypeScript. This allows developers to simply annotate their HTTP web endpoints with payment requirements, abstracting away complex blockchain plumbing.

**Ecosystem Adoption: Masumi and Beyond**  
Masumi serves as a primary “killer application” for x402 on Cardano, leveraging the standard to power autonomous agent-to-agent payments, service registries, and decentralized task execution. Moving forward, the team is expanding x402 support to cover native tokens, script-based escrow flows (such as CIP-113 compliant tokens), and lightweight layer 2 payment channels to lower transaction fee friction for ultra-high-frequency microtransactions.

* * *

### **Top Five Q&A (FAQ) about the x402 Standard on Cardano**

**Question 1: What is x402 and how does the payment workflow function?**  
**Answer:** x402 is an open extension of the standard HTTP 402 “Payment Required” status code. When a client requests an x402-protected endpoint, the server responds with a 402 status code detailing the exact payment terms. The client executes the payment transaction, and upon server or facilitator verification, the server fulfills the request with a standard HTTP 200 success code and delivers the resource.

**Question 2: Why is x402 especially important for autonomous AI agents?**  
**Answer:** Autonomous AI agents cannot perform human onboarding tasks like filling out registration forms, completing KYC checks, or entering credit card credentials. x402 allows AI agents to autonomously discover endpoints, evaluate payment offers, and execute instant crypto payments per request without human intervention.

**Question 3: How do developers implement x402 in their existing applications?**  
**Answer:** The Cardano Foundation has provided official SDK packages for Go, Java, Python, and TypeScript (available via package managers like npm, pip, and Maven). Developers can simply add payment annotations to their existing REST or web framework endpoints, specifying the required price and currency, while the SDK automatically handles the HTTP 402 handshake and payment verification.

**Question 4: What is the role of an optional “facilitator” in x402?**  
**Answer:** A facilitator is an optional third-party service that handles payment monitoring, mempool verification, and settlement tracking on behalf of the web server. This prevents servers from needing to run full blockchain nodes or custom indexing infrastructure, though servers can also verify payments independently to remain fully self-hosted and trustless.

**Question 5: How does x402 interact with the Masumi ecosystem on Cardano?**  
**Answer:** Masumi integrates x402 as its primary payment protocol for AI agent services. Through x402, agents listed on Masumi can advertise their pricing, accept automated payments in native assets or stablecoins, and pay other autonomous agents for specialized sub-tasks seamlessly.

---

<div class="post-metadata">

**Author:** ![middayday](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.cardano.org/middayday/32/92259_2.png) [@middayday](https://forum.cardano.org/u/middayday)\
**Post date:** [5 November 2026 11:10 UTC](https://forum.cardano.org/t/special-developers-office-hours-81-build-pay-automate-with-x402-06-october/157138/3 "2026-11-05T11:10:38Z")

</div>

Thanks for posting the recording and the FAQ writeup. The SDK annotation path looks clean for new services. Harder question for people with an API already in production: what’s the least painful way to put 402 in front of an existing endpoint without rewriting the app, and is there a public Cardano facilitator on mainnet yet or still preprod only? Also interested whether sellers should quote ADA, a stable CNT, or both in the accepts list.

---

<div class="post-metadata">

**Author:** ![kammerlo](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.cardano.org/kammerlo/32/76160_2.png) [@kammerlo](https://forum.cardano.org/u/kammerlo)\
**Post date:** [5 November 2026 11:43 UTC](https://forum.cardano.org/t/special-developers-office-hours-81-build-pay-automate-with-x402-06-october/157138/4 "2026-11-05T11:43:25Z")

</div>

Thanks for answering and listening! It’s always great if questions arise.

For typescript it’s the way I showed in the dev office hours. The pain should be quite low, since it’s just annotations of the existing endpoints. In the TS SDK all major server should be supported. If needed I can also share more or deeper examples.

If the Server is written in another language, then it depends: Go, Python and Java are currently in review so the PRs are already created and we’ll now need to wait.

Mainnet facilitator is live here: `https://x402.mainnet.cardanofoundation.org`  
And Preprod here: `https://x402.preprod.dev.ecosyseng.cf-deployments.org`

Regarding what sellers should quote, that’s quite hard to tell what you are trying to achieve. Ada is probably with the least friction, since everyone has it. Common stablecoins like USDM are also easy for users, when it comes to more exotic CNTs then it will be harder for people to pay. Just think about if a user needs to go to a DEX before using your app. That’s what I think currently.

I hope it helps, if there are other questions, let me know. I’m happy to help 🙂
