lucidAGENTS
Packages

Packages

Reference map for the open-source Lucid runtime packages.

Lucid is a typed extension runtime with one canonical capability registry and one HTTP authorization transaction. Start with a task guide; use this section when you need the exact boundary of a package.

This index describes the current repository. Package versions are independent, and some Next packages are not published. Use the release channel table for clean installs.

Runtime layers

LayerPackagesResponsibility
Contracts@lucid-agents/typesCanonical cross-package protocol and runtime types
Kernel@lucid-agents/coreExtension lifecycle and one capability registry
Transport@lucid-agents/httpFetch handlers, route plan, SSE, authorization transaction
Commercepayments, mpp, walletReceive, buy, verify, enforce policy, and sign
Agent protocolsa2a, identity, ap2Discovery, tasks, trust, and role metadata
Operationsanalytics, scheduler, catalogReporting, recurring calls, and catalog-defined capabilities
Adaptershono, express, tanstackBind the same route plan to a framework
Toolingcli, deployGenerate projects and deploy guarded previews

Dependency direction

@lucid-agents/types

@lucid-agents/core + domain extensions

@lucid-agents/http route and authorization contract

Hono | Express | TanStack Start | generated Next.js modules

Adapters do not own paywalls, manifests, or a second registry. A domain package returns a complete runtime slice and core exposes it directly.

Which packages do I need?

For a Hono x402 seller:

bun add @lucid-agents/core @lucid-agents/http \
  @lucid-agents/payments @lucid-agents/hono zod

For exact Stable versions, use the pinned command in Install Lucid. Add wallet/A2A/identity only when the application needs outbound signing, agent discovery/tasks, or on-chain trust.

The generated Next.js adapter is not an npm package. The hosted Runtime API client is documented separately under Hosted Products because it has a different lifecycle and support boundary.

On this page