Agentuity Documentation

Start here when the thing you are deploying is an app, API, static site, worker route, or service boundary. Agentuity packages the project you already own. Keep the framework conventions, logging, and app data layer; add service clients where server-side code needs Agentuity infrastructure.

Choose the App Shape

App shape	Use when	Start with
Web app	The app has pages, browser UI, and server routes or server functions.	Web Apps
Backend API	The app exposes JSON endpoints, webhooks, or an internal service API.	Backend APIs
Static site	The app is plain HTML, a docs site, or a static SPA bundle.	Static Sites
Background work	A request starts work that needs retries, status, or durable output.	Background Work

Minimal Backend Shape

A deployable app can be a plain HTTP server. This Hono example has no agent-specific wrapper:

typescriptsrc/index.ts

import { Hono } from 'hono';
 
const app = new Hono();
 
app.get('/health', (c) => {
  return c.json({ healthy: true, uptime: process.uptime() });
});
 
app.post('/echo', async (c) => {
  const body: unknown = await c.req.json();
  return c.json({ echo: body, receivedAt: new Date().toISOString() });
});
 
export default app;

Add service clients only where the app needs them. A route can call KeyValueClient, a worker can publish to QueueClient, and a script can call SandboxClient with the same project credentials. Keep your app database, ORM, and framework logger where they already fit.

Next Steps

Use these pages after you choose the HTTP, static, or background-work shape.

Frameworks: use framework-native route files and server functions
Services: pick the client package for storage, queues, tasks, schedules, sandbox, Coder, and observability
Deploy Framework Apps: inspect agentuity build output and launch.json