Creating accounts and managing billing across multiple platforms is a real pain. This is a good solution, but I’m wondering if this should be more like an open standard that platforms implement, with Stripe providing a way for platforms to charge and optionally for users to pay (in addition to credit cards, wallets like Tempo, etc)
Use cases: create accounts, set up billing, manage secrets, manage resources, get invoices/receipts
Finally, I don’t know if it’s better to use a CLI imperative approach or a more declarative one like IaC
steve_adams_86•4m ago
That last part struck me as well. I don't want an imperative solution, but... I'm not sure if that's just me.
Declarative solutions are perfectly fast and capable as well. They can use all the same tooling under the hood. Why choose imperative? At least I can record, validate, and version control a declarative solution. And imperative process is nice for exploration and one-off needs, but... I don't know when I'd really need that or when that's a bottleneck for me.
And I get that this is probably more of a tool for agents than humans, despite that agents are only mentioned in passing. But that's even more concerning in a way. I'm not yet comfortable with giving them tools like this.
tom1337•7m ago
Nice idea, but I'd love a more open approach to this (or more support for OpenTofu / Terraform). This is just another vendor-locked-in way and might only work with selected platforms.
Stripe has the incentive to add platforms that use Stripe as a payment processor so they can cash on the payment fees, they don't really have any incentive to add a platform that doesn't bring money to them (except affiliates are possible with this)
skybrian•6m ago
Sadly it doesn’t seem to do anything innovative to protect your api keys from getting exfiltrated by tricking the AI. Looks like they are stored in an ordinary config file:
gonzalovargas•25m ago
Use cases: create accounts, set up billing, manage secrets, manage resources, get invoices/receipts
Finally, I don’t know if it’s better to use a CLI imperative approach or a more declarative one like IaC
steve_adams_86•4m ago
Declarative solutions are perfectly fast and capable as well. They can use all the same tooling under the hood. Why choose imperative? At least I can record, validate, and version control a declarative solution. And imperative process is nice for exploration and one-off needs, but... I don't know when I'd really need that or when that's a bottleneck for me.
And I get that this is probably more of a tool for agents than humans, despite that agents are only mentioned in passing. But that's even more concerning in a way. I'm not yet comfortable with giving them tools like this.