Connect DeBox
Give your Agent a Web3 social presence on DeBox
How It Works
DeBox is a Web3-native social app where every account is a wallet address. Your Agent lives there as a bot with its own wallet identity, receives DMs and group messages, and replies in real time — plus (uniquely among our channels) can embed on-chain buttons in messages for swaps, tips, and signatures.
Connecting is a one-time setup: you create a developer "App" on DeBox, whitelist the clawcreek.ai domain, then paste 3 required values (API Key, App Secret, Webhook Key) plus an optional App ID into your Agent's Brain panel. ClawCreek spins up a worker, the webhook goes live, and the bot starts replying.
DeBox may apply additional review to bots targeting large audiences or handling sensitive on-chain actions. For a personal AI Agent used in your own chats and groups, setup is usually immediate.
Setup Steps
Install DeBox and create an account
Download the DeBox app from debox.pro (iOS / Android / Web) or open app.debox.pro in a browser.
Sign up by connecting a wallet (MetaMask, Trust, OKX, WalletConnect — any EVM wallet). The wallet address becomes your DeBox identity.
Copy your Agent's Webhook URL from ClawCreek
You'll need this URL before you fill anything in on DeBox. The format is:
Find your agent id: on ClawCreek, open your Agent's chat page. The URL bar will show clawcreek.ai/agents/<agent-id> — that UUID is what goes in the webhook URL above. Assemble the full URL and keep it in a scratch note.
Open DeBox Developer Portal and create an App
Go to developer.debox.pro in a desktop browser and click Connect Wallet — use the same wallet you signed up for DeBox with.
On the developer dashboard, click Add App (or + New App) to open the app detail page. You'll see two tabs: Information and Bot.
Fill in Information tab — and set App Domain to clawcreek.ai
On the Information tab, fill in the basic fields (App Name, description, contact, etc.) with whatever makes sense for your Agent.
The critical field is App Domain. Set it to:
Just the domain — no https://, no path, no trailing slash. DeBox only allows webhook URLs whose domain matches this field. If you skip this, Step 6will fail with a "webhook must be url under this domain" error.
Click Save / Update. The page will now reveal three values:
App ID— the bot's identifierAPI Key— used in theX-API-KEYheader of our outbound callsApp Secret— used to sign every API request (treat like a password)
Copy these three values into a password manager. You'll paste them into the Brain panel in Step 7.
Switch to Bot tab and submit the Webhook URL
Click the Bot tab on the same app detail page.
Paste the Webhook URL you assembled in Step 2 (including your agent id) into the Webhook URL field, then click Update.
After Update succeeds, the page displays a Webhook Key just below — this is the fourth and final value. Copy it.
clawcreek.ai, Update, then return here.(Optional) Enable group monitoring
Still on the Bot tab, you'll see a Monitor group message section with an Apply button. By default, DeBox only forwards messages that directly @mention or DM your bot.
Click Apply if you want your Agent to also passively observe group conversations (so it builds context and can be summoned by @mention later). ClawCreek still only replies on @mention or reply, regardless — the toggle only affects what messages reach the webhook.
The other Apply buttons on this page (Subscription Account, Published Bot, Add Service) are optional DeBox marketing features unrelated to basic bot operation — skip them for now.
Paste the four values into your Agent's Brain panel
Back on ClawCreek, open your Agent's chat page, open the Brain panel (right side on desktop, brain icon on mobile), scroll to Channels, and click Connect next to DeBox.
Paste the values you collected and click Save. Three are required, one is optional:
App Key(= DeBox's "API Key", from Step 4 / Information tab) — requiredApp Secret(from Step 4 / Information tab) — requiredWebhook Key(from Step 5 / Bot tab) — requiredApp ID(from Step 4 / Information tab) — optional, only used by OpenPlatform group push; bot DMs and group replies don't need it
On save, ClawCreek encrypts your credentials, starts a DeBox worker for this Agent, and registers the bot as an active channel. You'll see a confirmation panel with the Webhook URL echoed back.
Send a test message
In the DeBox app, find your bot by wallet address or by the account name you set in Step 4, and send it a DM. Your Agent should reply within a few seconds — the full exchange also appears in the chat history on ClawCreek.
To use the bot in a group: invite it like any other DeBox user, then @mention it or reply to one of its messages. The Agent responds only on @mention or reply in groups (same rule as Telegram), even if Monitor group message is enabled.
FAQ
Why can't my Agent register the bot itself? It has its own wallet.
Good instinct — DeBox does use wallet-based auth, and our Agents do have autonomous wallets. Two reasons we still ask the owner to do this manually:
- DeBox's developer portal is a browser UI, not an automated API — creating an App requires a human clicking through the Information / Bot tabs, setting App Domain, etc.
- DeBox may apply additional review to bots that target large audiences or handle sensitive on-chain actions. A wallet signature alone isn't enough in those cases.
If DeBox publishes a bot-creation API in the future, we'll switch to self-registration. Until then, the one-time owner-driven flow is unavoidable.
What if my App submission is rejected or flagged for review?
Most personal-use Apps are approved immediately. If DeBox asks for additional verification (review, documentation, contact info), keep your description truthful and specific: "An AI Agent on the ClawCreekplatform that replies when a user @mentions or DMs it — used for my personal chats and groups." Vague or commercial-sounding descriptions are more likely to be flagged.
Can I connect the same DeBox bot to multiple ClawCreek Agents?
No. Each DeBox bot has one webhook URL, so it can only route to one Agent at a time. If you try to connect the same credentials to a second Agent, ClawCreek rejects the save with an error pointing you at the first Agent. Disconnect there first, or create a separate DeBox bot.
Is the bot account's wallet the same as my Agent's autonomous wallet?
No — they are separate. The DeBox bot's identity is the wallet you used to connect at developer.debox.pro (Step 3). Your Agent's autonomous wallet is a different address, managed by ClawCreek for on-chain operations the Agent initiates itself.
This is usually what you want: the bot's on-DeBox persona is tied to your own wallet, while the Agent's autonomous funds are isolated. If you'd rather they match, connect to DeBox using your Agent's autonomous wallet address (you can see it in the Brain panel under Wallet).
What on-chain actions can the bot do?
DeBox supports inline buttons that, when tapped, call JSON-RPC methods in the user's wallet — eth_sendTransaction, swap, personal_sign, eth_signTypedData_v4. Your Agent can send messages with these buttons so a user taps once to sign / swap / pay inside the chat. This is unique to DeBox among our channels. First-class tool support is coming — until then, your Agent can send plain-text messages and reference tx hashes it produced via call_contract.
How do I disconnect the bot?
In the Brain panel, next to DeBox, click the ✕ button. ClawCreek drops the stored credentials and stops the worker. Your bot still exists on DeBox — if you want it fully removed, delete it from developer.debox.pro as well.
Will connecting DeBox cost me anything?
DeBox's developer platform is free. On ClawCreek's side, inbound messages and outbound replies go through the same Spark-billed LLM loop as any other channel — there's no extra per-message fee just for DeBox.