Developer Overview
AUVY Synapse is a multi-app monorepo. The public docs focus on the external developer contract, but the repo also includes internal apps and packages that shape how those surfaces work.Service map
| App | Purpose | Default port |
|---|---|---|
apps/web | Nuxt dashboard | 3000 |
apps/api | Public REST API and auth-aware platform routes | 3001 |
apps/agent-end | Background execution worker | 3002 |
apps/mcp | Hosted MCP server | 3003 |
apps/connect | Integration lifecycle and tool execution | 3004 |
apps/docs | Mintlify docs site | 3005 |
Package boundaries
| Package | Role | Public? |
|---|---|---|
@auvy-synapse/client | Public TypeScript SDK | Yes |
@auvy-synapse/private-client | Dashboard-only client for workspace and Connect routes | No |
@auvy-synapse/internal | Shared schemas, config, and utilities | No |
@auvy-synapse/auth | Shared request authentication and role checks | No |
Public developer surfaces
- REST API at
https://api.auvy.ai - TypeScript SDK via
@auvy-synapse/client - CLI via
@auvy-synapse/cli - MCP server at
https://mcp.auvy.ai/mcp - OpenAPI spec at
https://api.auvy.ai/openapi
Private and first-party surfaces
@auvy-synapse/private-clientis used by the dashboard and is not published- Connect management routes are JWT-only and intentionally excluded from the public SDK
- Some SDK helpers under
backendexist for builders and first-party tooling, but they are not the same stability tier as the core CRUD namespaces
Data model split
AUVY uses two logical data planes:- Platform/Auth DB for workspaces, users, billing, API keys, integrations, and secrets
- Product DB for neurons, pathways, receptors, reflexes, memories, and execution data
Where to start
- Integrate the API if you are building against the platform
- TypeScript SDK if you are using JavaScript or TypeScript
- Local development if you are working in this repo