Integration
Cloud Developer Mode
Developer-facing guide to OAuth-connected cloud AI sessions with Synchronex context injection.
5 min read
OAuth Sequence
text
AI client
-> redirects user to /oauth/authorize
-> user approves scopes
-> Synchronex returns authorization code
-> client exchanges code at /api/oauth/token
-> client calls Synchronex MCP/API with sxo_* tokenRedirect URIs
Register exact HTTPS redirect URIs for production apps. Local development may use localhost callback URLs during testing.
Scopes
| Scope | Meaning |
|---|---|
| memory:read | Read Identity Kernel and Product State |
| memory:write | Update memory and product state |
| decisions:read | Search and read Decision Index |
| decisions:write | Log decisions and session outcomes |
Tokens and Refresh
Access tokens use the sxo_* prefix. Expired tokens return a structured token-expired response so clients can show a reconnect flow.
Context Injection
Synchronex injects the Identity Kernel first. Product State is appended when the session has an active product or the client asks for one explicitly.