Vero Agents

Vero Agents is a runtime for AI agents — session management, message routing, tool execution, structured memory, isolated VM execution, and real-time event delivery behind a single REST API. The @veroai/sdk TypeScript package wraps the full surface.

Install

bash
pnpm add @veroai/sdk

Two-minute setup

typescript
import { VeroAI } from "@veroai/sdk";

const veroai = new VeroAI({ apiKey: process.env.VERO_API_KEY! });

// 1. Trigger an agent run
const { runId } = await veroai.agents.trigger("coordinator", {
  conversationId: "call_8291",
  senderId:       "david-cohen",
  message:        "I need help with my denied claim",
});

// 2. Stream tokens + tool calls
for await (const ev of veroai.agents.runs.stream(runId)) {
  if (ev.type === "token") process.stdout.write(String(ev.data.text));
  if (ev.type === "done")  break;
}

What to read next

  • Quickstart — full working script in under 30 lines.
  • Agents & runs — create agents, trigger runs, stream events, cancel.
  • Brain — structured memory for telepathy-style coordination.
  • Sandcastle — isolated microVMs for untrusted tool execution.
  • REST API — raw HTTP surface, for non-JS clients.

What’s in the runtime

  • Agents — typed CRUD, workspace files (SOUL.md, AGENTS.md, TOOLS.md), auto-trigger policies, multi-modal (text + voice).
  • Runs — multi-turn LLM loop on FIFO session lanes. SSE streaming of tokens, tool calls, and final message. Queryable history.
  • Brain — semantic, episodic, graph, tasks, working memory. Hybrid search with token budgeting. Live subscriptions (the telepathy primitive).
  • Sandcastle — isolated microVMs with ~125 ms cold boot, MCP server on :3000, boot-time secret injection, auto-termination.
  • Messaging — conversations, messages, reactions, typing, media. Agents are first-class participants.
  • Voice — phone numbers, inbound/outbound calls, LiveKit audio for voice agents.
  • Events — WebSocket + SSE + webhooks. Same catalog, three transports.