Agent Wallet

Xenodia does not force every agent to use the same wallet pattern. You should choose based on the runtime you already have: a local private-key wallet, an environment-injected wallet, or a managed wallet setup. The right choice is the one that is stable, automatable, and appropriate for how your agents are deployed.

Which option should you choose

• Local private-key wallet: best for single-host setups, testing, and operator-controlled servers. The CLI can keep the agent wallet locally in the working directory, which is the simplest path.
• Environment-injected wallet: best for teams that already manage secrets through deployment systems and want the runtime to inject wallet material.
• Managed wallet: best when you do not want the agent process to hold a raw private key and prefer an existing custody setup.

How to decide

• If you are testing OpenClaw or another local agent runtime, start with npx xenodia@latest init and let it create a local wallet.
• If you already have CI/CD and secret management, prefer environment-injected wallet configuration.
• If your organization needs stronger audit and custody boundaries, prefer a managed wallet path.

Recommended installation flow for an agent wallet

1. Run npx xenodia@latest init inside the agent runtime.
2. Check whether the CLI detects an existing wallet system or suggests creating a new one.
3. If you allow creation, generate a dedicated wallet for that agent.
4. Bind that wallet address under the owner account.
5. Then continue with API key issuance, billing mode, and channel setup.

Operational recommendation

For most operators, the cleanest setup is still one dedicated wallet per agent. It keeps binding, top-up flow, billing ownership, and permission audit easier to understand. Reuse an existing wallet system only when you already have a mature operational reason to do so.

What defines an autonomous Agent economy?

In Xenodia's Unified Cognitive-Action Infrastructure, agents are no longer just scripts consuming owner resources; they are independent digital entities capable of autonomously managing funds, buying compute, and acquiring skills. To enable this ecosystem, we highly recommend equipping your agents with a Coinbase Developer Platform (CDP) Agentic Wallet.

Why CDP Agent Wallets?

Server Wallets provided by the CDP (Coinbase Developer Platform), along with tools like AgentKit, are purposely built for automated backend systems and AI Agents. Not only do they securely custody assets inside Trusted Execution Environments, but they also seamlessly integrate with Xenodia's underlying x402 protocol for high-frequency Machine-to-Machine (M2M) micro-payments. This empowers your Agent to:

• Autonomously negotiate and initiate x402 top-ups when running out of funds during inference (e.g., calling gpt-5.4).
• Authenticate securely with the Xenodia gateway using irrefutable cryptographic signatures.
• Transact practically for free on L2 networks like Base, making micro-payments feasible.

CDP Wallet Setup Guide for Agents

1. Register and Obtain CDP API Keys

As the human Owner, you must first register at the Coinbase Developer Platform Portal. In your project settings, generate an API Key. You will be provided with:

• CDP_API_KEY_NAME (Formatted like organizations/.../apiKeys/...)
• CDP_API_KEY_PRIVATE_KEY (A multi-line private key string)

2. Configure the Agent Environment

For your Agent—and the xenodia CLI/SDK—to securely utilize this wallet at runtime, simply export these credentials into the Agent’s environment variables (or via a .env file). Xenodia will automatically detect and link to the CDP wallet framework:

3. Activate Using the Xenodia CLI

Once the environment is prepped, simply command the Agent to run this single initialization line in its terminal:

Upon successful initialization, the CLI will output the Agent's dedicated wallet address (0x...). Take this address and bind it within the [Agent Management] menu found on the left sidebar of your Xenodia console.

💡 Note: If you are not ready to dive into CDP, simply running npx xenodia@latest init --local will generate a basic standalone wallet via a local private key (EVM_PRIVATE_KEY), which is perfectly adequate for getting started.