Live data from Hacker News

Temporary Cloudflare accounts for AI agents

blog.cloudflare.com

131–140 of 173 posts

Re: Temporary Cloudflare accounts for AI agents

#131

Earlier quoted context omitted.

I've dealt with this before. The problem with doing a billing cap is that now you are bringing an out-of-band batch system (billing) in-band. The only way to do a dollar cap is to constantly calculate your bill. Capping it at 100K requests is a lot easier, because it's a single number that can be incremented easily in a distributed way. It's the same reason it took AWS forever to offer billing caps, and even today, t…

How about implementing a prepaid system where you set your budget, and if you exceed it, everything just pauses until you pay more?

That wouldn't change anything in this case. Either way you would need to (a) be able to know the state of billing in band before executing a request or (b) accept a slight out of band delay where cloudflare may allow a few extra requests through and eat the cost.

It is a very solvable problem, I just don't think pre- vs postpaid changes it.

Re: Temporary Cloudflare accounts for AI agents

#133
post #47

Looks like Cloudflare still haven't shipped the most valuable possible feature for Cloudflare Workers though: hard billing caps. I want to set a cap of $100/month and know, for sure, that if something untoward happens my apps will all stop serving traffic rather than me getting hit with a bill for $1000s. The safest way to use Workers is on the free tier, which will shut off after 100,000 requests/day: https://develo…

I've dealt with this before. The problem with doing a billing cap is that now you are bringing an out-of-band batch system (billing) in-band. The only way to do a dollar cap is to constantly calculate your bill. Capping it at 100K requests is a lot easier, because it's a single number that can be incremented easily in a distributed way. It's the same reason it took AWS forever to offer billing caps, and even today, t…

Vercel achieved it perfectly fine

Re: Temporary Cloudflare accounts for AI agents

#134

Cloudflare: let's give the bots their own accounts so they can scrape harder. Also Cloudflare: let's send normal humans who are trying to go about their daily lives into endless Turnstile spinner loops with absolutely zero recourse, grievance, or support infrastructure.

Bots are very close to being able to pass any captcha a human can. We're very close to most sites requiring a login.

Re: Temporary Cloudflare accounts for AI agents

#136
post #24

Hot damn... > Any agent can now run wrangler deploy --temporary and deploy a Worker to Cloudflare. This temporary deployment stays live for 60 minutes, during which time you can claim the temporary account, making it permanently your own. If you don't, it expires on its own. Forget about agents, Cloudflare just provided free scratch deployments - ephemeral for 60 minutes - for anyone . This is going to be amazing for…

> This is going to be amazing for things like PR previews and code review. Being able to deploy a preview to a working URL for free is a huge reduction in friction.

Uh that's already true?

Re: Temporary Cloudflare accounts for AI agents

#137

Lets keep in mind this is cloudflare workers runtime - it only makes sense to deploy small things there, maybe static sites. Unless the agent creates something for cf workers from scratch, asking it to „now deploy to cloudflare” will fail so bad. This would only work if they would provision docker image deployment, similar to google cloud run, but the still, everything serveless has its own caveats…

This is just objectively wrong, CF hosts an app for me with 1 million MAU

Re: Temporary Cloudflare accounts for AI agents

#138
post #30
post #25

Earlier quoted context omitted.

I just tried this out: % npx wrangler deploy --temporary wrangler 4.103.0 ──────────────────── You must accept Cloudflare's Terms of Service (https://www.cloudflare.com/terms/) and Privacy Policy (https://www.cloudflare.com/privacypolicy/) in order to continue. By typing "yes", you agree to these terms. Type "yes" to continue. … yes Solving proof-of-work challenge… Temporary account ready: Account: Educated Celery (c…

> I'm amused that it made me accept the terms and conditions without any indication of who I am as far as i’m aware, that’s fully binding and often an accepted practise - take Minecraft’s server software, where you must accept the EULA with a text flag before running

This has never been tried in court, though, at best it probably just protects mojang from liability for banning your server from the IP address entry box (that's a real thing they do) if you don't obey

Re: Temporary Cloudflare accounts for AI agents

#139
post #14

Earlier quoted context omitted.

> Would love to know more about how Cloudflare plans to prevent abuse of ephemeral infrastructure to host malicious content If it helps laugh DDoS attacks they would be incentivized to do the exact opposite. They can charge more for “protection” then.

DDoS is one thing you wouldn't be launching from Cloudflare, but if they can get enough types of other bot traffic (whether malicious or "legitimate" or just general grey zone) to use them as the starting point, it improves their error rates when dealing with bot traffic that didn't migrate.

Cloudflare knowingly protects DDoS services' payment systems.

Re: Temporary Cloudflare accounts for AI agents

#140
post #47

Looks like Cloudflare still haven't shipped the most valuable possible feature for Cloudflare Workers though: hard billing caps. I want to set a cap of $100/month and know, for sure, that if something untoward happens my apps will all stop serving traffic rather than me getting hit with a bill for $1000s. The safest way to use Workers is on the free tier, which will shut off after 100,000 requests/day: https://develo…

This smells like a cottage industry similar to detecting soon to be expired ssl certs.

"Oh that thing that was an experiment and had billing caps turned on but we rushed in to production and now the whole business relies on that thing is in an outage and destroying customer trust we've barely earned yet"

I get the flip side but... 2nd order effects oof.

Post reply on HN