Agentda

Agentda remembers how you travel. Books it. Pays it. Done. x402-powered. Zero manual intervention. → agentda.xyz

Singapore. Next Tuesday. Mandarin Oriental. 380 USDC. Done.

Future in Bloom🌸 Join the campaign and win a share of the 300 USDT raffle! app.galxe.com/quest/Gata/GCf… A new season for builders. Ideas grow. Communities connect. New projects emerge. Take part in the campaign and explore what’s next. @clawrouter @IsingResearch @Whiffin_cc @AdxProtocol @Agentda_AI @Voranofficial

An agent just paid for a VPN with x402 on Base. 🛡️ x402 started with hotels. Now it's buying bandwidth. Agentda was running hotel payments on x402 three weeks before this. What gets paid next?

agents are choosing base for payments

Imagine if your AI assistant could independently search for a new API tool, check the price, pay for it, and use it, all in seconds. Today we are launching Bazaar MCP: the first discovery marketplace for AI tools and APIs. 🛒🤖 Here is why this matters 🧵👇

A Telegram message → hotel confirmed → USDC settled → conversation saved. End-to-end proof. No middlemen. No black box. That's how we're building verified agent payments — and why VRP-1 made it the right moment to say so.

The stack that makes this possible: → x402 as the payment protocol → Stablecoins as settlement (<$0.01 gas) → Telegram as the human-readable record layer Most people building agent payments stop at "transaction confirmed." We don't stop there.

Agent books hotel. Payment settles. But where's the proof? 🤔 Crypto payments have a trust problem nobody talks about. Transaction confirmed. But did the hotel actually receive it? Is there a record a human can read? A support team can verify? "Payment went through" isn't a receipt.

Why HTTP 402? It was literally called "Payment Required." Reserved in 1991. Never used. Because the web never had a native payment layer — until now. x402 isn't a workaround. It's what the internet always needed. This is what Agentda is building on. AI agents that book hotels end-to-end — search, confirm, pay — in a single flow. No checkout page. No card form. No clearing house. Just: intent → booking → done. The 518K number is a signal. The infrastructure is ready. Hotel booking is next.

The x402 trust chain: You → Contract → Done. No intermediary holds your money. No one can lose it, delay it, or skim a cut. The hotel gets paid the moment you book. Not in 3-5 business days.

518,000 payments. $0.31 each. Settled yesterday — no banks involved. That's Circle's x402 in one day. Here's why hotel booking is exactly where this changes everything: 👇

Hotel booking in 2026 still feels like filing a tax return. Tab 1: flights. Tab 2: hotel. Tab 3: that sketchy aggregator your friend swore by. Tab 4: back to Tab 1 because you forgot the dates. Type your card number. Again. Verify your email. Again. "Your session has expired." With Agentda, just drop a message in Telegram. One conversation, one payment — confirmed. The receipt is on-chain. The headache isn't. ✅

@CoinbaseDev This "Upto" scheme is a game-changer for AI agents. Lowering the barrier for variable-cost services like LLM inference makes building autonomous travel booking agents on x402 much more efficient. Great step forward!

Usage-based pricing is now live on x402! The new "Upto" scheme lets agents pay only for what they consume, unlocking variable-cost services like LLM inference, compute, and data queries on x402. Available now on the x402 SDK + CDP Facilitator. ↓

This gets really interesting when the buyer isn’t a human. With autonomous agents, HTTP 402 becomes a native payment layer for software. Think travel agents that can book flights, hotels, and services themselves. That’s the direction we’re exploring with Agentda.