SOLUTIONS · PAYMENTS

Money that moves as fast as machines.

Payments at machine speed.

Per second, per call, per use. Payments small and fast enough for machines to pay each other.

See what’s builtTalk to us
XE FOR PAYMENTS

Payments sized for machines. Payments are final in 300ms, moving value costs nothing, and a $0.001 payment settles like any other. Every account has its own chain, so a payment never queues behind anyone else’s.

THE PROBLEM

Payments were built for people.

Card rails, monthly invoices and fees that swallow small amounts. Machines work in seconds and cents.

Today
Fees bigger than the paymentA few cents of work can’t carry a fee that costs more than the work.
On XE
Final in 300msTransactions settle in a fraction of a second, with no fee auction.
Today
Settled in daysInvoices, net-30 and chargebacks. A machine can’t wait a month to be paid.
On XE
Fractions of a centSmall enough to pay per call, per second, per use.
Today
A human on every accountEvery rail wants a person, a bank and a card.
On XE
Escrow, released per secondThe budget is locked up front and released for every second of work.
Today
Paid for the month, not the workMonthly plans charge for the time you didn’t use.
On XE
Accounts for machinesAgents and robots hold their own account, with no human card behind them.

Machines work in seconds and cents. Their money should too.

PAYMENTS ON XE

On XE, payment is part of the network.

Escrow, per-second release and accounts for machines are built in, so value moves the moment the work happens.

Built on
IdentityDiscoveryPaymentComputeMessaging
  • Built for · 01Platforms billing usageCharge by the second, not by the month.
  • Built for · 02Agent and API buildersGet paid per call, in fractions of a cent.
  • Built for · 03Finance and operationsBill every team for exactly what it ran.
WHAT YOU CAN BUILD

Five ways machines pay and get paid.

Each one is built from the same products and primitives. Pick one to see what it may reach, how it’s paid and what it’s made of.

  1. Reaches
    Only what the job declaresPayment moves between accounts. The job itself declares what access it needs.
    Paid
    Per second, from escrow
    Built with
    PaymentXE ContractsXE Machines
WHY IT’S FAST

Your own chain, not a shared queue.

On most chains every payment waits in one line and bids for a place. On XE every account writes its own chain, so a payment never waits behind anyone else’s.

A shared chainOne queue
  • Every payment waits in the same line.
  • A busy network means higher fees for everyone.
  • A $0.001 payment isn’t worth sending.
On XEEvery account, its own chain
  • Each account writes its own chain.
  • Nothing queues behind anyone else.
  • A $0.001 payment stays a $0.001 payment, final in 300ms.
ONE JOB, END TO END

A budget, released by the second.

Escrow is part of the network, not an app on top. Each step lights the part of the network it runs on.

Your side
Whoever paysA person, agent, robot or team
Whoever is paidA machine owner, service or API
Products · this step needs none, it’s the network itself
XE MachinesRental billed to the secondXE ContractsBudgets released per secondXE ImagesOne-click, checked setupsXE NetsUsage billing on your hardware
Primitives
IdentityAccounts for agents and machinesDiscoveryFind work and capacityPaymentEscrow, release, final in 300msComputeThe work the payment is forMessagingTerms agreed before money moves
The network
Every account has its own chainFinal in 300ms · Zero fee · 1M+ TPS
FOR BUILDERS AND AGENTS

Pay for the work, as it happens.

Every contract carries its own payment terms: a ceiling per second, a budget in escrow, and what happens to the rest.

For builders
render_farm.xeXE Contract
1contract render_farm {
2  // two hundred machines, paid per second of work
3  image    = "acme/blender:4.1"
4  cpu      = 16
5  memory   = "64 GB"
6
7  network  = none
8  machines = 200
9
10  pays     = up_to(0.0004 XE/s)
11  budget   = escrow(900 XE)
12  refund   = on_stop   // the rest returns at once
13}
01The budget is locked before a single machine starts.
02Each machine is paid for the seconds it worked, and no more.
03Stop early and the unused budget comes straight back.
For agents
Open an escrow, pay a call, close it.Three commands, from the agent’s own account. Nothing waits for a bank, and nothing is charged for moving the money.
PAYMENT MODELS

Six ways work gets paid.

All of them settle the same way: final in 300ms, with nothing charged for moving the money.

Per secondEscrow, released as work happensA job’s budget is locked up front and paid out for every second of work. Stop early and the rest comes back.Machine rental, contractsPaymentCompute
Per callFractions of a cent, each requestAn agent pays for every call from its own account, settled before the answer comes back.APIs, models, agentsIdentityPayment
Per useMachine to machineA robot pays the charger, the lift or the robot that finishes its delivery, each time it uses them.Robots, devicesPaymentMessaging
Per bootA royalty every time it runsPublish an image once, and earn each time anyone launches it on any machine.Image and model authorsPaymentDiscovery
Per teamUsage billing, inside your wallsEvery team on your own hardware is billed for exactly the compute it used, by the second.Hospitals, universities, labsPaymentCompute
Fixed pricePriced in compute unitsPay in XE and it converts to compute units, so the price of the work stays fixed while it runs.Anyone buying computePayment
PROOF · LIVE ON XE

Thousands of machines, paid by the second.

Every machine on Edge Network is an account on XE, paid for the work it does. No invoices between Edge and the people whose machines serve its customers, and nobody waiting a month to be paid.

edge.network
Nodes online5K+
Paying customers3K+
Edge locations988
Network uptime100%
ShipsCDN · Compute · Storage · DNS · Shield
MachinesOwned by independent people, each an account on XE
Built on
IdentityDiscoveryPaymentComputeMessaging
GET STARTED

Get paid by the second.

Start buildingTalk to us
Page