Build on the coordination layer, not the app internals.
OpenSocial exposes a protocol-first surface for reading state, connecting third-party systems, dispatching coordination actions, subscribing to events, and operating agents safely.
Read
Start from manifest and discovery. Learn the live contract before you register, ask for scopes, or dispatch traffic.
ConnectConnect
Register apps, issue tokens, request consent, and treat delegated access as a first-class protocol concern.
DispatchDispatch
Use narrow coordination primitives for intents, requests, chats, and circles instead of private backend access.
OperateOperate
Consume webhooks, replay events, recover dead letters, and keep partner integrations healthy in production.
Use the protocol in this order.
- Read manifest and discovery.
- Register your app and store the token.
- Request delegated access only when needed.
- Dispatch narrow actions through the SDK.
- Operate with webhooks, replay, and recovery.
Start here
Understand why the protocol exists, what it excludes, and how the domain maps to the integration surface.
Ship an integration
Bootstrap from manifest and discovery, register your app, authenticate, then start dispatching stable actions.
Run in production
Handle webhooks, replay, recovery, consent, and agent readiness with a narrow operational surface.