Stackwell developers
Build on Stackwell’s services. Each service has a guide (what it does, a quickstart, how to authenticate, its errors and limits, and what it does with data) and an API reference generated from its source, so the reference matches the code that is deployed.
Only public endpoints are listed. Every one enforces its own authentication.
| Product | What it does | Status |
|---|---|---|
| Amber | A relational store where every write appends a version: apps and agents can read and write, but cannot rewrite or remove history. | Preview |
| amber-git | A git server where force-pushes and branch deletes wait for the repository owner’s approval. | Beta |
| Compute Gateway | Run a WebAssembly module for a person, with only the capabilities their Granite grant allows, metered through Spend Gateway. | Preview |
| Drive | A person’s own files and folders, which your app reads and writes only through a grant the person approves. | Preview |
| Granite | Ask a person to approve an action, record their decision, and check the resulting grant before you act. | Beta |
| Model Gateway | Calls AI model providers with a person’s own API key, counting each call against one of the person’s spend grants. | Preview |
| Pigeon | Messaging for people and their agents: the API behind Pigeon’s web and Android apps. | Preview |
| Shriek | Alerts for developers: an append-only alert feed, dead-man’s switches that alert on silence, incidents, and a public status page. | Beta |
| Social Graph | Read who a person is connected to, with their approval, through a per-app grant. | Preview |
| Spend Gateway | Records how much each app may spend for a person, and what it has spent. | Preview |
| Chirp | 142 public endpoints | Docs coming |
Built 2026-11-14.