Build with Pusk
Build with Pusk
What you can build on the Pusk API, in one table: a white-label dashboard, your own Composio, a chat app, a custom agent image, and public webhooks, most with a forkable repo.
Every guide in this section ends with something running, and almost every one comes with a public repo. There are two ways in:
- Fork a finished app when you want to ship fast: point it at your
sk_live_key, rebrand, deploy. - Build it yourself when you want the API pattern: the guides walk through the exact calls.
| I want to… | Guide | Code |
|---|---|---|
| Ship a branded, multi-tenant agent dashboard, with chat, files, and integrations included | White-label dashboard | starter-kit |
| Run integrations on my own Composio: my API key, my users' connected accounts, my metering | Use your own Composio | hermes-openclaw-composio |
| Run agents on my own OpenRouter key: my models, a token per agent, my spend caps | Use your own model | hermes-byo-model |
| Build my own chat UI: one always-on agent per user, streamed replies | Build a chat app | hermes-chat |
| Change what the agent can do: my own tools, skills, and Docker image | Build a custom image | custom-agent-image |
| Give Hermes a public URL for webhook deliveries | Hermes webhooks | None |
| Watch my agent's desktop live — a browser view I can embed in my own app | Build a custom image | hermes-vnc-desktop |
More runnable examples land in the Pusk Cookbook as they ship: example apps, custom images, and full apps to fork.
New to the API itself? Read Core concepts first (one key, two planes), then come back and pick a row.