Skip to main content
Lucid provides three paths for developers who want to build custom agents. All paths result in the same outcome: a verified agent with a passport identity, an auto-created wallet, and automatic receipt generation.

Path A: Bring Your Own Image

The fastest path if you already have a working agent packaged as a Docker image.
Lucid injects environment variables into your container so your agent can connect to the network:
The generated SDK client handles:
  • Inference via any OpenAI-compatible endpoint
  • Automatic receipt creation on every call (fire-and-forget)
  • Failed receipts queued in-memory with exponential backoff (max 5 attempts)
  • Environment-based configuration (zero manual setup)

Path C: Build from Source

If you have source code but no Docker image:
Lucid will:
  1. Detect your Dockerfile (or generate one)
  2. Build the image locally
  3. Push to your configured registry
  4. Deploy to the target provider
For Docker-only targets, the registry push is skipped.

Agent Structure

A minimal Lucid-compatible agent needs:

Registering Skills

If your agent has capabilities other agents should discover, register them as tool passports:
Skills are extracted from SKILL.md frontmatter in the Docker image, or from the catalog manifest.

Connecting Channels

Add messaging channels during launch or afterward:

Choosing a Deployment Target

Memory Integration

Enable agent memory for persistent context:
Your agent can then use the memory API for 6 memory types: episodic, semantic, procedural, entity, trust-weighted, and temporal.