Lucid Agents Docs

Build, buy, and operate typed machine services with x402 as the default payment rail.

Lucid is the TypeScript application runtime for machine commerce. The verified Stable path turns a function into a typed x402-paid service and keeps payment admission, fulfillment, and retries in one runtime contract. The Next repository adds the newer extension architecture, MPP integration, and owned task runtime documented on pages marked Next.

What are you building?

A paid API

Complete the primary seller path from schema to testnet settlement.

A service buyer

Call x402 endpoints from a wallet constrained by recipient and spend policy.

An existing web application

Keep your framework and add one shared Lucid runtime.

An agent-framework or MCP integration

Keep orchestration in its owning framework and connect through the paid HTTP service boundary.

A production deployment

Choose durable state, security, observability, facilitator, and adapter controls.

Where Lucid fits

Your typed capability and fulfillment
              ↓
Lucid: schemas, policy, authorization, fulfillment, discovery, state
              ↓
x402 payment negotiation (Stable); x402 or MPP on qualified Next pages
              ↓
Wallet + facilitator + network/provider infrastructure

Lucid does not replace wallets, facilitators, networks, or payment protocols. It makes them usable as part of a coherent application transaction.

Read When to use Lucid for a concrete decision table, including when the official x402 SDK is the smaller integration.

Read the status badge

The repository is ahead of the public package set. Every page states whether it describes Stable npm packages, the Next repository surface, an experiment, a deprecated migration, or a separately operated hosted product. See release channels before combining examples.

Current x402 scope

Lucid currently supports x402 v2 fixed-price exact payments. It does not yet expose upto, batch settlement, Bazaar publication, payment identifiers, signed offers/receipts, or gas-sponsorship declarations. Buyer and seller network support also differ. Use the x402 support matrix as the source of truth.

The fastest proof is the paid API quickstart: an unpaid request returns 402, then a funded testnet buyer signs and retries.

Lucid documentation