Concepts
Hub Protocol flow
The path of a request from an agent or script through the Hub REST API to the pod.
For BuildersOpen-source podSynap Cloudbeta
Not yet re-verified
This page predates the current docs review and has not been checked against the code yet. Commands, names and counts may be out of date. Prefer the pages marked as reviewed.
Hub Protocol is the primary bridge between agent runtimes and Synap pods.
Request path
- Client/agent calls Hub route with scoped credentials
- Backend resolves actor, workspace, and authorization scope
- Reads return directly; writes enter policy/governance flow
- Event/executor pipeline applies side effects and downstream updates
Why this protocol exists
- one stable surface for external intelligence and automation clients
- avoids coupling integrations to internal frontend implementation details
- keeps governance and audit behavior consistent across user and agent writes
Typical capabilities exposed
- entity and relationship operations
- channel/message operations
- memory/fact operations
- setup and integration utility flows
See: