DeHub Developers — Build Apps on DeHub
DeHub is an open platform. Ship a mini app to the DeHub app store, let people sign in with DeHub on your own site, take payments in DHB, or read and write DeHub from your server or your AI agent. Pick the path that fits what you are building.
Pick your path
- Mini apps: A web app that runs inside DeHub on web and phone, listed in the DeHub app store. One script tag, no SDK install.
- Sign in with DeHub: Let people log in to your app or website with their DeHub account. Standard OAuth with PKCE.
- Webhooks and notifications: Hear when someone adds your app, and send them notifications on web and phone.
- API reference: The REST API, the Mastodon-compatible API, rate limits and errors.
- Examples: Copy and paste code for the things most apps need first.
- AI agents (MCP): Connect ChatGPT, Claude or your own agent to DeHub with the MCP server.
Your first mini app in five minutes
- Put any web page online over https.
- Add
<script src="https://riftn.com/sdk/miniapp.js"></script>and calldehub.ready()once your first screen is on. - Open dehub.io/apps/dev, paste your link and press Launch. It runs inside the real DeHub host, localhost included.
- Add a
/.well-known/dehub.jsonmanifest. The developer page checks it field by field and signs the ownership block with your wallet. - Press Submit. Your app gets a share link right away and goes into review for the store.
No account approval, no API key and no fee to get started. Farcaster mini apps run as they are: DeHub reads farcaster.json when there is no dehub.json.
What DeHub gives your app
| Feature | What it does |
|---|---|
| Distribution | A listing in the DeHub app store on web and phone, rich link cards in the feed, and a share link for every app. |
| Identity | A signed token that proves who the user is, checked on your server with public keys. No passwords to store. |
| Payments | Ask for DHB in one call. The money goes straight to your wallet. No fee on your first $10,000 a year. |
| Notifications | Reach people who added your app on web and phone, with one HTTP call from your server. |
| Rewards | The top apps each week share a monthly DHB pool, ranked by real use. |
Best practices
- Build mobile first. On wide screens DeHub runs your app in a phone-width column.
- Call
dehub.ready()as soon as your first screen paints. The splash screen waits up to 8 seconds, then steps aside anyway. - Never trust the browser. Send the sign-in token and payment receipts to your server and verify them there.
- Use
dehub.getCapabilities()before calling an action, so your app degrades well on older hosts. - Keep notifications rare and useful. Each person gets at most one every 30 seconds and ten a day from your app.
- Use
notificationIdvalues that describe the event (for exampleturn-42), so a retry never sends the same thing twice.
Getting help
Stuck? Read Troubleshooting first. For anything else, ask in the DeHub app or contact the team.
Open DeHub