Build Apps for Agents
Turn app capabilities into structured actions for CLI, HTTP, MCP, OpenAI / AI SDK tools, React hooks, and typed clients.
React
TypeScript
Node.js
npm
Next.jsReactTypeScriptNode.jsnpmNext.jsStart from the entry point that matches your app
Mature documentation sites usually make the next step obvious. Start fresh, integrate into an existing app, or jump in with a template.
Start with the core flow
Learn the baseline setup, package layout, and the first action-to-surface workflow.
Integrate into an existing app
Follow practical recipes for MCP servers, React apps, route handlers, and automation scripts.
Start from a pattern
Use documented starter patterns when you want a proven integration path instead of guessing the surface wiring.
Define once, observe everywhere
An action is the unit of agentic capability. Every surface and every consumer reads from the same contract and the same streaming runtime.
Streaming Runtime
Validation, permissions, retries with per-attempt cancellation, idempotency, concurrency limits, redaction — and live event streams any consumer can subscribe to.
CLI / HTTP / MCP
All three are thin adapters over the same action contract. MCP stdio auto-detects Content-Length and newline framing; HTTP returns detailed error codes.
OpenAI / AI SDK / Typed Client
Generate OpenAI Chat & Responses tool specs, Vercel AI SDK tools, and a typed client (.d.ts) — all from the same action manifest.
Open in your coding assistant
Download a bootstrap markdown file for your local coding assistant. It tells the assistant to clone the repo, find the SDK package root, read the right docs, and start from there without extra setup from the user.
One contract, every surface
Ageniti gives you the action contract and the runtime that observes it. CLI, HTTP, MCP, OpenAI / AI SDK tools, React hook, and the typed client are all derived from the same definition.
One contract, every surface
CLI flags, HTTP routes, MCP tools, OpenAI / AI SDK tool specs, React hooks, and the typed client are all derived from the same action. You never describe an action twice.
Bring your own schema
Zod, Valibot, ArkType, anything implementing Standard Schema v1 — Ageniti detects and wraps foreign schemas, so your existing typed validation keeps working.
Streaming events as a primitive
Logs, progress, and artifacts emit live as events any consumer can subscribe to. Build chat UIs, agent loops, or log shippers on top without owning the action.
Production-ready controls
Validation, permissions, timeouts, retries with per-attempt cancellation, idempotency keys, concurrency limits, secret redaction, and detailed error codes — all in the runtime.
Cover the main integration paths
Expose selected application capabilities to the environments where agents and operators actually work.
Use patterns to skip integration guesswork
Use focused starter patterns to wire one app capability into CLI, MCP, HTTP, React, or tool-calling surfaces without guessing the package shape.
CLI App Starter
Start with one action and expose it through generated CLI commands with flags, JSON input, schema output, and stable envelopes.
MCP Server Bundle
Expose selected app capabilities through MCP tools and generate the stdio launcher plus descriptor used by MCP hosts.
Next.js AI SDK Bridge
Map selected actions to Vercel AI SDK-style tools from a Node-safe app entry while keeping app logic in the shared runtime.
Integrate gradually
Ageniti works best when you start from a narrow, stable capability and grow outward.
Wrap one capability
Choose an existing flow like search, invoice creation, or account lookup, then define it with a typed action contract.
Add a headless entry
Keep your existing React or Next.js structure, and add a small Node-safe app entry for runtime and launcher wiring.
Expose where needed
Generate the surfaces you need for external tools, operators, internal automation, or local development.
What's in the box
Ageniti is the action primitive layer. It stays focused on the contract and the runtime, and stays unopinionated about how you compose actions on top.
Built in
Up to you
Start with one capability, not a rewrite
Read the docs, define a first action, and expose a real part of your application to external tools, automation systems, and agent callers through explicit, reviewable contracts.