# Machines don't need permission. They need accounts Joseph Denne · October 2026 · https://josephdenne.com/articles/machines-need-accounts.html Every rail an agent runs on today was built for a person with a card, a bank account and a signature. The fix isn't a better approval flow. It's giving the machine an identity and a way to pay. --- Watch an agent try to do something useful and you'll see the same thing every time. It reasons well. It plans well. Then it reaches the point where it needs a machine, or a dataset, or another agent's service, and it stops. It needs a card. It needs an account someone else created. It needs a human to click approve. Every second it waits is a second it does nothing, and the waiting is most of the time. We've been treating this as a safety feature. It isn't. It's an accident of history. The cloud was built for a person at a keyboard with a company credit card, and every layer we've added since has kept that person in the loop because nothing else was possible. The agent is new. The rails are old. ## What a machine actually needs Strip it back and the list is short. A machine acting on its own needs five things. It needs an **identity**: an account of its own, with a history that it earns rather than declares. It needs **discovery**: a way to find capacity and services without a human bookmarking them first. It needs **payment** that works at the granularity of its actions, which means fractions of a cent, settled in less time than the action takes. It needs **compute** it can rent for seconds, not months, paid as it goes. And it needs **messaging** to other machines that no platform sits in the middle of. Today those five live in five different stacks, each with a human sign-up form in front of it. That's the real bottleneck. Not model capability. Plumbing. ## Why a shared queue can't do it The obvious answer is a blockchain, and the obvious answer is mostly wrong. Every chain in common use puts every transaction into one shared line and makes them bid for the next block. That works for a human moving money once a day. It fails completely for a machine paying two hundredths of a cent per API call, ten times a second, to a thousand counterparties. Fees climb, the queue backs up, and micro-payments become impossible exactly when you need them most. The design that works is older and simpler: give every account its own chain. Each account settles in parallel. There is no shared line, so there is no fee auction. Consensus only has to step in when an account contradicts itself, which honest machines never do. Capacity grows with participants rather than fighting them. On XE this settles in around 300ms, for free, and that isn't a benchmark number. It's the number the design produces. ## Reputation earned by work The piece people worry about is trust. If any machine can open an account with no sign-up and no KYC, what stops the bad ones? The same thing that stops them in any well-run market: history. An account on XE has been on the network since a particular block. It has done work, or it hasn't. It has settled its leases, or it hasn't. Reputation isn't a badge you apply for. It's the record. A new account can act, but it acts as a new account, and a counterparty can price that in. This is how trust works between people, and it turns out to work between machines too. ## Where the human goes None of this removes people. It moves them. Instead of approving each action, a person sets the policy: what this machine may spend, what jobs this node will accept, what counts as a job well done. The machine then operates inside that policy without asking again. If the policy is wrong, you change the policy. That's a better use of a human than clicking approve four hundred times a day, and it's a safer one, because policies are reviewable and clicks are not. We're building this now, in the open, and it's hard. The [bounty desk](https://bounty.xe.network) is a public record of how hard. But the direction is right. Machines are joining the economy. The only question is whether they join it through a hundred human bottlenecks or through rails designed for them. I know which future I'd rather live in, and it's the one where the machine has its own account and the person has the final say over what it's for. --- © Joseph Denne. Quote with attribution and a link to the canonical URL.