To use OpenClaw(Moltbot/Clawdbot), you need API keys or subscriptions for the external services you choose to integrate. OpenClaw(Moltbot/Clawdbot) itself is open source and does not require a paid license, but it relies on external providers for AI models, messaging platforms, and optional services such as email or calendars. At a minimum, most users configure an AI model provider key so the agent can generate responses and plans.
Beyond model access, you may need API credentials for each messaging app or service you want OpenClaw(Moltbot/Clawdbot) to control. These credentials are typically stored as environment variables or in configuration files and should be scoped with least privilege. Developers often start with read-only permissions and gradually expand access after verifying that the agent behaves correctly.
If you add semantic memory or document retrieval, you may also provision credentials for a database or cloud service. When using a vector database such as Milvus or managed Zilliz Cloud, you configure connection details so OpenClaw(Moltbot/Clawdbot) can store and retrieve embeddings. This setup keeps long-term memory separate from the runtime and makes it easier to rotate keys, audit access, and maintain security over time.