SDK Resources
The public SDK is organized into resource namespaces. Most map directly to documented REST endpoints; a smaller set exists to support advanced first-party workflows.Stable resource clients
| Namespace | Purpose | Reference |
|---|---|---|
receptors | List, resolve, share, and invoke public entry points | /api-reference/receptors |
jobs | Execute async work, inspect status, stream progress, transcribe audio | /api-reference/jobs |
memories | Create, ingest, update, and search memory records | /api-reference/memories |
traces | Inspect conversation threads and add messages | /api-reference/traces |
neurons | Manage AI workers and execution config | /api-reference/neurons |
pathways | Manage and execute visual workflows | /api-reference/pathways |
reflexes | Manage tool collections and execution bindings | /api-reference/reflexes |
recollections | Manage memory scopes for traces and owners | /api-reference/recollections |
search | Semantic search over indexed resources | /api-reference/search |
usage | Usage and billing visibility | /api-reference/usage |
activity | Workspace activity feed and engrams | /api-reference/activity |
public | Share-token based receptor and trace flows | /api-reference/public |
health | Liveness and authenticated workspace context | /api-reference/health |
config | Model catalog, embedding config, and cost estimates | /api-reference/config |
stakeholderMap | Stakeholder graph snapshots, briefings, and versions | /api-reference/stakeholder-map |
Advanced helpers
These namespaces are exposed publicly but are closer to first-party tooling than the core REST contract:| Namespace | Includes | Notes |
|---|---|---|
backend | validatePathway, compilePathway, getNeuronCards, chatCompletion, chatNeuron, raw tools metadata | Useful for builders and internal tooling. Some helpers front endpoints that may evolve faster than the core resource CRUD surfaces. |
v1 | get, post, put, patch, delete helpers under /v1/* | Escape hatch for new endpoints before a typed namespace is added. |
Streaming helpers
These package-level exports are part of the intended SDK surface:Pagination helpers
Every list-style namespace exposes eitherpaginate(), listAll(), or both.
Contract boundaries
@auvy-synapse/clientis the public package and is appropriate for product integrations.@auvy-synapse/private-clientis dashboard-only and not published to npm.- JWT-only workspace integration management is intentionally outside this API-key-focused docs set.
Related
- TypeScript SDK for installation and auth setup
- API Reference for REST details
- Developer overview for app/package boundaries