DeBox Open Capabilities
DeBox provides a practical developer surface for building bots, DApps, and ecosystem integrations around communities and Web3 user interactions.
Capability Map
1. DeBox DApp
- Build in-app Web experiences inside DeBox.
- Use injected wallet providers (
window.deboxWallet,window.ethereum,window.solana) for Web3 interactions. - Read DApp runtime and permission flow in DeBox DApp.
2. DeBox Bot, OpenAPI, and SDKs
- Create and manage a bot through BotMother. Start with the DeBox Bot Development Overview.
- A DApp that needs DeBox OpenAPI must first create a bot and have its backend use the bot's
App Key. - Use the DeBox Developer OpenAPI, Go SDK, Node.js SDK, or Python SDK for the required integration path.
3. OpenClaw DeBox Plugin
- Connect OpenClaw workflows with DeBox bot channels.
- Suitable for teams already operating OpenClaw multi-channel automation.
- Installation and setup: OpenClaw DeBox Plugin.
4. DeBox Shares Protocol
- Integrate permissionless automated revenue sharing into product payments.
- Supports on-chain payment split patterns and settlement workflows.
- Integration guide: DeBox Shares Protocol.
5. DeBox Grant Program
- Apply for ecosystem support if your project is actively integrated with DeBox capabilities.
- Program details and application path: DeBox Grant Program.
6. DeBox App Deep Links
- Open DeBox token market and trading pages, group pages, and user profiles from supported links.
- Link formats and identifier rules: DeBox App Deep Links.
Recommended Integration Path
- For a DApp that only uses injected wallet capabilities, follow DeBox DApp; no OpenAPI credentials are required.
- If a DApp needs DeBox OpenAPI, first create a bot through BotMother, keep its
App Keyon the backend, and then follow DeBox Developer OpenAPI. - For bot development, start with DeBox Bot Development Overview, then choose the Go SDK, Node.js SDK, or Python SDK.
- For a Go bot, choose Long Polling or Webhook based on the message receiving mode.
- If needed, add Shares and Grant participation after the core capability is stable.
Support
- Developer troubleshooting: Developer FAQ / Troubleshooting