lucid-agent-editor

To update a Lucid agent configuration via the API, send a PUT request to /api/agents/:agentId with modified fields like entrypoints or paymentsConfig. You must include valid PAYMENT-SIGNATURE headers or session cookies to authenticate the update for agents you own.

You can authenticate Lucid agent edits using three options: MCP Tool with SIWE (Sign-In with Ethereum), SDK with a wallet, or Viem with custom signing. Requests require either a PAYMENT-SIGNATURE header or session cookie authentication.

Yes, you can modify a production Lucid agent's payment configuration by sending updates to the paymentsConfig field via the API. This allows you to adjust payment settings without needing to recreate the agent from scratch.

You can modify the enabled, name, description, entrypoints, paymentsConfig, walletsConfig, and analyticsConfig fields. These updates are performed through PUT endpoints to change metadata and configurations across agents you own.

SIWE (Sign-In with Ethereum) enables wallet-based authentication for Lucid agent updates by generating a cryptographic signature. This signature is passed via PAYMENT-SIGNATURE headers to verify ownership before applying configuration changes through the API.

No, you do not need to recreate an agent to change its entrypoints or description. You can directly update these fields on existing agents you own by sending a PUT request with the new values and valid authentication to the API.