Developers
Two codebases talking through one frozen OpenAPI contract - a NestJS backend that never signs, and a Next.js client that never holds a key.
Botanary's developer surface is two codebases talking through one frozen contract - a NestJS backend builds unsigned operations and never signs, a Next.js frontend generates a typed client straight from that contract, signs client-side, and relays what it signed. The sections below cover the architecture, the API seam, authentication, the ERC-4337 smart account layer, the generated API client, the full API reference, and how to run the stack locally.
Architecture
How the backend and frontend are organized.
The API seam
The hand-authored OpenAPI contract both sides build against.
Authentication
How a Privy auth token becomes a Botanary session.
ERC-4337 and user operations
The UserOperation lifecycle everything signs into.
API client
The generated TypeScript client, running against mocks in minutes.
API Reference
Every endpoint, request, and response schema.
Local development
Running the whole stack locally, frontend and backend.