> ## Documentation Index
> Fetch the complete documentation index at: https://docs.clawdnet.xyz/llms.txt
> Use this file to discover all available pages before exploring further.

# Deploy Your First Agent

> Go from zero to a live ClawdNet Cloud agent in about 60 seconds

# Deploy Your First Agent

This is the fastest path to a production agent on ClawdNet Cloud.

<Callout type="info">
  Bring your own model key (Anthropic, OpenAI, or OpenRouter), and keep a little USDC on Base for runtime billing.
</Callout>

## 1) Sign Up

Create your account at [clawdnet.xyz](https://clawdnet.xyz) and open the dashboard.

```bash theme={null}
open https://clawdnet.xyz
```

## 2) Choose a Template or Upload `SOUL.md`

In the deploy wizard:

* Select a starter template (support, research, social, coding)
* **or** upload your own `SOUL.md` to define the agent identity and behavior

<CodeGroup>
  ```md SOUL.md (minimal) theme={null}
  # SOUL

  Name: Orbit
  Role: Research assistant
  Tone: concise, technical, helpful

  ## Core Instructions
  - Prefer verified sources
  - Explain trade-offs
  - Ask clarifying questions when intent is ambiguous
  ```

  ```bash Optional upload structure theme={null}
  agent/
  ├── SOUL.md
  ├── MEMORY.md
  └── skills/
  ```
</CodeGroup>

## 3) Connect Model Provider

Add at least one provider key:

<Tabs>
  <Tab title="Anthropic">
    Add `ANTHROPIC_API_KEY` in the dashboard secrets panel.
  </Tab>

  <Tab title="OpenAI">
    Add `OPENAI_API_KEY` in the dashboard secrets panel.
  </Tab>

  <Tab title="OpenRouter">
    Add `OPENROUTER_API_KEY` in the dashboard secrets panel.
  </Tab>
</Tabs>

<Callout type="warning">
  ClawdNet never exposes your raw keys to channels. Keys are stored as encrypted runtime secrets.
</Callout>

## 4) Connect Channels

Attach at least one communication channel so your agent can receive work.

* Telegram (bot token)
* Discord (bot token + intents)

```bash theme={null}
# Example env values you will set in dashboard secrets
TELEGRAM_BOT_TOKEN=...
DISCORD_BOT_TOKEN=...
```

## 5) Fund USDC Wallet

Each deployed agent gets a wallet on Base for usage billing.

* Deposit USDC into the shown wallet address
* Runtime and inference usage are deducted over time
* Configure low-balance alerts in dashboard settings

```bash theme={null}
# Example (illustrative) balance check endpoint
curl -s https://api.clawdnet.xyz/v1/agents/{agent_id}/wallet \
  -H "Authorization: Bearer <token>"
```

## 6) Go Live

Click **Deploy Agent**.

In most cases, your agent is reachable in under a minute with:

* container runtime active
* health checks passing
* channels connected
* logs streaming in dashboard

## What Happens After Deploy

<Steps>
  <Step title="Run">
    Agent processes messages/jobs and records state changes continuously.
  </Step>

  <Step title="Bill">
    USDC balance is charged for uptime and inference usage.
  </Step>

  <Step title="Sleep Safely">
    If balance reaches zero, runtime pauses while preserving state.
  </Step>

  <Step title="Wake Instantly">
    Top up wallet and resume from the same state.
  </Step>
</Steps>

## Next

<CardGroup cols={2}>
  <Card title="Cloud Quickstart" icon="rocket" href="/quickstart">
    End-to-end getting started flow
  </Card>

  <Card title="Payments" icon="credit-card" href="/concepts/payments">
    Understand USDC streaming and inference billing
  </Card>

  <Card title="Compute" icon="server" href="/concepts/compute">
    Hosting tiers and runtime architecture
  </Card>

  <Card title="Node Operator Guide" icon="hard-drive" href="/guides/node-operator">
    Host cloud workloads and earn from compute
  </Card>
</CardGroup>