Ramya Chinnadurai 馃殌 (@code_rams) header
Ramya Chinnadurai 馃殌 (@code_rams) profile picture

Cofounder @heyula_ai Engineer & founder building with AI agents and sharing what actually works (and what breaks) along the way.

Planet Earth
Joined June 2020
Photo by Ramya Chinnadurai 馃殌 (@code_rams)Photo by Ramya Chinnadurai 馃殌 (@code_rams)Photo by Ramya Chinnadurai 馃殌 (@code_rams)Photo by Ramya Chinnadurai 馃殌 (@code_rams)Photo by Ramya Chinnadurai 馃殌 (@code_rams)Photo by Ramya Chinnadurai 馃殌 (@code_rams)Photo by Ramya Chinnadurai 馃殌 (@code_rams)Photo by Ramya Chinnadurai 馃殌 (@code_rams)Photo by Ramya Chinnadurai 馃殌 (@code_rams)
Turning 29 today 馃コ - Built two SaaS products. - Became a first-time mom. - Bootstrapped every line of code. - Balanced baby milestones with user feedback. My biggest lesson? You can build slow, messy, beautiful things and still be on the right path. Here鈥檚 to a year of softness, strength, and showing up, as me. What鈥檚 one life lesson you learned this year?
217
186
17
4,030
167,059
Replying to @ReelMap
Hand off at payment for now. Will switch to an agent wallet with a per merchant limit once a bank here supports it.
7
A budget plus a limit per merchant would have done it for us. The harder part was the rails, none of the routes we tried let a small team plug an agent into checkout yet 馃槄
1
17
Exactly! Ula does all the boring form filling, so the only thing left for the person is the one decision that really needs them.
9
Yeah, I'd add a limit per merchant on top of that. One overall cap would still let it spend the whole amount at a single hotel.
7
Replying to @Aspararm @heyula_ai
Agreed, and the cart context matters as much as the gate. If the approve screen only shows a total, people tap without checking what they're actually paying for.
7
No date yet. It depends on a bank here supporting agent tokens. Will explore and add it as soon as possible.
5
Ooh I hadn't seen that one, thanks! A token tied to one approved invoice is basically what I'd want for a hotel booking too.. one booking, one price, one approval.
10
Yes, the silent part scares me too. For a hotel booking the evidence would be the confirmation from the hotel itself, so hold-until-evidence fits travel well. What counts as evidence for the bigger jobs in AgentSolis?
11
Replying to @Aniketx @heyula_ai
Yes, that's close to what we do! Some of our API partners let us hold the price for a set time, so Ula fills everything and the parent gets one approve tap. If the hold runs out, they approve again with the new price.
10
Thanks Prasanth, that's pretty much how it works today.. some of our API partners hold the price for a set time, and if that runs out you approve again with the new number. Nothing gets paid on an old approval.
9
Good question! Some of our API partners let us hold the price for a set time. If that window runs out before the booking goes through, you get asked to approve again with the new price.
1
16
I tried to let @heyula_ai pay for an experience on its own. It got all the way to the payment page and died there 馃槄 Ula is our AI travel companion, it plans and books family trips. The planning part works. The booking part works, up to the moment money has to move. Then it needs a human. We tried a lot of routes over the last few weeks: 1. Plain cards. A card checkout expects a person. The OTP goes to your phone, not to the agent, and the bank's fraud checks are trained on human sessions. 2. Visa agent tokens. Live in the US and Europe, rolling out to Asia Pacific through partner banks. No bank in the market where we're launching first yet. 3. Mastercard agent tokens. There was one authenticated demo with local banks earlier this year, in a controlled setup. Nothing a small team can integrate today. 4. Some other payment APIs we looked at don't support agents at all yet. So the rails are too early for where we launch first. Agent payments on the local payment rails are being worked on, but still waiting on approval as far as I know. Here is how Ula works now: 1. Ula plans the trip and fills every form, [hotel, train, the kids' details], all of it. 2. It stops right before payment and shows the exact price. 3. You tap approve on your phone and pay with your usual method. 4. Ula confirms the booking and adds it to the itinerary. Every single payment gets one tap from a human. Honestly this started as plan B. Now I think it's the right default for family trips anyway, you want to see the final price before anyone pays for a hotel.. I'm watching the card networks and the local agent payment work closely. The day a bank here supports agent wallets with a limit per merchant, Ula will use them.
12
16
728
Replying to @levie
Even a tiny setup goes stale fast.. my OpenClaw setup from February and my Hermes one from April both feel outdated already. Every month something lands that makes last month's setup feel slow. These days everything runs in Grokbot and Claude Code, and I'm sure that will change too.
1
3
540
Ah nice, all the best to you too Kenn.
1
1
67
Ha I had no idea either 馃槀 I drove to another city so my cofounder and I could record ours together in person. Just talk to the camera for a minute about what you're building and why you, it doesn't need to look polished. Good luck!
1
80
Ha not rich at all. Nothing gets booked until you say yes on the exact price, so the random trip stays a suggestion till you approve it.
1
136
Everything. Each new call starts fresh, nothing from the last call carries over, not just the tail end. Same bot both times, my main one.
2
97
Desktop. It knows the text chat, but not what we said in the last voice call, so I end up repeating myself every time. Already doing the inbox with pages, one dashboard per product plus an HQ view. A native inbox would still be nicer.
2
2
243