I personally think stuff like this should be made as protocols and done in the open instead
Avoid.
31–34 of 34 posts
I personally think stuff like this should be made as protocols and done in the open instead
Avoid.
In the era of enshittification I can't really see the logic in tying a bunch of your infrastructure/services to the likes of stripe. Then again I also don't see the logic in asking spicy autocomplete to write code or provision services for you either. Maybe I'm just not the target market. I guess if you're spinning up 5 new toy todo list apps a week to show off how well you can talk to a predictive text engine maybe…
“Spicy autocomplete” absolutely made my day. Thank you.
Earlier quoted context omitted.
I'm going to guess that signing up for stripe is a prerequisite to use this. I will try it out later and confirm. I think I just got access. EDIT: The linked docs from their blog post point to a login step after you install it. So yeah, signing up for stripe is a prereq.
So you handover access to stripe to your AI agent? Is this how this works?
You would hope that you can set overall and per-integration billing caps on things rather than just "spend any money on my linked credit card" if it's meant for a "humanless" loop to be able to run stuff off.
I think there is still room, since, as I understand it, I do not want coding agents to use the same account that I end up using. I understand that some users may not care, but I think agents should have their own accounts and the ability to create their own accounts and use services like Vercel, Supabase, etc.
Sign in to your Stripe account. Associate your existing provider account (or create a new one) with stripe projects link. Add a payment method with stripe projects billing add. Start the agent session.
This is a note in their docs. I think there still needs a better way for autonomous agents.