Build on the platform
Build on Onchain Suite
Drop the SDK into your dApp for wallet-based notifications, send events from your product, and read your data from a server-to-server API. Start in the frontend, reach for the backend as you grow.
Two layers
Most integrations begin in the frontend and grow into the backend. You can ship real value with only the first.
Integrations
The frontend SDK and the events that feed it. Wallet auth, in-app and
push notifications, and custom product events. No backend required to
start.
Developers
The server-to-server API. Keys, domain verification, automation
triggers, webhooks, and the SQL schema behind your data.
Start in the frontend
Wallet-authenticated notifications in your dApp, in two lines.
In-app notifications
Wallet auth plus in-app, web, and mobile push. Where most integrations begin.
Custom events
Send signups, deposits, and upgrades, and trigger messaging from them.
API keys
Publishable keys for the browser, secret keys for your server.
Reach for the backend
Server-to-server control when you need it.
Wallet and contract data
The on-chain and off-chain signals behind audiences and automations.
Domain verification
Authenticate your sending domain with the right DNS records.
Automation triggers
Feed trigger events from your own indexer or backend.
Webhooks
Receive platform events at your endpoint.
SQL schema
Every table, column, and type you can query.
Docs MCP server
Connect these docs to Claude, Cursor, or VS Code.
The shape of an integration
Add the SDK so wallets can receive notifications. Send events from your product, from the browser through a form or from your backend with a secret key. Then let campaigns, audiences, and automations operate on the result and reach users on whichever channel they’re on.