Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.auvy.ai/llms.txt

Use this file to discover all available pages before exploring further.

Developer Overview

AUVY Synapse is a multi-app monorepo. Durable product objects (resource heads, versions, document lane, search chunks) live on the unified resource spine in Mongo and related stores; the public docs explain how to use that model via /v1/browse, /v1/search, and /v1/resources. This page maps apps and packages for contributors. 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

AppPurposeDefault port
apps/webNuxt dashboard3000
apps/apiPublic REST API and auth-aware platform routes3001
apps/agent-endBackground execution worker3002
apps/mcpHosted MCP server3003
apps/connectIntegration lifecycle and tool execution3004
apps/botsBot control plane + worker (not the Synapse API)3005
apps/docsMintlify docs site3000 (or next free)

Package boundaries

PackageRolePublic?
@auvy-synapse/kernelShared env helpers, workspace/branding constants, pure utilities — imported from packages/kernel/src (no publish workflow for app imports)N/A (monorepo-only; consumed like application code)
@auvy-synapse/clientPublic TypeScript SDKYes
@auvy-synapse/connect-clientTyped HTTP client for Connect (/v1/integrations, OAuth apps); workspace-only packageNo
@auvy-synapse/private-clientDashboard-only client for workspace APIs and Connect-backed integration routesNo
@auvy-synapse/internalShared schemas, config, and utilitiesNo
@auvy-synapse/authShared request authentication and role checksNo

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-client is used by the dashboard and is not published
  • resolveConnectPublicUrlFromEnv (Connect’s public base URL for OAuth and integration HTTP) lives in @auvy-synapse/kernel/config/connectPublicUrl and is re-exported from @auvy-synapse/connect-client for callers that already depend on Connect types
  • Connect management routes are JWT-only and intentionally excluded from the public SDK
  • Some SDK helpers under backend exist 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, document-lane resources, and execution data
This split is why some public flows are API-key based while integration management remains user-session based.

Where to start