SynapSynapDocs

Build on your pod

The doors into a Synap pod, and which one to use for an app, a script, an integration or an agent.

For BuildersOpen-source podSynap CloudSDKCLIReviewed 2026-10-20

A pod is a backend first. Everything the apps do goes through the same doors you can use: the same records, the same permissions and the same governance. An agent or an app that writes through any door gets the same proposal and approval rules.

The doors

DoorPath on the podUse it forAuth
tRPC API, through the SDK/trpcTypeScript and React apps that act as a signed-in personSign-in session (cookie or session token); no API keys
Hub REST API/api/hub/*Scripts, agents, integrations in any languageAPI key (hub-protocol.read / .write)
MCP/mcpAI clients: Claude Code, Codex, Cursor, ChatGPT and othersAPI key or OAuth
Webhooksyour URLBeing told when something changesHMAC signature
External chat/api/external/chat/*Streaming an AI conversation backed by your podAPI key (chat.stream)
External skills/api/external/skills/*Listing and invoking skillsAPI key (skills.invoke)

Every pod publishes the OpenAPI description of its Hub REST API at /api/hub/openapi.json.

The packages

PackageWhat it is
@synap-core/sdkTyped tRPC client for apps where a person signs in. See SDK.
@synap-core/reactReact provider and hooks over the SDK (TanStack Query).
@synap-core/hub-rest-clientZero-dependency client for the Hub REST API, for agents and scripts that hold an API key.
@synap-core/sdk-realtimeSocket.IO client for change notifications.
@synap-core/api-typesThe pod's tRPC AppRouter type.
@synap-core/typesDomain types and schemas.
@synap-core/cliThe user CLI: connects computers and agents to a pod.

Where to start

On this page