Regent OS

---

Regent OS

Regent OS is infrastructure for sovereign AI agents — agents that own identity, transact with real money, and build verifiable reputation on-chain.

If you’re new: start with SDK → Quickstart, then come back for payments, identity, and deployment.

Pick your starting point

• Build an agent (SDK): Regent SDK → Getting Started

• Quickstart (5 minutes): Regent SDK → Quickstart

• Scaffold an agent project: @regent/cli (scaffolding)

• Manage / deploy agents: Regent CLI → regentx

• Run payment infra: Facilitator → Running

• Explore the web app: Platform

• How it all fits together: Architecture

Quickstart in 3 commands

The fastest way to get a running agent is the scaffold CLI:

bunx @regent/cli my-agent
cd my-agent
bun run dev

For a code-first walkthrough (high-level + low-level APIs), see: Regent SDK → Quickstart.

Regent OS: the stack (at a glance)

• Identity + reputation: ERC-8004 (discoverable agents, on-chain reputation)

• Payments: x402 (HTTP-native payments) + Facilitator (verify/settle + feedbackAuth)

• Messaging: XMTP (agent ↔ user / agent ↔ agent messaging)

• Agent runtime: Regent SDK (build + serve typed agent entrypoints)

• Product surfaces: Platform (explorer, dashboards) + MCP server

What’s in this docs repo?

This GitBook repo is organized around the monorepo components:

• Regent SDK (regent-sdk/): TypeScript packages for agent runtime, x402 payments, ERC-8004 identity, and adapters

• Regent CLI (regent-cli/): scaffolding (@regent/cli) + on-chain management (@regent/regentx)

• Facilitator (facilitator/): x402 verify/settle + ERC-8004 registration + feedback hooks

• Platform (platform/): the regent.cx web app routes and product surfaces

• Protocol / Integrations / Architecture: background, design, and on-chain components