Machines that transact — under rules

What is x402 settlement?

Machine-native payments. x402 turns the HTTP 402 "Payment Required" status into a real settlement rail: an agent (or a service) requests payment, the counterparty pays programmatically, and the action unlocks — no invoices, no human in the loop. Genesis402 runs monetized operator actions on this rail, settling on Apostle Chain 7332 and mirroring to the Unykorn multi-rail core.

What is the agent mesh?

A fleet of scoped, permissioned agents behind one operator console. Each agent has a defined capability, a budget, and — critically — no privileged path around the compliance gate. Every action an agent takes is a signed, replayable intent that a human can audit after the fact. Agents that can move value are the highest-risk component in any stack; here they sit above the spine, never beside the keys.

What is the Genesis Protocol engine?

A closed-economy simulation and settlement engine. Agents earn, conserve, and spend energy (denominated in ATP — Agent Transaction Protocol) to operate, with an autonomous treasury that redistributes revenue under deterministic rules and no human governance. It is the research-grade core (see Research) that proves the firm can model and run automated on-ledger economies and treasury logic.

How does compliance work here?

The same way it works everywhere in the Unykorn stack: as a gate, not a report. Every value movement — human- or agent-initiated — passes one AML/KYC/Travel-Rule check before it executes, and eligibility is enforced on-chain at the token boundary. Detail on the Unykorn trust center.