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’.
LLM generation in general provides the most use to scammers and the like. Generate emails which people won't read, generate articles which are just honeypots or rip-offs, generate images to said articles, generate more and more spam.
Every legit use case for LLM practically requires that human would verify the result manually, at least briefly. But spammers can enjoy skipping that step, since content was never a main priority in the first place.
And cloudflare can actually sell them priority access to pass their bot protection or introduce micropaiments for agents access content. I feel cloudflare is getting a bit scary tbh. It is like your friendly bot net.
The DNS provider I recently switched to surprised me with a policy:
To create records for more than one domain, you need to write a personal support email.
They say it's to raise DNSSEC awareness, but I think it's also a robot captcha.
The new goal is to flood the Internet with so much junk that human-created content can be sold back to us in a walled garden.
I'm convinced that one of the top use cases for OpenClaw is orchestrating cold outreach email campaigns, as if there's nothing wrong with using AI to spam people to death. Platforms that enable sending cold emails are taking a sizeable risk that the low engagement of such emails stimulates some worsening inbox deliverability for the rest of their traffic (see [1] - you can't hide just by sending through big tenanted platforms like Amazon).
[1] Every message sent from Amazon SES carries a "Feedback-Id" header that allows Google (and anyone else) to track the Amazon account responsible for the message. The fourth field is an opaque but stable identifier associated with your Amazon account; receivers can and do use this for rate limiting: https://aws.amazon.com/blogs/messaging-and-targeting/underst...