Use this reference when you need the API shape for current TypeScript packages. Most apps use standalone clients in framework or server code. Hono apps can also use @agentuity/hono to receive service clients on c.var.
Choose an SDK Surface
| If your code is... | Start with | Use it for |
|---|---|---|
| A framework route, server function, worker, or script | Standalone Packages | Importing KeyValueClient, QueueClient, SandboxClient, and other service clients directly |
| A Hono app | Frameworks | Keeping framework routing while reading Agentuity clients from Hono context |
| Service-specific app logic | Service Guides | Choosing KV, vector, queues, email, schedules, tasks, sandbox, auth, or Coder by job |
| Shared validation or structured model output | Schema Validation | Validating route inputs and function/tool inputs |
| Cross-language or non-TypeScript code | REST API | Calling Agentuity services over HTTP |
Standalone Packages
Install and import Agentuity clients from server code
Service Guides
Use KV, vector, queues, email, schedules, tasks, sandbox, auth, and Coder
Frameworks
Use Agentuity from Hono, Next.js, React Router, TanStack Start, and other server frameworks
Schema Validation
Validate route inputs, shared function inputs, and structured outputs
Calling App Code
Share typed workflow functions across routes, workers, scripts, and jobs
Coder Client
Manage AI coding sessions, workspaces, and skills with CoderClient
REST API
Call Agentuity services from any language or HTTP client
If you are moving an older app forward, start with Migration before using this reference for current code.