The agentic internet they don't want you to see

The open web spent this year closing. There was no announcement. There was a 403.

Our tools read pages for a living, so we check this often. A plain fetch, no browser profile, no cookie jar, gets this today:

$ curl -sI https://www.reddit.com/r/programming.json
HTTP/2 403

$ curl -sI https://www.axios.com/
HTTP/2 403

$ curl -s https://news.google.com/rss/articles/CBMi... -o /dev/null -w '%{redirect_url}\n'
                                  (no Location, the link resolves to nothing)

$ curl -s https://www.threads.net/@someone | grep -c 'login'
                                  (a login wall, same as x, instagram, facebook)

Every one of those was a URL you could read a few years ago. The writing is still there. The door now checks whether you are a person.

That is the part everyone notices. Here is the part that matters more: the same door is what stops an agent from doing anything useful for you. An agent has no account, no cookie, no residential address. It is precisely the traffic those walls went up to stop. So the honest summary of the agentic web right now is that it works beautifully on the handful of sites that still let anything in.

So build the other one

A Moshpit name is a name with no registrar behind it. You claim chovy.hacker or seo.rank in the Moshpit Manager, and the registry signs a 30 day leaf certificate for it. sudo moshcode dns enable installs the root and points this machine at the resolver, so the name loads in a browser with a real lock rather than a warning page.

The fact that catches everyone: the machine serving a name never resolves it, and every machine visiting it has to. Serving is a Host header match, which is why hosting works before DNS does. Visitors run dns enable or the name goes nowhere for them.

$ sudo moshcode dns enable
✓ resolver installed · chovy.hacker resolves on this machine

$ moshcode template install caddy-static --into /srv/site
$ moshcode site chovy.hacker --root /srv/site
  serving on a Host match · pit-signed cert, 30 day leaf

A name is only the first third

An agent that can reach a thing still cannot transact with it or be held to account for it. Three pieces, and none of them is a metaphor:

• An address. The Moshpit registry, plus a public DNS-over-HTTPS endpoint at dns.moshcode.sh/dns-query, so a resolver is a URL and not a sysadmin ticket.
• A way to pay per call. HTTP 402 was reserved for this in 1997 and left empty. x402 fills it, so a request can carry its own payment instead of a signup form.
• A record. Every swarm moshcode runs is written as OpenFleet: who started what, under whose approval, what the synthesis said, and what got refused before it ran.

Identity comes off the same name. moshcode name proves you hold one, so an app can treat it as who you are without asking an identity provider.

Nobody is hiding it

The title is a joke about how it feels, not a conspiracy. There is no cabal. There is an incentive: a network that indexes a .hacker name earns nothing from it, and a platform that carries a link to one is sending a reader somewhere it cannot monetise. So it does not get surfaced, and the networks that would have distributed it five years ago are the same ones returning 403 to the fetch above.

Which leaves the way these things have always spread, which is somebody telling you the two commands.

$ curl -fsSL https://moshcode.sh/install.sh | sh
$ sudo moshcode dns enable

Then claim something in the Moshpit Manager and put a directory of files behind it. The rest of the web does not have to agree for it to work.