Build agents that can do the work
Stead is a backend for agent applications. Deploy your agent programs and JavaScript tools, connect a model provider, and give your application an authenticated API for running them.
The starter is a small support application. A customer signs in, asks about their orders, and requests a refund. The agent reads that customer’s exposed order data. The refund pauses for the developer’s approval before changing the demo balance.
What you bring
Section titled “What you bring”- Your application. Build its interface with the client SDK and optional React binding.
- Your agent programs and tools. Describe the steps in
stead.jsonand implement tools in a JavaScript handler bundle. - Your data model. Deploy SQL migrations and explicitly expose the data operations your agents and customers may use.
- Your model provider key. Save it in project settings. Model usage is charged by your provider.
What Stead runs
Section titled “What Stead runs”Each deployed project receives its own database runtime. Stead stores deployment versions, coordinates agent runs, records step results and reported costs, and resumes eligible interrupted work. Approval gates pause a run until its project owner approves or denies the action.
The browser SDK authenticates customers separately from the developer who owns the project. Conversations and data access use the customer’s identity. A project credential grants broader access and belongs only in trusted tooling or server code.
Two accounts, different responsibilities
Section titled “Two accounts, different responsibilities”| Account | Where it signs in | What it does |
|---|---|---|
| Developer | Stead console | Creates projects, deploys code, configures keys and browser origins, inspects runs, and resolves approvals. |
| Customer | Your application | Starts exposed agents, accesses allowed data, and returns to their conversation. |
A developer account does not automatically sign you into the starter as a customer. Even when you use the same email address, the accounts and sessions are separate.
When it fits
Section titled “When it fits”Stead fits applications where an agent needs controlled access to user data and tools: support workflows, assistants inside a product, or actions that require review before execution. The beta starter demonstrates these boundaries with demo orders; it does not connect to a payment processor or issue real refunds.
Stead does not supply a model-provider balance or make arbitrary external side effects exactly once. Your tools must handle retries safely, and your data exposures must express the access rules your application needs.
Where things live
Section titled “Where things live”| Address | Purpose |
|---|---|
| getstead.dev | Product introduction |
| app.getstead.dev | Developer console |
| docs.getstead.dev | These docs |
https://api.getstead.dev |
CLI, SDK, and HTTP API |