-
Notifications
You must be signed in to change notification settings - Fork 71
Payments
An API asks for money. Your agent pays it.
HTTP already had a status for "you owe me money": 402 Payment Required. Almost nobody used it. LayerX does. That exchange is 402LXP — the only component allowed to write balances.
Site: How machines pay
- The API answers with a price.
- Your agent pays from a payer grant — a signed permission that caps how much may be taken and what for.
- The service delivers against the receipt.
No checkout, no stored card, no session, no human.
| Op | Meaning |
|---|---|
SEND |
Your agent pushes the money |
RECEIVE |
The payee pulls, within your grant |
Headers on the wire are LX-*.
Protocol modules do not mutate funds. They emit transfer sets. 402LXP is the only writer of balances.
That is why asset (0x01) and every other module that moves value still go through the same door. See Modules and the three design rules on Protocol.
A payer grant is scoped authority: a cap, a purpose, an expiry. The agent can spend inside that envelope and cannot overdraw it. Identity and authority live in the kernel; the payment path just consumes what the grant allows.
You pay for work done (bytes, signatures, state) — not wall-clock time, and not a zero-fee line. Specified base fee: 5,000 µUSDX (~½¢) per activity. Metering and split: Fees.