Transcript
A (0:00)
I just made the biggest speculative point
B (0:02)
transfer in my life. A few hundred thousand points moved out in one shot and I'm still not totally sure if it was brilliant or reckless.
A (0:10)
Today I'm going to tell you exactly
B (0:11)
why I did it, what made this particular deal so hard to pass up, and how you should think about transfer bonuses so you can decide for yourself when they're worth it. I've also got a breakdown of the new Hyatt award chart changes, which yes, really suck, but might not be as catastrophic as the headlines suggest. Then I'll walk through the best elevated credit card welcome offers right now, Delta, United, Southwest and more. And I'll share a quick update on how AI is changing the way I actually run this podcast behind the scenes and some of the stuff I'm working on there. Lots of ground to cover, tons of takeaways you can put to use. So let's get into it. I'm Chris Hutchins. If you enjoy this episode, please leave a comment or share it with a friend. And if you want to keep upgrading your money points and life, click follow or subscribe.
A (0:55)
All right, so let's talk about a lot of things today, but I'm going to start with something I've been spending a tremendous amount of time on, which won't be a surprise for people who listen to my episode a few weeks ago about AI tools, because it's just kind of really captivated me. It feels like I'm living in the future. And back then I was talking about how I built this open claw agent named Ted. Since then I've spun up another seven agents. So there are kind of seven agent employees operating in my slack on text and all kinds of areas of life. And I want to say that I've kind of evolved how I'm using this tool in a way that I think is a little bit different than I first thought. At first it was I have this assistant. I can message him anytime and he can do all these things. And I'm starting to realize that one great use case for a lot of these technologies is repeatable work that requires context and kind of siloing it into different agents. And I realized that you could do this in two ways. One, you could kind of write up the background and context you want for certain tasks and just have any tool do that when you go and open up a new chat in Claude, in ChatGPT and Gemini. You know what I used to do is I would dump in a list of every title of every episode I've ever published and then say, help me come up with a new title for this episode. Here's the transcript. Now, I have one agent who's solely focused on kind of the creative work around episodes. And so their memory and all of their kind of context already has that. I had them go through all of the past thumbnails, titles and takeaway learnings and write up a brief for themselves for every time I ask them to do anything. And so that agent, her name is Spark, gets a transcript and can propose different ideas for YouTube thumbnails. And so what I've tried to do is instead of thinking of it necessarily like a chat interface, I'm taking different actions and trying to, to kind of tie them both to an agent and to a bunch of context, but also to some automation. And so as soon as I'm done recording, and I mark that in a project management tool that fires off an agent to go grab the transcript, come up with thumbnail ideas, and the next thing that I haven't built yet, but I'm excited about is actually working with some image generation stuff to actually just create the thumbnails. Haven't gotten that far. Right now it uses the Gemini API to generate thumbnails with random people that aren't me, to kind of give the idea of what they would look like. But I actually think there's a world where you could start to use your own images and kind of piece things together. So that is one. And if you don't know how to do that, don't worry, that's where I was. And I just always encourage people to just start talking to these tools and say, hey, I want to build something that could generate thumbnails. How could it do this? And you could do that for any aspect of life. That said, the usefulness of openclaw, I would say, hasn't changed, but the ability for other tools to catch up and kind of replace a lot of what made it super valuable has. And so if anyone uses Claude, they have this tool called Claude Cowork, and you can run it on your computer. And it kind of solves some of this because they added scheduled tasks. So you can say, hey, could you put together this briefing of sorts of whatever you want? And then, hey, could you run it every morning at 7am and so you don't need to go buy a Mac Mini and install Open Claw to do that. And I imagine that a lot of these tools are going to start to layer in schedules, scheduled tasks on an ongoing basis. And as they start building out more connections right in Claude you can go in and connect your email, you can connect things, Chat. GPT has some different apps. Once that starts to happen, you'll have very similar experiences to what you can create with openclaw. But you can do it using the tools that you're already using, instead of having to kind of start from scratch in a little bit more of a raw way. And so I think that's kind of the evolution of where this goes over the next probably couple of weeks is that more and more features like that will exist. What's still missing is that when you have a piece of software running on a computer that has the ability to create more software and run it on the computer as well, you can spin up lots and lots of other things. And I think that's where I still really value what's going on with Open Claw over a lot of these other tools. So, for example, I have an OURA ring, and there wasn't a Aura connector built into CLAUDE or chatgpt on. But there are ways that you could say, hey, go spin up a skill that syncs with Aura and pulls down my sleep data, or, hey, go Sync with Tesla's APIs, or go log into my Open Snow account and give me a snow forecast for an upcoming trip, or go build a way to interact with my meal planning app. Those kinds of things are things that you can use GPT codecs on your computer, you can use CLAUDE code to kind of build those skills, but you need something to interact with them and run them on a recurring basis. I don't think we're that far from all of these mainstream AI properties or kind of software companies from building things like this. But right now, I still think that's one of the competitive edges that you get from playing with things like openclaws that you get to create software that does exactly what you want, runs on a schedule, and kind of interfaces with you wherever you want. And that's the other big thing. I love being able to use iMessage or Slack as the medium instead of going to the ChatGPT app or going to the cloud app. One other thing I've been playing with is I have Card Tool, and then I also have all the hacks. And so I've been trying to think about how I can take all the knowledge of those things and tie them into existing tools. And because I have that information and it lives online in different servers, I actually built something called a mcp, which is a model context protocol. And it kind of sits on top of an API, which is how different applications interface with other applications online. I could plug it into Claude, or you could go create a custom GPT and you could plug it in there and it's able to access that information. It was a really fun experiment because I started seeing another aspect of what I keep referring to as like the future of the web and the future of all of this. And that is that when I go on Claude now or ChatGPT and I open that custom GPT, I can reference data that lives in card tools. So I've added 41 credit cards to this app I've been building and it knows all my annual fees, it knows what credits I have outstanding, it knows when the bills are due, it knows what the balances are, it knows everything, because that's what that app's purpose is. And up until now, ish, every piece of software online is something that you interface with using that piece of software. So when I first built Card Tool, and when we're talking two months ago, it never crossed my mind that someone might use Card Tool without ever even going to our website. And I think that's probably true of all kinds of pieces of software. So, for example, how would you interface with United Airlines if you didn't have the app or the website? Right. I guess you could call the phone number, you could fly the planes, but how would you book a flight? Historically, companies have created APIs so that other companies can access them. But it was very much not a consumer thing, right? It was so that other businesses could interoperate with that business. So maybe Built Travel Portal wants to use United's travel booking platform to book a United flight. So they create an API, but it's not really a consumer thing. Now, some of These tools make APIs available to anyone, and some of them don't. And some of them kind of make them available to anyone. But it's definitely not a straightforward, simple process. And what I realized as I added the card tool data to Claude and I was able to just query it, I realized that the core thing I built was not necessarily a website or an app. It was a bunch of information stored in a particular way that makes it more valuable to because of the way it's stored, and that the interface to it might not in the future be a website or an app. And that as I'm both simultaneously building this app and interfacing with the assistant I've built on openclaw, I started to think about the future of the Internet and whether it looks a lot more like it looked 20 something years ago. Than it does today. And what I mean BY that is 20 or maybe 25, 30 years ago, I can't even keep track of time. You know you would just go into aol, right? And you wouldn't go to a bunch of websites. The content you looked at was on one place. Or I remember Yahoo, the Yahoo homepage. Like you would spend a lot of time on Yahoo. You wouldn't just bounce around to lots of websites. I wonder if in the future we will all have our own interface to the web and that interface could be one single app that we've created with some agent that looks in shapes and feels exactly like we want it to. Or maybe we don't even interface with it on an app at all. Maybe it's just a text based interface. Maybe it's kind of like if you've seen the movie her, it's just something you can talk to. And that app, that interface connects to everything else. So do I ever need to go to my bank's website to do anything? If I could interface with it by just asking. And I'll use Siri as an example here. But if every time I wanted I could say, hey Siri, how much money is in my checking account? Hey Siri, can you transfer a hundred dollars to my friend? Imagine that world where you could just talk like that and interface with all the different services you have, right? If you have a meal planning app, you could say, hey, what's for dinner tonight? What's the recipe? Can you add this to my grocery list? Can you order it on Instacart? And all that stuff can happen, but you don't actually have to go into any of those individual apps or go to any of those websites. And so what that requires or what needs to happen for that to work is that everything needs to talk to everything. And right now the kind of way a lot of those things happen is opening a browser window and browsing to it. And if you've ever synced a bank account using a fintech app or some banking app or a net worth tracking tool, most of the time you'll see plaid or Yodlee or something pop up and it says, you know, enter your login and this third party service will, will connect with the bank. Well, four or five years ago, the way that third party service worked is that they had a little browser instance in the cloud on a server somewhere that would open up the bank and log in. Which is why if anyone used these tools, they broke all the time because the bank would change something about the interface of their website and then these kind of third party aggregator tools would have to go re quickly build the tool and over and over again. Then eventually a lot of the mainstream banks added an OAuth service which is you kind of redirect yourself to the bank's website, you log in there and it says, hey, would you like to allow this third party to have access to this limited set of data? And you've probably done that anytime you sign in with Google or you know, back in the day, if you signed into a lot of things with Facebook, use your Facebook login as the way you authenticate and it would share certain piece of information or maybe you do that with Google and now you share your calendar with a tool. And so I think that there's going to be a lot more of that happening and as people have their own interfaces to lots of different things.
