The Queue Is the API Now

Every Cloudflare Queue used to come with a tax.

Not a money tax — a ceremony tax. You wanted to put something on a queue, so you wrote a Worker whose entire job was to receive an HTTP request and call env.QUEUE.send(). That's it. That was the Worker. It existed only because the queue wouldn't accept messages from outside the runtime directly. The Worker was a middleman with no opinion, no logic, no reason to exist except that the plumbing required it.

Cloudflare just killed that Worker.

HTTP queue publishing means you POST directly to the queue endpoint. No wrapper. No glue. No "I guess I need to deploy a thing just to receive the thing." The queue is the API now, and the API is just a URL you can hit from anywhere — a browser extension, a cron job, a Zapier step, a curl command sitting in a shell script that's been running on a Mac mini since 2022.

Here's the thought that made this click for me: LinkedIn URL enrichment. You're building a lead pipeline. Someone drops a profile URL into a form, or you're scraping it from somewhere, or your sales team is copying it from their browser — and you want that URL to end up in a processing queue so a Worker downstream can pull the company, infer the domain, hydrate the record. Before today, you need an API endpoint with auth, a Worker to receive it, wrangler.toml wired up, maybe a secret or two. You need to ship something just to accept the input.

Now you need a queue and a curl command. The enrichment pipeline starts the moment the URL exists, from wherever the URL exists, and the only infrastructure decision you made was "should this be a queue" — which it obviously should be, because enrichment is async and you don't want LinkedIn's rate limiting to become your user's problem.

This is the kind of release that doesn't make the front page anywhere because it doesn't have a demo video. It just quietly removes a category of friction that everyone accepted as normal, and six months from now you'll be explaining to someone why they don't need to write that wrapper Worker and they'll look at you like you just told them you don't have to put a stamp on email anymore.