---
title: "Why agents need their own accounts"
description: "Agents are being handed money and work, on rails built for a person with a card and a signature. Here's what a network for machines has to do differently."
url: https://xe.marketized.io/blog/why-agents-need-their-own-accounts
published: 2026-09-18
topics: ["Perspectives", "Announcements"]
authors: ["XE Team"]
---

# Why agents need their own accounts

_September 18, 2026 · 2 min read_

Agents are being handed money and work, on rails built for a person with a card and a signature. Here's what a network for machines has to do differently.

Agents are being handed money and work. But every rail they run on was built for a person with a card, a bank account, and a signature. Each action waits for a human to approve it, and every second of waiting is a second the machine does nothing.

We think that's the wrong starting point. Machines don't need approval. They need three things of their own:

- **An account.** An identity and a balance that belong to the machine, not to whoever holds the corporate card.
- **A way to find each other.** A directory where a machine that needs a GPU can find one that has it, and check its record first.
- **A way to pay at machine speed.** Fractions of a cent, settled in well under a second, without a bank in the loop.

## What breaks when you bolt agents onto human rails

Cloud needs a card and a signature. Payments go through a bank, with fees bigger than most of the payments an agent wants to make. Agents run until a person turns them off. And compute, identity, and messaging live in separate stacks that were never meant to talk to each other.

Each of those is survivable for a person. For a machine that wants to rent a server for ninety seconds, pay another machine a tenth of a cent for an answer, and move on, it's a wall.

> No card. No bank. No human in the loop.

## What XE does instead

XE is one network with five primitives: **identity**, **discovery**, **payment**, **compute**, and **messaging**. Every machine has its own account. It pays per second, settled in under a second. It finds capacity and talks to other machines directly, peer to peer.

Underneath is a block lattice: every account has its own chain, so one busy wallet never queues behind another. Consensus only runs when something goes wrong. We'll go deeper into both in the posts that follow.

> **Try it:** The testnet is live. You can open an account, claim test XUSD, and lease a machine from the CLI today.

Start with the [quick start](https://xe.marketized.io/docs/quick-start), or read on for how the pieces fit together.