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.
Integrate the API
This is the canonical onboarding guide: from account creation to production-ready API usage with error handling and streaming. It focuses on the API-key-controlled surface. Platform shape: durable objects (neurons, pathways, documents, …) live on the unified resource spine—use Browse, Search, Resources, and Assets and Artifacts for discovery and knowledge. Execution is receptor- or neuron-first: configure neurons (and optionally pathways), expose them through receptors when you need a stable HTTP surface, share links, or channel triggers. Most “run this agent” flows end atPOST /v1/receptors/:workspace_slug/:slug_or_id/invoke. See Neuron scope for core / workspace / brain.
For server-side or cron neuron runs that should not clutter the user’s default thread history, pass neuron_task_options: { trace_type: "system" } on POST /v1/neurons/:id/invoke or on receptor invoke (same object). neuron_type: completion neurons already persist off the default thread plane when not inside a pathway—see Neurons — Invoke neuron.
Quick start (under 2 minutes)
- Get an API key — Sign up in the dashboard, then Settings > API Keys > Create API Key.
- Pick an entry point:
- REST
- TypeScript SDK
- CLI
- MCP
1. Create an Account and API Key
- Sign up at cortex.auvy.ai.
- Go to Settings > API Keys > Create API Key.
- Copy the key immediately — it is shown only once.
Use an API key issued from the dashboard and send it as
Authorization: Bearer YOUR_API_KEY.2. Choose Your Integration Method
| Method | Best for | Install |
|---|---|---|
| REST API | Any language, curl, custom HTTP clients | None |
| TypeScript SDK | Node/Bun/browser apps with type safety, streaming, retries | npm install @auvy-synapse/client |
| CLI | Terminal workflows, scripting, local testing | npm install -g @auvy-synapse/cli |
| MCP | AI assistants (Cursor, Claude, ChatGPT) | Add server URL to MCP config |
3. Make Your First Request
REST (curl)
TypeScript SDK
The simplest setup usesfromApiKey — it resolves the base URL and workspace from your key:
createAUVYClient (baseUrl defaults to https://api.auvy.ai):
AUVY_API_URL is optional (default https://api.auvy.ai):
public, config, health, and advanced backend helpers, see the TypeScript SDK docs.
Invoke a Receptor
Receptors are the entry points for neurons and pathways. You need the workspace slug and receptor slug:POST /v1/receptors/:workspace_slug/:slug_or_id/invoke — see Receptors API.
4. Handle Errors
All API errors return a consistent JSON shape:AUVYError for typed error handling:
5. Add Streaming
For long-running executions, request a token stream:6. Use the OpenAPI Spec
The full OpenAPI 3.1 specification is available at:- URL: api.auvy.ai/openapi
- File: openapi.json
Troubleshooting
| Issue | What to check |
|---|---|
| Invalid or missing key | Use Authorization: Bearer YOUR_API_KEY. Key must come from Settings > API Keys. Never use a publishable key for server-side writes. |
| Wrong base URL | Default is https://api.auvy.ai. For self-hosted or local dev, set AUVY_API_URL or SDK baseUrl (no trailing slash). |
| CORS errors | Browser requests need the same origin or a backend proxy. Use publishable key + JWT for frontend, API key for backend. |
| 429 Rate limit | Response includes retryAfter (seconds). Back off and reduce frequency. The SDK retries automatically. |
| 401 / 403 | Verify the API key has access to the target workspace and that any required X-Brain-Id context is set. |
403 trial_expired | Free workspace trial ended; upgrade in dashboard Workspace Settings → Subscription. |
403 cost_cap | Monthly included spend (USD) for the plan is exceeded; upgrade or wait for the next period. |
error.getRecoverySuggestion() and Integration patterns.
Next Steps
- Authentication — credential types and when to use each.
- TypeScript SDK — install, auth modes, env variables, and resource clients.
- Integration patterns — streaming, pagination, and error handling.
- API Reference — every endpoint, parameter, and response.