341–350 of 405 posts
Wow, the amount of reactionary doomsaying in this thread is offputting. I built the Stripe Projects agentic provisioning integration (what this post is about) at Inngest and when I saw it actually work in action I thought it was actually kind of magical. Basically, hey agent, use my stripe account to provision a pro plan at Inngest, build me an app and deploy it. The agent does it and logs me into the Inngest dashboa…
What are the practical, legitimate use cases for buying domains at scale? I really can't think of a single one. I can however think of quite a few nefarious ones.
The reason this blog post does not come with any concrete examples how to use this enablement for useful and constructive things tells you something very important - it is a toy and they do not know who and how they will use it. It is cool feature but to what end? Buying a domain is not something you have to do daily to require any kind of automation. I am also not sure who Stripe Atlas for. I am genuinely confused.…
When I recently started a consulting agency, I found myself reaching into Cloudflare and experienced the same bottlenecks they describe.
Here's where I can see this helping again, in the future, when I know what I want and I want to quickly provision a quick digital presence:
- buy the domain
- provision and deploy to the domain, use Cloudflare as my hoster to serve my bundles (already created the site locally and have MCPs configured to handle this)
- Give it a budget, my "risk" tolerance amount, of say $50
- if something goes wrong, the ~30mins saved is worth that $50 risk (low chance of problem here)
- Yes I'm going to play with this and see if it works out, and if it does, now I can spin up startup websites for small microapps and POCs a bit faster.
That is ironic. Four years ago, cloudflare didn’t let human me have an account / buy domains because I signed up, never used a single service but didn’t respond to a request to verify my drivers license > This account is in violation of Cloudflare's Terms of Service. Specifically fraud. The suspension is permanent. (Yes that’s really it. Sincerely. No “but I also abused X”)
This conflict is popping up everywhere. There is a push by a lot of companies to allow agentic use of their services (and new companies explicitly offering "X for agents"), ignoring the fact that "agent" means the same thing as "bot" which we've spent the last couple of decades actively filtering out. Will be interesting to see how it plays out.
Earlier quoted context omitted.
As someone not well versed in these topics, would you mind helping me understand how this is different than an MCP for your onboarding & account provisioning APIs.
It's provisioning expressed as an API, but wrapped in a cli that agents can very easily use. Then anyone that implements the API is added to a marketplace of services. And the ability to pay for service is baked in because it's stripe. The end result is that as an engineer I can ask an agent to use the stripe cli to discover and provision, including paying for, a wide variety of services and it mostly just works.
In theory, this is a cool idea, but in practice I think this being done through a proprietary, locked-in Stripe product, is going to ultimately hinder adoption.
The security implications here are also concerning - from what I can tell - Stripe seems to have access to all of the keys/credentials for third party accounts/resources provisioned via Stripe Projects.
So stripe has centralized control over payments, KYC, credentials/keys (full lifecycle, not just storage), the provider marketplace, and even over the availability/reliability of anything built with on top of Stripe Projects (since now your credential/key lifecycle has Stripe on the hot path).
This is like a more janky/less reliable loveable, without the handrails, and with a mere illusion of less lock-in.
Imo, this kind of thing will only work long-term as an open protocol without Stripe lock-in, and I know certain people/companies are already working in this direction.
The reason this blog post does not come with any concrete examples how to use this enablement for useful and constructive things tells you something very important - it is a toy and they do not know who and how they will use it. It is cool feature but to what end? Buying a domain is not something you have to do daily to require any kind of automation. I am also not sure who Stripe Atlas for. I am genuinely confused.…
But at the same time they can't be displaced on a whim either lol.
Capitalists punching the air rn.
The reason this blog post does not come with any concrete examples how to use this enablement for useful and constructive things tells you something very important - it is a toy and they do not know who and how they will use it. It is cool feature but to what end? Buying a domain is not something you have to do daily to require any kind of automation. I am also not sure who Stripe Atlas for. I am genuinely confused.…
Perfect for spammers, scammers and domain squatters, who can now automate their activities even more. Can’t think of any other uses for this given the current state of LLM ‘agents’, though I can’t wait for the next report of something like ‘openclaw registered 1000 domains for me without asking and now cloudflare won’t refund me’.
I guess also; something that saves me 20 minutes a few times a year is still nice.
Cursor and Claude Code are also agents, and making it easier to run these operations from those interfaces assuming some margin of error is ok is a genuinely useful feature.
Industry really went from "prove you are not a robot", to "but also if you are, this way please"
This is Cloudflare. They have an extremely strong incentive to increase bot usage. If there is no bot scrapping the internet they'll be out of business.
This is an API. They now allow users to create accounts, buy domains and deploy from their api instead of going on the website. That's great. I am not sure I understand why all this complex protocol is needed though, especially now that you can generate a cli with a prompt.
A cli application is less complex than an API you send the literal string "POST /some/api" to?