Packages

Regent SDK is organized as a monorepo with packages in layers:

Architecture

┌─────────────────────────────────────────────────────────┐
│                    Unified Package                       │
│                      regent-sdk                          │
└─────────────────────────────────────────────────────────┘
                            │
┌─────────────────────────────────────────────────────────┐
│                    Developer Tools                       │
│               @regent/cli  │  @regent/regentx            │
└─────────────────────────────────────────────────────────┘
                            │
┌─────────────────────────────────────────────────────────┐
│                   Framework Adapters                     │
│         hono  │  tanstack  │  express                   │
└─────────────────────────────────────────────────────────┘
                            │
┌─────────────────────────────────────────────────────────┐
│                      Extensions                          │
│   http │ x402 │ erc8004 │ a2a │ wallet │ ap2            │
└─────────────────────────────────────────────────────────┘
                            │
┌─────────────────────────────────────────────────────────┐
│                         Core                             │
│                     @regent/core                         │
└─────────────────────────────────────────────────────────┘
                            │
┌─────────────────────────────────────────────────────────┐
│                        Types                             │
│                     @regent/types                        │
└─────────────────────────────────────────────────────────┘

Dependencies flow downward. The core runtime is protocol-agnostic; HTTP is provided as an extension.

Unified Package

• regent-sdk - Re-exports all packages with high-level APIs (createRegentAgent, createRegentSDK)

Foundation

• @regent/types - Shared TypeScript type definitions

• @regent/core - Protocol-agnostic agent runtime with extension system

Extensions

Optional capabilities you can add to your agent:

• @regent/http - HTTP request/response handling and SSE streaming

• @regent/x402 - x402 payment protocol for monetizing agents

• @regent/erc8004 - ERC-8004 on-chain identity, discovery, and reputation

• @regent/a2a - Agent-to-Agent protocol for discovery and communication

• @regent/wallet - Wallet connectors for agent operations

• @regent/ap2 - Agent Payments Protocol extension

Framework Adapters

Integrate agents with your preferred web framework:

• @regent/hono - Hono framework adapter

• @regent/tanstack - TanStack Start adapter (UI and headless)

• @regent/express - Express framework adapter

Supporting Packages

• @regent/scheduler - Scheduled agent invocations

• @regent/analytics - Payment tracking and reporting

Developer Tools

• @regent/cli - CLI for scaffolding new agent projects (templates + adapters)

• @regent/regentx - CLI for managing agents on-chain (factory + ERC-8004)

Package Matrix

Package	Purpose	Required
regent-sdk	Unified SDK with high-level APIs	No (convenience)
@regent/core	Agent runtime	Yes
@regent/types	Type definitions	Yes
@regent/http	HTTP extension	For web servers
@regent/x402	Payment protocol	For monetization
@regent/erc8004	On-chain identity	For registration
@regent/a2a	Agent communication	For multi-agent
@regent/wallet	Wallet management	For payments/identity
@regent/ap2	Agent Payments Protocol	Optional
@regent/hono	Hono adapter	Choose one
@regent/express	Express adapter	Choose one
@regent/tanstack	TanStack adapter	Choose one
@regent/cli	Project scaffolding	Development
@regent/scheduler	Scheduled tasks	Optional
@regent/analytics	Payment analytics	Optional